Coming soon

Pricing and access.

schedule-bit Cloud is in developer beta. Keys are issued by request while we build sign-up, a console and billing.

Developer beta Live

Available now. A key scoped to one workspace, with read and/or write. The dev deployment, with every capability marked Live.

Keys are issued by the operator and shown once. Ask the schedule-bit team for one.

Plans and billing Coming soon

Self-serve sign-up, a console (hosted Relay Studio), plans and billing.

What the beta doesn’t include yet.

  • Cross-organisation relays Today a relay's hands must be in the planner's workspace (phase 3). Coming soon
  • A production hostname and an SLA Dev only, today. Coming soon
  • An official SDK package Use plain HTTP; the examples above are the reference. Coming soon
  • Presets beyond temporal-hour and temporal-minute The library has spatial and custom configurations; the API doesn't expose them yet. Coming soon
  • WebSocket authentication for browsers The watch needs an Authorization header, which browsers can't send on a WebSocket, so it's server-side only for now. Coming soon
  • Federation with other clouds, and data residency (phase 4) Coming soon
  • Idempotency keys expire after 24 h, and webhook secrets are stored in the directory as given (encryption at rest is planned) Coming soon

Limits

Body size, idempotency window, journal page, seats, legs, window horizon, webhooks and rate limits are listed in the API reference.

/api#limits →