01
Message CRUD, threads, drafts, sending, tracking, search, labels, attachments, and repairable incremental sync.
5 MVP surfaces
Platform
A product surface for every communication primitive.
Horato is not a wrapper around one provider. It is a control plane for the resources your customers already depend on.
Provider index
Google WorkspaceMicrosoft 365GmailOutlookIMAPSMTPCalDAVCardDAVCal.comCronofyNylasAurinko
Every resource your customers already live inside.
Horato turns provider variance into explicit capabilities, sync state, and durable events across the communication surfaces your product needs.
02
Calendar
Events, availability, free/busy, recurrence, RSVP, conferences, watch renewal, and sync token recovery.
Push plus delta
03
Contacts
Contact CRUD, multi-value fields, dedupe assistance, address books, groups, and directory-aware capability flags.
Raw payloads preserved
04
Tasks
Task lists, completion, reconciliation, subtasks, linked resources, and provider-specific status mapping.
Google plus Graph
05
Scheduling
White-label booking links, event types, slot generation, lifecycle tokens, buffers, questions, and reminders.
Booking as system of record
06
MCP
Agent tools for search, availability, booking, and email send with explicit approvals for external actions.
Approval-safe writes
Architecture
Normalize the common path. Preserve every provider truth.
Horato is a layered control plane over provider adapters, not a lowest-common-denominator wrapper. Clients get canonical models, capability flags, raw payload escape hatches, signed webhooks, and one action model across REST, SDKs, and MCP.
01
Provider adapters
Google Workspace and Microsoft 365 lead the MVP, with IMAP, SMTP, CalDAV, and CardDAV adapter families next.
02
Canonical domain layer
Email, calendar, contacts, tasks, scheduling, and webhooks share tenant-aware models without discarding etags, sync tokens, or provider IDs.
03
Event log and delivery
Inbound push and delta changes land in an internal log before replay-safe customer webhooks are signed and delivered.
04
Agent-safe action plane
The same actions power REST, JS, Python, and MCP tools, with approval gates for email send, bookings, event mutation, and destructive operations.
Designed for products where communication is workflow state.
Each surface can ship alone, but the control plane gets stronger when conversations, schedules, tasks, and approvals share one event stream.