Billing

Sinatra bills a flat monthly price per workspace for the orchestration it runs: sandboxes, the workflow engine, and the dashboard. Sinatra never bills for model usage. That's between you and your provider.

Every account, including existing and paid accounts, must connect a personal subscription or use a workspace API key before running an agent. A paid Sinatra plan does not replace model access.

Plans

A workspace connects at most one GitHub organization or personal account. Each plan is one price for the whole workspace: invite as many people as you like. Prices are in USD.

There is no daily or monthly task limit on any plan. Every plan includes hosted sandboxes, GitHub issue triggers, optional Linear integration, the CLI, MCP server and HTTP API, and responses to eligible review feedback.

On Free, each request runs for up to 60 minutes. If it needs longer, Sinatra stops, keeps the changes, and picks up when you reply.

Startups get Team at half price for a year: $49.50/mo for 10 tasks at a time, plus 25 queued. Apply on the startups page.

How the queue works

Assign as many tickets as you want. Your plan sets how many run at once; the rest are queued and start on their own as soon as one finishes. If the queue is full, Sinatra says so on the ticket, or in the task's conversation, instead of starting it. On Pro, for example: "Your workspace's queue is full (Pro plan: 3 tasks at a time, plus 10 queued), so I didn't start this one. Try again once a running task finishes." On Free, the message ends with a link to upgrade for more room.

A queued task shows as Queued in the dashboard, and Sinatra posts its position on the ticket: "Queued (position 2). I'll start as soon as a running task finishes." A task started from the CLI, MCP or API gets no position post: its conversation stays quiet while it waits, the CLI says it's queued, and the API's queued field is true. Requests from people start first, oldest first. Work Sinatra starts on its own, such as fixing a failed CI check, comes after them.

What counts as running

A task counts as running from the moment Sinatra starts setting up its sandbox until the agent finishes that request. A task that needs your reply, or sits idle with a PR open, doesn't count. When you reply, the task counts again: it starts right away if the plan has room, and is queued if not.

What counts as queued

A task counts as queued from the moment it is held back by the plan's tasks-at-a-time limit until it starts. A task counts once at most: it is either running or queued, never both, and never twice. Stopping a queued task takes it out of the queue.

CI fixes count against the same limits as your own requests. If the queue is full when you ask for something, your request takes the place of the most recently queued CI fix, and Sinatra says on the PR that it didn't start that fix. Reply on the PR to ask for the fix again.

Tasks from the CLI, MCP or API

Tasks started from the CLI, MCP or API count against your plan's limits like any other task. A start that billing or the queue would stop is refused before the task is made, as in the dashboard: 409 payment_required when you have no model access or the subscription is past due, with a link to the setting that fixes it, and 409 capacity_full when the queue is full, with the dashboard's queue-full message and, on Free, the upgrade link.

Model access and provider costs

Bring your own Claude or ChatGPT subscription, or an API key. Connect a personal subscription in Settings, or ask an owner or admin to add a workspace Anthropic or OpenRouter API key. Personal connections cover the member who connects them, not teammates' tasks. Workspace API keys are shared with authorized workspace members. See Models for supported connections and compatible models.

Your provider's charges, subscription limits, and rate limits apply separately from your Sinatra plan.

Sinatra records token usage and estimated model costs for diagnostics. These estimates are not invoices or amounts owed to Sinatra, including when your provider subscription covers the usage.

Subscriptions

Only the workspace owner manages billing. On Free, the owner picks a plan in Settings → Billing and pays through Stripe Checkout. On a paid plan, Change plan or billing opens the Stripe billing portal, where the owner can switch plans, update the card, see invoices, or cancel. Self-serve billing is monthly.

• Upgrades take effect immediately. Stripe charges the prorated difference for the rest of the period.
• Downgrades take effect at the end of the current billing period. Until then the workspace keeps the larger plan's limits.

Payment past due

A past-due subscription keeps working for a 7-day grace period. After that, new work pauses until the card is fixed or the subscription ends: Sinatra posts on the ticket that the last payment didn't go through, and the task shows Needs your input. Scheduling a cancellation does not clear a past-due pause.

After a subscription ends

When a subscription ends, the workspace returns to Free: 1 task at a time, plus 1 queued, with the 60-minute limit per request. You don't need a card to keep using Free, but you do need a workspace API key or personal subscription.

Check the billing portal's confirmation for when a cancellation takes effect. A cancellation scheduled for the end of the paid period keeps the plan live until then.

Enterprise

Enterprise is arranged by annual contract, with custom limits. Get in touch about security reviews, compliance evidence, SSO / SAML requirements, support, and contractual terms. These are scoped with your team; this page does not represent SOC 2 certification or promise that every Enterprise requirement is already available.