Backlog Cloud
Everything Backlog does locally is free, forever.
Cloud only adds the things that genuinely need our infrastructure — and even then, you opt in per feature.
What Cloud actually adds
The boundary is simple: if a feature needs our infrastructure, it's Cloud. Everything else stays Apache-2.0, forever.
SMTP delivery
Invitations, digests, run notifications via email. Running a relay is a real cost and a real abuse surface — that's why it's a Cloud gate.
Hosted auth & SSO
Magic links, password resets, Google / GitHub OAuth as a managed identity, SAML / OIDC SSO, SCIM provisioning.
Multi-tenant collab
Shared workspace state across machines, presence indicators, real-time board sync, cross-device claim resolution.
Hosted run executors
Anthropic Managed Agents, hosted ephemeral sandboxes, hosted Codex over our infra. The plumbing ships open; the hosted endpoint is metered.
Run history retention
Beyond local disk: cross-device search, replay, artifact blob storage. Pro = 30 days, Team = 90 days, Enterprise = custom.
Audit log export
SOC2-flavored: tamper-evident, retained, exportable to S3 or your SIEM. Local audit (file-based) stays free.
Stays free, always
For the avoidance of doubt — none of these will ever be gated behind Cloud.
- The full Desktop app — kanban, run inspector, agent management, repo management, local invitations
- The CLI — every command, no feature flag, no upsell modal
- The SDK — published standalone on npm, embeddable
- All connectors with BYO token — GitHub, GitLab, Linear, Jira, Notion, Trello, Asana
- Local executors — Claude Code, Codex, custom command, SSH-to-your-own-box, your own Coder/Gitpod/Codespaces
- Local run history & audit trail in
.backlog/ - Self-hosting — point any client at your own backend over the same OpenAPI contract
Get on the waitlist
No marketing list, no drip campaign. One email when Cloud opens to your tier.