Pay for what you hold. Nothing else.

Get started on Hobby for free. No card required.

Each plan, pack and limit is posted before it applies: Pro's, Teams' and SSO's prices are set, the packs are not for sale yet, and every limit and each pack's price is a default that may still change before it applies.

What each plan holds, what a pack adds on Pro or Teams, and what happens past each limit.

Every feature is on every plan. What Pro, Teams and the packs add is capacity: choose a plan by its spans, the telemetry your agents send, and treat retention, questions, content held, data out and alerts as ceilings, set so that few organizations meet them.

What a span is

Each step, model call and tool call an agent sends is one span, and so is the run itself, its root. A span counts once for each kilobyte its fields take as they are stored — the bytes of its names, tags, attributes and other text, and 64 for its ids, timings and token counts — rounded up, so a typical span, a few hundred bytes, counts once, and one heavy with attributes counts for the disk it takes. Content is held apart, under the organization's content ceiling, so no plan sells content storage and content never adds to a span's count. A score attached to a run costs nothing.

What data out is

What we send your organization's machines, by the byte: each answer on the API — except to the spans it takes in — with 6.5 KB for its connection, and every export the console builds. A script that loops on the API stops at the day's ceiling; a person reading the console is never counted.

More of one thing, each at its own monthly price, on Pro or Teams; SSO, the one add-on, is on Teams alone. Members, content held and data out are never sold on their own. None is for sale yet.

Each pack is added from your organization's billing page, so there is never a doubt which organization it lands on.

Nothing here will ever carry a price.

Members

Nobody an organization invites pays, and no plan sells a seat. Hobby holds one, its owner, so anyone who works with somebody else moves to Pro; Pro and Teams hold as many as an organization invites, because a team should invite everyone who reads an alert.

Protection

No protection is on a paid plan alone: the content modes, the redactors, the access audit, deletion with receipts, the posture page, the field inventory, the export and the audit log are on Hobby as they are on Teams. A privacy promise that costs extra is not privacy first.

Features

A feature sold apart gives every customer a different product, puts “does my plan have this?” on every page, makes a combination to test of each, and keeps a team from trying what it would need. Hobby is held to one person by its capacity, its one member among it, never by a missing feature.

Sponsorship

A sponsorship of the company, through GitHub Sponsors, is company income: it unlocks nothing and is not a plan.

Two prices, and packs of exactly the capacity an organization needs.

Two numbers

Pro for a developer or a small team, and Teams, five times Pro, for a team that has outgrown it. Teams costs less than the packs that would bring Pro up to it, which cannot match its content or data out at all.

One thing to buy

Every refusal of something sold names the one thing that lifts it: Pro, on Hobby; one pack, on Pro or Teams. What is never sold on its own — content held, data out — is a ceiling sized for what the plan holds, and its refusal says when it lifts.

Prepaid, never metered

Pro, Teams and their packs are paid for before they are used, so what you hold is known at the door and a bill never moves on its own: pay for what you hold, nothing else. There is no usage bill, no overage charge and no automatic top-up; more capacity is a pack the owner buys.

Nothing is dropped silently, and every refusal says what lifts it and when.

Members

On Hobby, an invitation that would pass its one member, pending invitations counted, is refused when it is sent, naming Pro, and one sent while the organization was on a paid plan seats nobody past it. An organization that falls to Hobby keeps every member it has, and invites nobody until it moves back.

Spans

On Pro and Teams, spans past what the plan grants are kept for a seven-day grace while the owner is asked for a pack, then sampled and flagged. On Hobby they are sampled and flagged from the first span over, and the owner is asked to move to Pro. The answer to the request that sent them, and the console, say what was sampled.

Retention

Each night the purge removes what has passed the organization's retention. A pack bought applies to what is already stored; one given up is honored the next night. Hourly totals, which name no user and no tag, are kept thirteen months on every plan, for baselines and year-on-year cost.

Content held

Past the ceiling, a span arrives with its metadata alone, the answer naming the content it dropped; each night the purge removes the oldest content first, until a tenth of the ceiling is free, so the newest is what a person opens. Sealed content counts at its ciphertext's size.

Agent questions

Past the cap, a question is refused with the date the period renews. Every question also has a budget of its own: one that reaches it is answered from what it has read so far.

Data out

Past the day's ceiling, the API answers with a Retry-After header until midnight UTC, an export waits for the next day, and the owner is told in the notification feed. Spans sent in are never counted, so a script that reads too much never stops an agent reporting. An audit log export counts each time it is downloaded, and is built no larger than the day's ceiling, so a long log comes a day's worth at a time.

Alerts

A new alert past the plan's number, paused ones counted, is refused when it is made, naming Pro, or Teams on Pro; an organization that falls to Hobby keeps every alert, its two oldest running and the rest paused until it moves back. Its deliveries are what its alerts send Slack, webhooks and PagerDuty, the notification feed never counted; past the day's number nothing more is sent until midnight UTC, the incident stands in the feed as ever, and the owner is told.

Organizations

A person has one Hobby organization: the first is theirs, free, and any other they create is paid for before it exists, on Pro or Teams, so nothing starts waiting on a plan. An organization whose plan ends while another of its owner's holds their Hobby place — a card that failed past the retries — is paused: it keeps its projects, data and members and takes in nothing new until it is on a paid plan again, merged into the Hobby organization, handed to someone whose Hobby place is free, or moved to Hobby once that place frees. Being a member of other organizations costs nothing and is never limited.

Each organization is billed on its own day, and keeps what it paid for to the end of its period.

Each organization's own month

A subscription renews on the day it began, so no first invoice is a prorated fraction. An organization that has never bought counts its month from the day it was created; moving to Pro or Teams starts a fresh period that day; a subscription that ends leaves its day in place. Usage is counted over the same period, so the invoice's month is the usage's month.

Changes

Moving up — to Pro, or from Pro to Teams — and buying a pack apply at once, prorated. Downgrades — Teams to Pro, or a pack given up — apply at the period's end, because the spans a plan or a pack grants may already be spent; what Teams held past Pro is then treated as the fall to Hobby treats what Pro held. A cancellation runs to the end of the period begun.

The fall to Hobby

An organization falls to Hobby when a cancellation reaches its period's end, or when a card fails and the retries run out; while they run, it keeps what it paid for and is sent payment reminders. Either way, its data past Hobby's retention is held, hidden, for fourteen days, then purged, the owner told the date twice; and its members stay, but it invites nobody until it moves back. A cancellation is refused while another of the owner's organizations holds their Hobby place, since the organization could not fall there: delete it, merge it into the Hobby organization, or hand it over instead. A card that fails past the retries while the place is held pauses the organization, as Organizations says. Cancelling keeps the organization and its data, under Hobby's limits.

Deletion

Deleting an organization cancels its subscription at once and refunds the unused part of the period. The organization is then erased, with no restore. Handing an organization to a new owner keeps its subscription, its card and its data; one on Hobby, or set to fall to it, goes only to an owner with no Hobby organization.

Prices are posted in USD, tax-exclusive. Stripe Tax computes tax at checkout, which collects the legal name, address and VAT id, so an EU business is reverse-charged. Every price will also be posted in EUR when the EU-hosted service opens.

Agencies

An agency holds client organizations as a pack on its Pro or Teams, the clients' spans pooled with the agency's. A client's viewer is a read-only member, so it costs nothing.