Billing documentation.

You are billed for unique non-bot git authors whose work the platform touched, counted over a trailing 90 days and measured at each monthly billing cycle. At each cycle the platform takes an immutable snapshot of that count; the billed quantity for the cycle never changes after the snapshot is taken.

Read-only console users, bots, and service accounts are not git authors, so they are never counted and cost nothing. A cycle with zero contributing developers invoices €0 and leaves the subscription and all entitlements active — access does not stop just because a cycle was quiet.

When your developer count grows or shrinks past a volume band, the new band takes effect at the next monthly cycle, in both directions. Nothing blocks or warns you mid-cycle when the count grows: work keeps running, and the change is reflected at the next cycle.

The platform is €35 per contributing developer per month, with volume bands that lower the per-developer rate as your team grows. There is no minimum developer count.

The amount for a cycle is the snapshot developer count multiplied by the rate for the band that count falls in. These are the deterministic figures the console computes; Stripe remains the invoicing authority for what you actually pay.

1. Start with no card

   A new organization gets a 14-day trial with no card required. The term is a fixed 14 days from activation.

2. One trial per GitHub organization, ever

   A single stable GitHub organization receives one trial, once. Re-signing up does not grant a second trial, and subscribing later never rewrites your trial history.

3. Watch the days remaining

   The billing panel reports trial.days_remaining — whole days left, rounded up — and trial.expires_at, the exact end of the term.

4. What happens on day 14

   A trial has no grace period. When the term ends, entitlement is honored only strictly before the end, so access stops until you subscribe. Subscribing from an expired trial works and moves you straight to a paid subscription; it does not restart the trial.

1. Open Billing in the console

   Everything below happens in the console — there is no public subscribe URL to call yourself. Open the Billing panel for your organization.

2. Start the subscription

   Choose to start a subscription. The console opens a Stripe Checkout session in subscription mode for the single platform price.

3. The seat count must be fresh

   Starting a subscription needs a seat-count snapshot whose cutoff is within the last 48 hours. While one is being produced the console tells you the seat count is being computed — the platform reports the count daily while an organization is unsubscribed — so try again once it is ready.

4. Complete Stripe Checkout

   Complete the Stripe Checkout session and return to the console. There is one open attempt per organization at a time, and duplicate completions converge to the same subscription.

1. Open the Stripe billing portal

   In the console, Billing → Manage billing calls POST /console/v1/billing/portal-session with an empty body ({}) and returns an ephemeral Stripe billing portal URL. From the portal you can update your card, view and download invoices, and cancel the subscription. The request needs your session cookie and the same-origin request header the console sends for you.

2. If you see a 409

   A 409 means the organization has no live billing binding yet — you are still on a trial, so there is nothing to manage in Stripe. Subscribe first.

3. Paid grace after a lapse

   A paid subscription has a 14-day grace window after a term ends. The panel reports in_grace: true while active stays true through that window. After grace, access is fail-closed until the subscription is reactivated.

GET /console/v1/billing reads the billing state for the session organization and returns the fields below. The trial block is present only while you are on a trial, and the seats block only once a per-cycle snapshot has been reported.

Status codes for GET /console/v1/billing:

Status codes for POST /console/v1/billing/portal-session:

POST /console/v1/org/deletion requests deletion of your organization, and GET /console/v1/org/deletion reports the state of that request. Deletion is a request that we process — it is not automatic and not immediate.

Cancel any billable Stripe subscription first: a deletion request will not complete while a subscription is in a billable state (incomplete, trialing, active, past_due, unpaid, or paused). Use the billing portal to cancel, then request deletion.

For a billing question, submit a support message from the console (POST /console/v1/support). You can also reach us through contact. A data processing agreement covers the hosted platform — see the DPA. To return to the rest of the platform documentation, see all docs.

There is no availability SLA and no high availability guarantee for the hosted platform. We do not offer BYOK or bring your own key billing.

We do not expose an invoice-PDF API — invoices come from Stripe and the billing portal. Billing is monthly only: there is no yearly or fixed-term prepayment, and no price other than the volume-band table above applies.

Get early access to the platform.

Every product is included in one platform subscription. Request early access and we'll onboard your team hands-on — free while we build toward launch.