Organization plans

An organization’s plan sets what it pays, not what it can do. There are no feature tiers: a one-person paid organization and a 250-person one run exactly the same platform, and only the price differs. Any Owner or Admin can view and change the configuration from Settings → Billing, section Plan & seats (/gravity/organisation/detail?tab=billing&section=plan).

For exact prices, see sencai.space/pricing - this page covers how the price is put together, not what it costs. The one rate it states is the price of a hosted CI minute above the included ones; see Hosted CI minutes.

What the price follows

There is no base fee and no package to choose. An organization’s price is a single continuous curve built from three things:

• Managed resources - the main driver, and the one most organizations feel first. The first five are free; you pay only above that.
• Automation scope - how much of running those resources you hand over to the platform. Three levels: no automation (Sencai watches, measures, and alerts, and every change stays in your hands), standard (patching, backups, and routine runbooks run on a schedule and report back), and advanced (policy-driven remediation across the fleet, with approvals and a full record of what changed).
• People beyond the included allowance - the automation level you pick prepays for a number of people: one with no automation, more as you automate. Past that allowance each person is priced on the same curve.

Each organization is priced on its own, so if you run several, the figures add up. Most companies need one.

What counts as a managed resource

One compute instance, managed database, storage bucket, or DNS zone that Sencai is actively managing for you counts as one. Resources you’re only tracking in inventory without managing don’t count. See Core concepts for the distinction between an inventory item and a managed resource.

The free configuration

One user, one organization, five managed resources, and 30 hosted CI minutes a month cost nothing - no card and no time limit. On the pricing curve, a free organization is priced at no automation - patching, backups, and scheduled runbooks are what you’re paying for above the free configuration, not a switch the platform throws once you pay. Patching and scheduled runbooks aren’t gated by plan at all, so a free organization can set them up and run them exactly like a paid one. Automated backups are a separate story: Apply Now, the step that actually configures snapshots at your cloud provider, isn’t switched on in any environment yet, so no organization - free or paid - can complete it today; see Applying a policy. The decided direction is that two specific capabilities are switched off by plan, until an organization moves to a paid one - AI, and the audit log along with the Auditor role that reads it:

Free includes	Free does not include
One user	AI of any kind (see Seats & personal plans)
Five managed resources	The audit log and the Auditor role that reads it
The core platform - inventory, monitoring, alerting, patching, backups, and scheduled runbooks	RoPA records for GDPR Article 30 (Privacy)
One organization, owned free
API keys and AI agents - read and write, same as a paid organization
30 hosted CI minutes a month, as a hard limit

Note

The Auditor role is refused in a free organization on every path that assigns it - an invitation, a role change, accepting an invitation, or approving a request - with a message that the organization needs a paid plan. Known issue: splitting part of a paid organization off into a new one doesn’t check this yet, so an Auditor moved by the split keeps the role in the new, free organization. The audit-log restriction is rolling out gradually and isn’t switched on everywhere yet - where it isn’t, a free organization can still read and export its own audit log like a paid one.

The first thing you pay for is your sixth managed resource, or your second user. You may own only one organization on the free configuration at a time, regardless of which personal plan you’re on - a second organization you own needs a plan of its own. See Seats & personal plans for what a personal plan governs instead.

Every paid plan includes the whole platform

Nothing is held back for larger customers. Once an organization is on any paid configuration, it gets the full product - the browser SSH terminal and just-in-time elevation, SSO with Entra ID or Google Workspace and SCIM provisioning, the policy engine and governance scoring, NIS2 evidence reporting, the private registry, security scanning, and the full FinOps surface including forecasting and multi-cloud comparison.

Note

Two things that sound like tiers are not. Service levels are agreed in your contract rather than unlocked by spending more - see Service levels. AI is bought per person on a personal plan and is never part of an organization’s price, though an organization can pay for its people’s plans - see Personal plans.

Hosted CI minutes

Hosted runners are metered in CI minutes, separately from the price curve above. Every organization has an allowance of them for each calendar month (Europe/Prague time):

Organization	CI minutes each month
Free configuration	30, a hard limit: when fewer than 5 are left, jobs wait for the next month
Paid	1,000 for the organization, plus 200 for each Plus seat, 500 for each Max seat and 1,500 for each Pro seat

The paid allowance follows what you pay for, day by day, the way the price of seats does. The 1,000 minutes are prorated by the days of the month on which the organization was paid, counted from the day Sencai has confirmed its payment, and the minutes of a seat by the days the seat is billed. Every member of a paid organization holds at least a Plus seat, so a paid organization with five members, all on Plus seats, has 1,000 + 5 × 200 = 2,000 minutes for a whole month.

A paid organization can use more. A minute beyond its allowance costs 0.016 EUR per minute, VAT excluded, billed starting with November 2026 (nothing is charged for extra minutes yet), up to an overage cap that its billing owners set: 1,000 minutes a month by default, any whole number from 0 to 100,000, where 0 means jobs wait instead. A free organization is never charged.

What counts as a minute, what happens when they run out, and who sees the figures are on Hosted runners.

Assigning Auditor has a price to confirm

The Auditor role is the one role assignment that changes your bill: a monthly per-auditor add-on, prorated daily, for as long as they hold it - see sencai.space/pricing for the current amount. It exists only on a paid configuration - a free organization is refused before any price is shown (see the note above) - so there’s no discounted or waived version of the price for a small organization. Being introduced: the price is shown and has to be confirmed everywhere, but the add-on isn’t billed yet outside Sencai’s own development environment - it’s recorded, and doesn’t reach an invoice.

Whoever assigns the role sees the price and confirms it before it takes effect, the same way a plan change or a new paid seat does. Two of the three ways to end up assigning it work that way today:

• Inviting someone straight into the role when you hold billing access - the usual case, since Owner and Admin hold it by default - shows you the price and lets you confirm it; the invitation goes out once you do.
• Moving an existing member into Auditor from the role dropdown on the Members tab works the same way: a price to confirm, then the change applies.
• Inviting someone straight into the role when you don’t hold billing access files a real, stored access request for your organization’s billing owners, carrying the invite’s own email and role. Approving it asks the approver to confirm the same price (shown, but not billed yet outside Sencai’s own development environment
  • see above), and then creates the invitation. Being introduced: there’s no screen anywhere in the app to review a request yet, and outside of Sencai’s own development environment the API endpoint that would approve it isn’t switched on, so it answers as if the request did not exist. Filing the request is therefore a dead end for now.

If you don’t hold billing access yourself, ask an Owner or Admin who does to send the Auditor invitation directly instead of going through the request queue - or contact support if that isn’t possible.

What happens when you hit a limit

This only applies to the free configuration, which has three hard ceilings left (see above): five managed resources, one user, and 30 hosted CI minutes a month. Creating a sixth managed resource is refused with a “reached its cloud-instance limit” error, and inviting a second member with a “reached its member limit” error. The error is the same whether the request comes from the app or from an API token; the app’s own instance wizard also stops you before you submit and points you at upgrading, while the member invitation shows only the bare error. Adding billing is the fix either way. Being introduced: instead of refusing, crossing either limit is meant to ask you to confirm moving the organization onto a paid plan (or, without billing access, to file a request for that) - that isn’t switched on yet. Nothing you already have is removed or disabled because you’re at a limit; the block applies only to new creation or invitations.

The CI minutes ceiling works differently: nothing is refused with an error. When fewer than 5 of the 30 minutes are left, a new CI job waits in the queue until the next month starts, or until the organization is on a paid plan and Sencai has confirmed its payment, and the Git host cancels a job that has waited more than 24 hours. Jobs that are already running are not stopped, except by the minutes they started with. See CI minutes.

A paid organization has no resource ceiling, and no people ceiling, to hit at all: creating more managed resources never blocks, it just moves you further along the curve above, and the same is true of adding people. Adding someone past your included allowance prices them on the curve rather than refusing the invitation, and no personal plan - yours or theirs - limits how many members a paid organization may have. Hosted CI minutes are the exception: a paid organization has the ceiling it sets itself, its overage cap (1,000 minutes a month unless a billing owner changes it). At the cap, new CI jobs wait until the next month, or until a billing owner raises the cap.

Separately from your Sencai bill, you can set a ceiling on what you spend with your own cloud providers; see Spend caps for what that screen does and does not enforce today.

Changing your configuration

There is one plan model - Free or Paid - and you move between the two from Settings → Billing → Plan & seats:

• On a Free organization, Preview price shows an estimate of the monthly total including VAT without committing to anything, and Upgrade to paid moves the organization onto the Paid configuration. Without billing access the button files a request to the people who hold it instead.
• On a Paid organization, Return to Free schedules the move back; the page shows the date it takes effect, and Cancel scheduled return undoes it until then.

Past that, the price follows what you actually run - more managed resources, a different automation level, more people - so there is no separate step for “changing tier”. Per-person seat tiers are assigned in the seat list on the same section; see Seats & personal plans. The platform won’t silently delete resources or remove members to fit a smaller configuration.

There is no longer a way to pick a named tier, switch between named tiers, buy add-ons, or compare tier cards. To stop paying, use Return to Free; see Payment, invoices and failed payments for what that does and doesn’t do to your data. The old addresses /gravity/settings/subscription, /gravity/settings/billing and /gravity/settings/upgrade redirect to this section.

Who can change the plan

Changing the plan, and everything else in the Billing area, requires the Owner or Admin role. An organization can additionally restrict a specific Admin’s billing access to read-only through a per-resource permission override - see Roles & permissions.

What’s next

• Billing overview - how organization and personal plans fit together
• Seats & personal plans - where AI is bought, and how a paid organization pays for each member’s seat
• Payment, invoices and failed payments
• Hosted runners - what counts as a CI minute, what happens when they run out, and who sees the figures
• Service levels