Nylas provides calendar infrastructure with scheduling features including round-robin meeting types (max-fairness and max-availability modes). Orita is provider resolution infrastructure — it determines which professional qualifies for a patient or request, then verifies availability and confirms the booking.
| Capability | Nylas | Orita |
|---|---|---|
| Primary use case | Read/write calendars and email | Resolve which provider qualifies, then book |
| Eligibility rules | Not included — you build it | Included: 13-stage deterministic pipeline |
| Insurance constraints | Not included | Included with alias normalization |
| License constraints | Not included | Included: expiry, region, verification |
| Provider routing | Not included — you build it | Included: ranked, explained options |
| Availability check | Calendar read | Calendar + eligibility-gated + hold |
| Idempotent confirmation | Not included | Included: prevents duplicate bookings |
| Bulk provider sync | Not included | Included: 500 providers, external IDs |
| Resolution explanation | Not included | Per-provider: why matched or excluded |
| Google Calendar | Included | Included |
| Microsoft Outlook | Included | Included |
| Webhooks | Included | Included: signed, stable IDs, replay |
| Multi-org isolation | Partially supported | Included: scoped keys |
| Email API | Included | Not provided |
| Contact sync | Included | Not provided |
Nylas and Orita can complement each other. Nylas handles the calendar integration layer; Orita handles the eligibility and routing layer on top of it.
Last verified: July 31, 2026 · Orita docs