Pricing
The entire stack — CLI, runtime, broker, Studio — is on GitHub, MIT-licensed. Self-host the whole thing or use our hosted Studio. You pay us when you want the workspace we run; you pay nothing when you don't.
OSS
$0forever
The whole app — CLI, runtime, broker, Studio. Fork it, run it, host it yourself.
@work.books/cli locally.htmlSolo
$7/ month
For one person who wants the hosted Studio — agents, integrations, workgroups for your own work.
Team
$20per seat / month
For 2–50 person teams shipping internal tools and shared work.
Enterprise
Contact sales
For organizations with procurement, security review, and compliance requirements.
Compare
| Feature | OSS | Solo | Team | Enterprise |
|---|---|---|---|---|
| Authoring | ||||
CLI builds .html locally |
Yes | Yes | Yes | Yes |
| Source available on GitHub | Yes | Yes | Yes | Yes |
Source-bundle in every .html |
Yes | Yes | Yes | Yes |
| Hosted Studio | ||||
| Hosted runtime + broker | Self-host | Yes | Yes | Yes |
| workbooks.sh publish URL | Self-host | Yes | Yes | Yes |
| Cloud sandboxes (E2B, Daytona, Vercel) | BYO | BYO key | BYO key | BYO key |
| Workgroups | ||||
| Create workgroups to organize workbooks | Self-host | Yes | Yes | Yes |
| Group-level integration credentials | Self-host | Yes | Yes | Yes |
| Invite teammates into a workgroup | Self-host | — | Yes | Yes |
| Member admin and roles | Self-host | — | Yes | Yes |
| Per-workgroup access controls | Self-host | — | Yes | Yes |
| Seat count | You decide | 1 | 2+ | Contracted |
| Identity | ||||
| Email + Google + Microsoft sign-in | Self-host | Yes | Yes | Yes |
| SAML / OIDC SSO via your IdP | Self-host | — | — | Yes |
| SCIM directory sync | Self-host | — | — | Yes |
| Compliance and security | ||||
| Audit log streaming to your SIEM | Self-host | — | — | Yes |
| DPA, MSA, security review | — | — | — | Yes |
| Uptime SLA | You operate it | — | — | Yes |
| Custom data residency | You pick | — | — | On request |
| Support | ||||
| Channel | GitHub issues | Named contact + Slack | ||
| Response target | Community | 2 business days | 1 business day | Per SLA |
Notes
The whole stack — CLI, runtime, broker, Studio — is MIT-licensed on GitHub. Clone, build, host it yourself, run it for as many users as you want. You're paying us when you want the workspace we run on workbooks.sh, not for access to the code.
OSS is yours to host. Solo is us hosting it for you — the broker, the runtime, the Convex storage, the Polar billing, the daily usage rollups. $7/month is what it costs us to do that for one person; pick OSS if you'd rather run your own infra.
One seat per member who can author, edit, or admin workbooks inside your workspace. Viewers who only open a workbook you've shared with them — internal or external — don't count.
Not really. Solo gives one person a hosted workspace with workgroups, agents, and integrations — but it's strictly 1 seat. Solo accounts can't invite each other, can't share a workgroup, can't share integration credentials. Five Solos = five disconnected workspaces. The moment two people want to collaborate inside the same workgroup, they need Team.
SAML and OIDC SSO terminate at your identity provider, which carries a real per-tenant cost on our side regardless of seat count. Email, Google, and Microsoft sign-in are on every paid tier — those cover most teams under 50 people without needing SAML.
Yes — the entire app is on GitHub. Roll your own Workbooks site, point your DNS at it, use your own Cloudflare account and Convex deployment. The CLI's host: config field lets your workbooks redirect at YOUR Studio instead of workbooks.sh.
Annual contract, signed MSA, and a seat floor we agree on during the sales conversation. It's priced to make sense once SSO, SCIM, and audit logs are actually needed — not as a toll on small teams.
Paid tiers cancel from inside Studio at any time, prorated to the end of the billing cycle. Your workbooks are .html files — they keep working after cancellation, you just lose the hosted workspace.
Most people start with the OSS CLI to build a workbook, move to Solo when they want the hosted runtime, move to Team when they invite a second person, and call us when their security review asks for SAML.