Plans and billing
Seylo charges for the platform by the size of what it manages - a fee per managed vCPU - and nothing for people: add as many as you need. Nightshift is billed per verified fix and the coding agent per seat. A cluster you let Seylo manage savings on adds 5% of the saving Seylo measures there. Everything is metered from the first day and shown to administrators and billing managers on the Billing page, so you can check every figure you are billed against.
Prices are in US dollars (USD), excluding any applicable tax, and invoiced by Seylo Labs Private Limited.
Paid from the first day
Section titled “Paid from the first day”There is no free preview and no standard trial. An organisation is on a paid plan from the day it is created, and its measured usage is shown on the Billing page from that day.
- The whole product, with unlimited clusters: deployments and approvals,
observability, dashboards and alerts, cost,
seylo-mcpand Nightshift. - Unlimited people, at no charge.
- The coding agent is paid per seat, before use - see coding agent seats.
A 30-day free trial, on request
Section titled “A 30-day free trial, on request”Seylo may grant your organisation a 30-day free trial. Write to
support@seylo.in to ask for one. It covers the platform fee and
Nightshift. It does not cover coding agent seats, which are paid before
use as always.
If changes are blocked
Section titled “If changes are blocked”Seylo stops changes, not reads. Existing deployments keep running, and
everything you already have — clusters, history, audit — stays readable. Any
action that would change something returns HTTP 402 with a code and a message
that says why: suspended for a suspended organisation, or trial-expired
with the date a free period ended.
The Billing page
Section titled “The Billing page”Admin → Billing, for administrators and billing managers. One page, five sections - Plan, Upcoming bill, Invoices and payment, Usage, Credits - for one calendar month at a time (UTC). Previous and Next move between months. The facts are on screen; the explanation behind each one (where a figure comes from, a price’s source, what the plan includes) is behind the (i) beside it.
Who can see it: the billing manager role
Section titled “Who can see it: the billing manager role”Administrators always see Billing. To let someone else see it - your finance team, say - without giving them anything else, make them a billing manager:
- Local accounts: an administrator ticks Billing manager on their row under Admin → Access → Accounts. Their other roles stay as they are. An account can also be created as billing manager only.
- Single sign-on: map a group from your identity provider (for example
finance) tobilling_managerin the role map, or assignbilling_managerto a person under Single sign-on → Users.
A billing manager sees the Billing page and no other administration page. Someone
who is only a billing manager opens Seylo straight onto Billing; give them
viewer as well if they should also see your clusters. The role takes effect
the next time they sign in. Taking it away signs them out, so it applies at once.
Granting and removing the role are both recorded in the audit log.
What your plan is (and, during a free trial Seylo granted, until when it is free), the amount due for the month, and how many people you have (there is no limit on people and no charge for them). What the plan includes is in the (i).
Usage this period
Section titled “Usage this period”What Seylo measured for the month. The (i) beside each line says where the number comes from and how it is measured. Show days opens any line to its day-by-day figures.
| Line | What it is |
|---|---|
| Managed vCPU | The month’s average of the daily 24-hour averages of CPU requests in managed namespaces (see below) |
| Managed GPUs | Not measured yet - the page says so rather than estimate |
| People active | People who signed in or used Seylo this month - for information; people are not charged |
| Nightshift verified fixes | Changes Nightshift applied that passed their check |
| Coding agent seats | Seats paid for this month, each for a named person |
| Coding agent sandbox minutes | Time the sandboxes ran; time asleep is not counted. Your monthly limit is shown beside it |
| Tokens on Seylo’s model | Tokens as the provider reported them, for calls Seylo’s model answered |
| Tokens on your own model key | The same for calls sent with your key - your provider bills these, Seylo does not |
Below the lines, Model use by purpose and model breaks the calls down by what they were for (investigations, sessions, model tests) and which model answered.
A line Seylo could not measure says Not measured and why. It is never shown as zero.
Upcoming bill
Section titled “Upcoming bill”Each line is a measured quantity times a published price, with the
arithmetic beside the amount (for example 37.5 vCPU x $5). The (i) beside
the price says whether it is Seylo’s list price or the rate agreed for your
organisation, and where it comes from.
A line without both a measurement and a price says why instead of showing a number - Unpriced, because … or Not measured - and the total says which lines it leaves out. Today that applies to:
- Coding agent minutes beyond those included with a seat: not set yet, so nothing is charged for them.
- GPUs: not measured and not priced.
During a free trial Seylo granted, the platform fee and Nightshift are not charged. The page shows what the month would cost at the list prices, labelled not charged.
Coding agent seats are not on the monthly bill: they are paid before use, and each seat payment has its own invoice.
Credits
Section titled “Credits”Credits are prepaid US dollars for Seylo’s model beyond what your plan includes. They are not available yet; the section says so. It never shows a balance of $0 in place of “no credits”.
Invoices and payment
Section titled “Invoices and payment”- On the 1st of each month, Seylo issues the invoice for the previous month’s platform fee and verified fixes, from the same bill this page shows: the same lines, the same prices, the same total. A line without a price is not on the invoice. The invoice is emailed to you with a payment link, and here it has a PDF and a Pay button.
- A coding agent seat payment gets its own invoice, already marked paid.
- Payment is due within 30 days of the invoice date.
- Payment is through Razorpay: Pay on this page opens Razorpay’s own checkout over the page, and the emailed link goes to the same payment. You enter your card there, not on Seylo’s page: Seylo never sees or stores card details. It keeps only what the provider reports for display, for example “Visa ending 4242”.
- After you pay, the invoice shows Confirming for a moment, then Paid once the provider confirms the payment to Seylo directly.
- If the bank declines the card, the reason is shown and the button offers to try again. Nothing is charged for a declined attempt.
- Admins and billing managers can pay. Other roles do not see Billing.
Billing details - your registered name, billing address and country - are needed before an invoice can be issued. The country decides the tax on the invoice.
People: free, and no limit
Section titled “People: free, and no limit”There is no charge for people and no limit on how many you add, on any plan, a free trial included. Seylo is priced on what it manages, not on how many of you use it. People active on the Billing page is shown for information only.
Platform fee: $5 per managed vCPU per month
Section titled “Platform fee: $5 per managed vCPU per month”A managed vCPU is the CPU your pods request in the namespaces Seylo manages. It is not the size of your nodes.
| What is counted | CPU requests of the containers of Pending, Running and Unknown pods |
| Where | Namespaces Seylo manages: those your cluster’s policy lets Seylo change |
| How it is averaged | A 24-hour average each day (sampled every 5 minutes), then the mean of those days across the month |
| A partial month | A first or last partial month is charged for the days it covers |
| Price | $5 per vCPU per month |
Why an average and not a peak: a peak would let one autoscaler burst or one CronJob set the month’s bill.
Why requests and not nodes: a namespace-scoped agent cannot read Nodes, and in a shared cluster node size would bill your namespaces for every other team’s workloads.
What is not counted
Section titled “What is not counted”These are left out deliberately, and each can only make the figure lower:
- Finished pods (Succeeded or Failed).
- Containers with no CPU request. They count as zero; Seylo reports how many there are per cluster.
- Init containers.
- Namespaces Seylo can see but may not change.
Where the number comes from, and when there is none
Section titled “Where the number comes from, and when there is none”The figure is read from kube-state-metrics, which the seylo-observability
chart installs in your cluster, through the agent. Admin → Integrations →
Observability stores shows the exact helm install command for the chart.
A cluster without the chart has no reading and is shown as not measured. Days on which a cluster could not be read are left out of the month’s mean rather than counted as zero, and Show days on the vCPU line lists each day with how many clusters it covers.
Check the figure yourself
Section titled “Check the figure yourself”Run this on the Metrics page of the cluster. It is the query the meter uses for “now”; the daily figure is its 24-hour average.
sum by (namespace) (kube_pod_container_resource_requests{resource="cpu"} * on (namespace, pod) group_left() max by (namespace, pod) (kube_pod_status_phase{phase=~"Pending|Running|Unknown"}))Seylo then keeps only the namespaces it manages. Unit: cores.
Right-sizing lowers the fee
Section titled “Right-sizing lowers the fee”Because the fee is metered on requests, a right-sizing recommendation that you approve and that lowers requests also lowers what you pay Seylo.
Nightshift: $6 per verified fix
Section titled “Nightshift: $6 per verified fix”- The first 5 verified fixes are free, once per organisation, then $6 per verified fix.
- A verified fix is a change that was applied, passed its check and was not undone. A proposal nobody approved and a change that did not hold are not charged.
- The price includes the tokens Nightshift’s investigations use on Seylo’s model, which are never charged separately. Investigations on your own model key are never billed by Seylo: your provider bills those tokens.
Managed savings: 5% of the measured saving
Section titled “Managed savings: 5% of the measured saving”Only for clusters where an admin switched
managed savings on:
- 5% of the saving Seylo measures, per lever. No saving, no fee.
- The saving is measured hour by hour: what the cluster would have run with the values before Seylo’s changes, minus what it actually ran, both priced from the same source. Discounts you buy yourself are never counted.
- Only changes in effect earn, each for at most 12 months, and only while the cluster is managed. Stop managing, or let it expire, and the fee stops.
- An hour with no price earns nothing and is not charged.
- A saving a person approved from the read-only Savings tab is covered by the platform fee, and a change billed as a Nightshift verified fix is never billed again as a saving.
The invoice has one line per lever, for example
Managed savings (rightsizing): 5% of $X measured. A lever with no saving is
a free line and is not on the invoice.
Seylo’s MCP tools (seylo-mcp), including deploying into your cluster
through them, are covered by the platform fee - they are not charged
separately.
Coding agent seats
Section titled “Coding agent seats”The coding agent is $20 per seat per month, paid before use.
- An organisation
adminbuys seats for named people. A seat starts working only once the payment is confirmed. - A seat covers the calendar month (UTC) it is bought for, and is not prorated. Bought on the 20th, it is still $20 and ends at the month’s end.
- Renewal for the next month opens on the 25th. A seat that is not renewed stops at 00:00 UTC on the 1st, until it is paid.
- Each seat payment gets its own invoice, already marked paid.
- Each seat includes sandbox minutes and $5 of Seylo’s model (GLM-5.3) use per month. The model menu in the coding agent’s composer shows each model’s cost as a multiple (×). On Seylo’s model, one call is limited to 200,000 tokens of context and 32,768 tokens of output.
- When the included use is spent, switch to your organisation’s own model key from the same menu. Top-ups are not available yet.
- Tokens on your own key are billed by your provider, never by Seylo.
- Sandbox minutes beyond a seat’s included minutes are not priced yet, so nothing is charged for them.
A free trial Seylo grants does not cover coding agent seats. See the hosted coding agent.
Cancelling
Section titled “Cancelling”Email support@seylo.in from an administrator account of your organisation.
Cancellation takes effect at the end of the current billing month; usage up to
then is invoiced as normal. Prepaid coding agent seats run to the end of the
month they were paid for and are not refunded.
Talk to us
Section titled “Talk to us”Questions about a bill, a 30-day trial or anything on this page: write to
support@seylo.in. Invoices come from Seylo Labs Private Limited.
Volume rates on annual terms are quoted from 200 managed vCPU, against what you actually ran.