Usage and billing

clf.fit(train, target="churned")   # 200 000 input rows
clf.predict(test)                  #  50 000 input + 50 000 output rows

Hollerith meters input and output rows for successful jobs. Input rows are rows a job processes; output rows are prediction rows returned. Free applies separate input and output allowances. Paid plans combine both as billable rows.

Pay for what you use

Job	Input rows	Output rows
`fit`	training rows	0
Inline `predict`	training rows + scored rows	scored rows
Context-backed `predict`	scored rows	scored rows
`evaluate`	rows in the frame	0
`forecast`	context rows + horizon rows	horizon rows

clf.fit(train, target="churned", evaluate=True)   # 2 jobs, 400 000 billable rows

Example

A context-backed predict counts only the rows to score as input because the fitted context is already stored. Input and output row counts are therefore equal. On 200 000 training rows and 50 000 rows to score:

fit        input 200 000   output      0    ->  200 000
predict    input  50 000   output 50 000    ->  100 000
                                     total      300 000

The fit is paid once. Each predict against that context pays twice its own batch. Free shows separate input and output meters. Paid plans show their combined billable rows.

Plans

Plan	Included rows per billing period
Free	1 000 000 input + 100 000 output
Cloud	1 000 000 billable
Scale	3 000 000 billable
Enterprise	10 000 000+ billable

Allowances are organization-wide: every key, member and job kind draws on the same counters. Free applies its input and output allowances independently. Paid plans pool both counters. Plans are not self-serve. A Hollerith administrator provisions changes (see Request higher limits). An owner of a Free organization can add a payment method, enable paid overage and set a monthly dollar ceiling.

Overage and credits

Spend order is fixed: included allowance first, then organization-level dollar credits, then paid overage. Overage is off by default. With overage off, jobs stop as soon as the plan’s input or output cap or the daily quota is exhausted, whichever comes first, not when the billed pooled total in the table above is crossed. Enabling overage and setting a monthly dollar ceiling lets jobs continue past the included allowance, drawing on credits first and then paid overage up to that ceiling.

Daily quota

Quota	Value
Calls	10 000
Input rows	1 000 000
Reset	00:00 UTC

The daily quota counts input rows only. Output rows bill but do not draw on it. A context-backed predict of 50 000 rows spends 50 000 of quota and bills 100 000. Quota is reserved when a job is submitted and released when it completes, so a burst of submits can hit quota_exceeded before any of them runs.

Request higher limits

If you need higher usage than your plan includes, email founders@monarcha.ai with the volumes you have in mind.

Get started

Guides

Reference

Account

Help

Pay for what you use

Example

Plans

Overage and credits

Daily quota

Request higher limits

Next steps

Limits

Data handling and retention

​Pay for what you use

​Example

​Plans

​Overage and credits

​Daily quota

​Request higher limits

​Next steps

Limits

Data handling and retention

Pay for what you use

Example

Plans

Overage and credits

Daily quota

Request higher limits

Next steps