ROADMAP · COMMITTEDWhat we've committed to ship, and when.
Items with a specific ship-quarter and a stated shipping quality bar. If it's here, we've said publicly we'll ship it — hitting the date is a promise we're accountable to.
UPDATED 2026-08-06 Committed means: we've done enough scoping to name a quarter with confidence, we've allocated build capacity, and any slippage will be announced with reasoning. Exploring items (see /roadmap/exploring) don't carry this weight.
2026-Q4
SSO (SAML) — GACommittedBeta running today for Okta / Google Workspace / Microsoft Entra
Android — public Play Store releaseCommittedPrivate beta ongoing
Business tier — self-serve seat managementCommittedManual onboarding continues in parallel until GA
2027-Q1
SCIM (automated user provisioning)CommittedEnterprise-critical for org-scale deployments
Windows native appCommittedBeta then Microsoft Store
SOC 2 Type II certificationCommittedEngagement + audit scheduled
Third-party pentest (see /security/pentest-summary)CommittedAlongside SOC 2
2027-Q2
Public API (individual + business)CommittedRate-limited; not yet a full LLM API
Business plan connectors — Slack, Google Drive, NotionCommittedRead-only initially
How a commitment can slip
If we miss a committed date: we announce it on /roadmap and in the monthly newsletter with the specific reason (a scope discovery, an upstream dependency delay, a hiring bottleneck). We don't quietly move the date. Recovery timeline is stated alongside the slippage announcement.
Committed items are the load-bearing part of the roadmap.
See /roadmap for the full view.
$20/MO · CANCEL ANYTIME · $0.80/MEAL · RECEIPTS MONTHLY
Read the ledger →