Billing
FeatureMesh Cloud bills each org in units: one unit is $20 and covers one member for one month with 2,000 queries. Orgs prepay units, and the monthly bill is taken from that balance.
Billing follows the access model : the org pays for everyone working in its projects and the org's OWNER and ADMIN members manage it. Your personal org has no monthly fee: you only pay for queries above its free allowance.
Who counts
A member is a user or a service account that ran at least 10 queries in the org's projects during the month. Someone with access who ran fewer is inactive that month: their queries are free and they cost nothing.
- A user counts once per org, however many of the org's projects they work in.
- Project-only members count: a
READ_ONLYuser of one project is a member of its org for billing. - Each service account counts as its own member.
- Someone working in two orgs is billed by both, each for its own usage.
A query is a FeatureQL query, or SQL with embedded FeatureQL (hybrid), that FeatureMesh translates successfully, metadata commands such as SHOW DOCS included. These are not counted:
- queries that fail in FeatureMesh: they appear as Free in your query history;
- plain SQL passed through unchanged;
- real-time serving traffic, including the serving engine's own catalog checks.
What happens when your client runs the translated SQL afterwards does not change the count.
How a month adds up
Each member brings their own allowance of 2,000 queries. Allowances are not shared: a light user's unused queries do not cover a heavy one. What goes above each member's own allowance is pooled across the org and billed as extra units of 2,000 queries.
Members who join or leave during the month pay pro-rata, using the higher of two fractions:
- their time: days as a member out of the days in the month, counting from the day they accepted the invitation;
- their queries: queries out of 2,000, capped at one unit.
Their allowance follows the same fraction. The org total is rounded once, at the end of the month, to the nearest unit (halves up). A month that rounds to zero costs nothing.
Take a 30-day month in an org with four members:
| Member | Membership | Queries | Fraction | Above allowance |
|---|---|---|---|---|
| Alice | all month | 3,500 | 1 | 1,500 |
| Bob | joined on day 21 (10 days) | 200 | 0.33 | 0 |
| Carol | left on day 6 (6 days) | 1,200 | 0.6 (queries beat time) | 0 |
| CI service account | all month | 4,000 | 1 | 2,000 |
The fractions add up to 2.93 units and the pooled overage is 3,500 queries, or 1.75 units: 4.68 units in all, billed as 5 units ($100).
Personal orgs
A personal org has no base fee and no pro-rata. You and your service accounts share one allowance of 2,000 queries a month; only the queries above it are billed, at $20 per 2,000 queries, rounded to the nearest tenth of a unit ($2) at the end of the month.
| Queries in the month | Above the free 2,000 | Billed |
|---|---|---|
| 2,099 | 99 | nothing |
| 2,100 | 100 | 0.1 unit ($2) |
| 3,500 | 1,500 | 0.8 unit ($16) |
| 6,000 | 4,000 | 2 units ($40) |
Service accounts do not bring their own allowance here: an owner with 1,500 queries and two service accounts with 1,000 each uses 3,500 queries of the shared allowance, and pays 0.8 unit. The same activity in a team org would be three members, so 3 units.
Balance and credits
Units you buy or receive are credits. Each batch of credits is valid for 24 months, and the month-end bill always uses the batch that expires first.
The balance can go negative: nobody is blocked when the credits run out. The missing units are settled first from the next credits added.
Paying
Everything happens on the org's Billing page in the console (dashboard → org menu → Billing). It is open to the org's OWNER and ADMIN members.
- Buy units: a one-off purchase of any number of units, paid through Stripe.
- Monthly reload: a subscription that adds a fixed number of units every month. Changing the number applies from the next renewal; cancelling and payment methods are handled in Stripe.
- Coupons: codes from FeatureMesh that add free units, for example for a trial. Each coupon works once per org.
The same page shows the estimate for the month in progress, usage per member for the last twelve months, remaining credits, and the full history of credits and charges. Invoices come from Stripe.
Your own usage
The Usage page of the console (left menu) shows one allowance at a time, picked in a selector:
- Personal: you and the service accounts of your personal org, sharing one allowance;
- each team org you belong to: your own queries and allowance there;
- each service account you own in a team org: its own queries and allowance.
For the selected allowance and billing month (the current month to date, or one of the 12 before it), it shows the queries, the allowance of the month, how many queries were included or above it, a chart per day, and the query history newest first with the text of each query. Each query is marked Included or Above allowance, in the same order the bill counts them.
The query history is separate from billing: it keeps the text for 30 days only, and you can delete one entry or clear it all. Deleting history never changes your usage or your bill.
What is recorded
To compute and justify the bill, FeatureMesh keeps:
- for each counted query: the org, project, member, time, duration, and a fingerprint (hash) of the query text, not the text itself. These records are kept 12 months, then only the monthly totals remain;
- separately, the query history: the text of each query, visible only to the user who ran it (or who owns the service account). It is kept 30 days and the user can delete it at any time;
- monthly totals per member and per org, the history of credits and charges, and when each member joined and left the org. These are kept as accounting records;
- purchases and coupon redemptions, with who made them, in the org's audit log .
Card details are held by Stripe and never reach FeatureMesh.
Next
- Access management — orgs, projects, roles, and invitations
- Managing access from Python — the
AccessClientcalls for members and service accounts