# coss.com vs Nylas Scheduler (https://coss.com/compare/nylas-scheduler)

> Nylas Scheduler has public booking links, Stripe payments and a BAA. coss.com Scheduling bills per booking, on the key you use for email and SMS.

Both give your product hosts, availability, calendar connections, one-on-one, collective, round-robin and group meetings, and a page or component to book on. Nylas Scheduler sits on Nylas's email and calendar APIs, is priced per connected account, and adds public links, native Stripe payments and a BAA. coss.com Scheduling is priced per booking, keeps only busy times from calendars, and shares its API key, webhooks and logs with the rest of coss.com.

Facts about Nylas Scheduler checked on 2026-11-03 against the sources listed below.

## At a glance

| | coss.com | Nylas Scheduler |
| --- | --- | --- |
| Price | $0.10 per booking, charged when confirmed; nothing per host or calendar | No per-booking price. Per connected account: Essentials $15 a month with 10 calendar-only accounts, then $1.70 each; Pro $49 a month with 35, then $1.50 each |
| Free | 100 scheduling bookings a month | 5 email and calendar accounts; calendar-only accounts aren't included |
| Hosts without a calendar | A host needs only a schedule | Virtual calendars, billed per account; Nylas sends no invitations or reminders for their events |
| Calendars | Google, Microsoft and CalDAV (Apple, Nextcloud, Fastmail) | Google, Microsoft, iCloud and Exchange; no Free/Busy on iCloud |
| Calendar consent | Hosts consent to coss.com's Google and Microsoft apps. Using your own apps isn't offered | Your own Google and Microsoft apps, or Nylas's shared Google app with the Accelerator add-on ($2,400 a year, on Pro Annual) |
| Meeting kinds | One-on-one, pool (shared by weight), collective, group (2 to 10,000 seats) | One-on-one, round-robin (fairness or availability), collective, group with a capacity |
| Double-booking | A Postgres exclusion constraint refuses overlapping claims of one host; the loser gets slot_unavailable | Re-checks the slot against the live calendar when booking and rejects a second claim; its page cites "race-condition-free locking" |
| Public booking links | — | A public Configuration gets a page at book.nylas.com/<slug> (coss.com's hosted pages open from a session your server creates) |
| Embedding | mountBooker and mountHostPortal open coss.com's pages in an iframe; or your own UI on the client API | Web and React components with CSS variables and a composable mode, and a Scheduler Editor for organizers |
| Taking payment | Hold the slot, charge with your own provider, then confirm | Native Stripe payments in the booking flow |
| Recurring series | Up to 52 weekly or monthly occurrences at the attendee's local time | — (Not on Scheduler's API reference; its Events API takes RRULEs) |
| Finding a host | Host attributes narrow a pool per booking; availability.search covers up to 500 hosts | — (Not compared: see Nylas's docs) |
| Booking emails | Fixed text, with your brand name or logo and accent color from your own domain; each can be turned off | Fixed wording and branding; turn them off and send your own |
| Reminders | Email, and SMS from your own approved number on the same account | Email or a webhook; SMS through your own messaging stack |
| Meeting links | Google Meet and Microsoft Teams; Zoom only once Zoom approves coss.com's app | Microsoft Teams, Google Meet and Zoom |
| Calendar data | Busy times only. Bookings go on as private events titled "Appointment". Attendee details kept 90 days after the booking ends | Free/Busy returns busy blocks without titles; the Events API reads whole events |
| HIPAA | No BAA yet; the Terms don't allow protected health information without a written agreement | Pre-signed BAA on every paid plan |
| Testing | Sandbox keys, with simulated calendars and no emails or charges | — (Not compared: see Nylas's docs) |
| Also on the same API key | Email, SMS, Verify, Risk, Forms, Sign, Hooks | Email and calendar APIs, Notetaker, Agent Accounts |

## When Nylas Scheduler is the better choice

- **You want a link anyone can open.** A public Nylas Configuration with a slug is a booking page at book.nylas.com. coss.com has no public booking pages yet: each hosted page opens from a session your server creates.
- **Payment belongs in the booking flow.** Nylas has native Stripe payments, with the booking finalized once payment succeeds. coss.com has no built-in payments: you hold the slot and charge through your own provider.
- **You handle patient data.** Nylas offers a pre-signed BAA on every paid plan. coss.com doesn't offer one yet, and its Terms don't allow protected health information without a written agreement.
- **You need more of the calendar than free and busy.** Nylas's Calendar and Events APIs read and write whole events, next to its email API and Notetaker. coss.com only knows when a host is busy, on purpose.
- **You want consent under your own name, or components you can restyle.** With Nylas, hosts consent to your own Google and Microsoft apps, and its web and React components take CSS variables and a composable mode. coss.com's consent screens are its own, and its pages are iframes with your brand name, logo and accent color.
- **Hosts take many bookings each.** Nylas charges per account, however many bookings it takes, so a busy host costs the same as a quiet one. coss.com charges every booking.

## When coss.com is the better choice

- **Many hosts, few bookings each.** A marketplace pays for what gets booked, not for every provider who connected a calendar. A host with no bookings this month costs nothing.
- **Nothing to set up for calendars.** Hosts connect Google or Microsoft through coss.com's consent screens, or CalDAV with an app-specific password. You don't create or verify an OAuth app.
- **Routing for marketplaces.** Describe hosts with your own attributes, narrow each booking by them, and search up to 500 hosts at once. It never falls back to a host who doesn't match.
- **Little held about people.** Only busy times are kept from calendars, bookings are private events titled "Appointment", attendee details are encrypted, and answers never reach webhooks, logs or emails.
- **One account for what comes around a booking.** Booking emails from your domain, SMS reminders from your number, webhooks, logs and sandbox environments, on the API key you use for email and SMS.

## Moving from Nylas Scheduler

1. **Add hosts and reconnect calendars.** Create a host for each organizer and participant with coss.scheduling.hosts.create(). Nylas grants don't carry over, so each host connects their calendar again through the host portal or coss.scheduling.calendars.authorize(). (/docs/scheduling/calendars)
2. **Turn Configurations into event types.** Open hours become schedules, and buffers and notice become event type settings. Round-robin becomes a pool, while collective and group keep their names. (/docs/scheduling/pools-and-groups)
3. **Swap the booking calls and the component.** POST /v3/scheduling/bookings becomes coss.scheduling.bookings.create(), and <nylas-scheduling> becomes mountBooker with a session from your server. Your own UI can use the client API instead. (/docs/scheduling/embedding)
4. **Move webhooks and notifications.** Subscribe an endpoint to the scheduling.booking.* events, set email_from on one of your verified domains, and turn off any notification you send yourself. (/docs/scheduling/notifications)

## Frequently asked questions

### Does coss.com have public booking pages like book.nylas.com?

Not yet. coss.com's hosted pages open from a session your server creates, for one event type, host or booking. Nylas generates a public page from a Configuration with a slug.

### What does coss.com Scheduling cost next to Nylas?

coss.com charges $0.10 per booking once it's confirmed, with 100 scheduling bookings a month on Free. Beyond that you need a paid plan, such as Pro at $25/month, whose fee counts toward usage. Nylas charges per connected account and lists no per-booking price, so which costs less depends on how many bookings each host takes.

### Can coss.com take payment for a booking?

Not by itself. Hold the slot with coss.scheduling.holds.create(), charge the customer with your own provider, then call coss.scheduling.holds.confirm(). Nylas has native Stripe payments in the booking flow.

### Will coss.com sign a BAA for Scheduling?

Not yet, and its Terms don't allow protected health information without a written agreement. Nylas offers a pre-signed BAA on every paid plan.

### Do hosts have to reconnect their calendars?

Yes. Calendar access granted to Nylas doesn't transfer, so each host connects Google, Microsoft or CalDAV again, from the page you embed or through your own UI.

### Is coss.com Scheduling related to Cal.com?

Yes. It's built by the team behind Cal.com, as its own engine with no runtime dependency on Cal.com.

## Sources

- [Nylas pricing](https://www.nylas.com/pricing/)
- [Nylas Scheduler](https://www.nylas.com/products/scheduler/)
- [Nylas docs: Scheduler](https://developer.nylas.com/docs/v3/scheduler/)
- [Nylas docs: hosted Scheduling Pages](https://developer.nylas.com/docs/v3/scheduler/hosted-scheduling-pages/)
- [Nylas docs: the Scheduling component](https://developer.nylas.com/docs/v3/scheduler/using-scheduling-component/)
- [Nylas API reference: Scheduler](https://developer.nylas.com/docs/api/v3/scheduler/)
- [Nylas docs: virtual calendars](https://developer.nylas.com/docs/v3/calendar/virtual-calendars/)
- [Nylas docs: recurring events](https://developer.nylas.com/docs/v3/calendar/recurring-events/)
- [Nylas docs: creating a Google auth app](https://developer.nylas.com/docs/provider-guides/google/create-google-app/)
- [Nylas docs: the Google shared app](https://developer.nylas.com/docs/provider-guides/google/shared-gcp-app/)
- [Nylas cookbook: healthcare appointment booking](https://developer.nylas.com/docs/cookbook/scheduler/healthcare-appointment-booking/)