What your plan counts
A DataMaker Cloud plan keeps four meters, and only one of them can stop anything you are already doing. This page is the whole list, so you can tell at a glance which figures change what you pay or what you can do, and which are only ever counted.
The meters your plan is priced on
| Meter | What happens at the allowance |
|---|---|
| AI credits | AI-assisted features pause until the next calendar month. See AI usage and credits. |
| Seats | Nothing is blocked. Seats past the included allowance are billed rather than refused, so nobody is locked out of a workspace they were invited to. |
| Core systems | Nothing is blocked. You declare your systems, and going over is an account-review conversation. See Core systems. |
| Workspaces | A new workspace is refused once the plan’s workspaces are all in use. Every workspace you already have keeps working. |
What is never counted against your plan
Generation and everything downstream of it is sold as unlimited. None of it is capped, throttled or billed by volume:
- rows generated
- scenario runs
- data jobs, including loads that move millions of rows
This holds even while the AI allowance is spent. The pause reaches AI-assisted features and nothing else, so a workspace out of credits keeps generating data and running scenarios and data jobs exactly as before.
What DataMaker records anyway
Unlimited does not mean uncounted. DataMaker keeps a running monthly total, per subscription, of:
- scenario runs started
- rows generated, whether from the generate endpoint or from a data job
- data jobs created
Rows a data job moves are counted as each chunk finishes rather than when the job ends, so a load running for hours is visible while it runs.
These totals exist for capacity planning and for checking that a plan is priced correctly for how it is really used. They are deliberately absent from your workspace: showing you a meter you are not charged against invites you to wonder whether you might be. Automators can share the figures for your subscription at a review.
Recording happens after the fact and never gates a request. A total that fails to be written cannot fail the run it was counting, and no figure here can refuse one.
Where an Enterprise agreement covers several workspaces, these totals pool across them, exactly as credits and seats do.