One number, and what can move it.
Every plan on the rate card is a flat monthly rate. This page is the rest of that promise: what a month actually looks like, a real specimen invoice, and the short, honest list of the few things that can change the total.
The month, start to finish
Four steps. The same four, every month.
- 1
The quote, in writing
A fixed monthly rate for the plan, any add-ons, and a database if one is attached — sent back within a business day.
- 2
The rate is fixed
The number in the quote is the number on the account. It does not move with traffic or how much the service gets used that month.
- 3
One invoice, issued monthly in advance
Billed at the start of the cycle it covers, itemised by plan, add-on, and database.
- 4
The same number next month
Nothing on the account changes the total unless you change something, or a posted rate change takes effect.
A specimen invoice
One example configuration: Static Pro, Iteration — CodeHerder loop, and DB Standard. It is priced the same way the estimator and the spec sheet price it. This is a specimen for illustration, not a real customer's bill.
| Line | Detail | Rate |
|---|---|---|
| Static Pro | Multiple sites & environments · staging · redirects/headersFair use: ~500 GB transfer/mo | $15/mo |
| Iteration — CodeHerder loop | Brief a change in plain language, an agent opens a PR, the same pipeline ships it. | +$25/mo |
| DB Standard | Postgres · 2 GB RAM · 40 GB storage7-day PITR | +$25/mo |
| Total, this specimen | $65/mo |
Build your own on the Pricing estimator, or hand one off with Spec sheet.
What moves the number, and what never does
A short list on the left. A longer one on the right, on purpose.
Moves it
Adding a plan, add-on, or database
The new line appears on the next invoice, at its posted rate.
Removing a plan, add-on, or database
The line drops off the next invoice — see "Changing something, mid-cycle" below for exactly when the change takes effect.
Changing tier
Moving between tiers works the same way as adding or removing a line: the new rate appears on the next invoice.
A posted rate change
Rates can change, with 30 days' notice before a new one takes effect on your account.
Tax, where it applies
Shown as its own line on the invoice — never folded into the rate itself.
Never moves it
A traffic spike
The rate is flat, up to the fair-use allowance set out below.
How many deploys you ship
Deploys are not a metered event on this platform.
How many changes you brief to the agent
The iteration add-on is a flat monthly line — see the tie-in section below.
A restore
Pulling a backup back in is part of the service, not a billable event.
A support request
Writing in through the quote channel costs nothing extra, however many times you do it.
Patching, or a certificate renewal
Routine maintenance the rate already covers.
An incident, or a rollback
Both are handled at no extra charge — see the service-credit ladder below for when an incident moves the number the other way.
Fair use, in numbers
A named allowance, not a hidden ceiling — and never a charge applied after the fact.
Static Starter
~100 GB transfer/mo
Static Pro
~500 GB transfer/mo
- 1
We notice
Usage sits near or above the allowance for more than one billing cycle.
- 2
We reach out
Through the quote channel, before anything on the account changes.
- 3
You choose the plan that fits
Move to a plan sized for the real workload, or talk through what is driving the transfer.
Dedicated plans work differently: they're bounded by the compute and storage of the instance itself, not a transfer allowance. See the Acceptable Use Policy for the full fair-use clause.
Changing something, mid-cycle
Adding, moving tier, or leaving — the same simple rule, each time.
Add or remove a line mid-cycle
The capability switches on or off the day you ask. There is no pro-rated charge and no pro-rated credit — the invoice simply looks different next cycle.
Move between tiers mid-cycle
The same rule applies: the new rate appears on the next invoice, not a partial charge on this one.
Cancel
Either side can end the service at any time. It stops at the close of the current monthly cycle, with no early-termination fee.
Take your stack with you
A documented handover is free, any time — see Portability for the full pack.
When we owe you
The Service Level Agreement is the binding text — this is its credit ladder, as a table.
| Monthly uptime | Service credit |
|---|---|
| Below 99.9% monthly uptime | 10% of that month's fees |
| Below 99.0% monthly uptime | 25% of that month's fees |
| Below 95.0% monthly uptime | 50% of that month's fees |
Credited to a future invoice, never paid out as cash. Claim through the quote form within 30 days of the incident — see SLA for how a claim is worked, and Status for the live incident history.
What "Agentic iteration — CodeHerder" does to the invoice
The honest answer to a fair question: does an agent that can open any number of pull requests produce a variable bill?
No. Agentic iteration — CodeHerder is a flat monthly line, the same as every other add-on on the rate card. An agent that opens twenty pull requests in a month costs the same as one that opens two — the line is priced per month, not per change.
One line stays separate from the hosting invoice: a net-new build. Designing and building the first version of a site or app is CustomLabs scope, quoted on its own before the work starts. Once it's live and hosted here, iterating on it through the loop is the flat add-on above — never metered by how many changes you brief.
See how the loop works →Read a brief in full on Brief a change, three real examples on Case files, or price a specific configuration on Spec sheet.
Billing questions
The anxiety questions, verbatim, answered from the clauses above.
01How do I pay?
The invoice carries its own payment details and a due date. Anything unusual — a purchase order number, a specific invoicing address — can be asked for on the quote form.
02Can you put a PO number on it?
Ask on the quote form. A purchase order number is the kind of detail an invoice can carry once you tell us it is needed.
03What if I go over the transfer allowance?
We reach out first — see "Fair use, in numbers" above. Nobody is billed for crossing a fair-use allowance without a conversation first.
04Do I get a refund if I leave mid-month?
No. The service runs to the close of the current monthly cycle, with no early-termination fee, but the current month's fee is not refunded.
05Does briefing more changes cost more?
No. Agentic iteration — CodeHerder is a flat monthly line — an agent that opens twenty pull requests in a month costs the same as one that opens two.
06Do you charge for a restore, or for support?
No. Both are part of the service the rate already covers, however often you need either.
07Does junk traffic — a bot or a scraper — count against my transfer allowance?
Yes, the same as any other traffic. Nothing on the platform tells a scraper from a real visitor before it hits the allowance. If usage sits near or above it, we reach out first — see Under attack for the full answer, including this site's own defences.
What billing connects to
- Pricing
The rate card this page bills from — what each plan, add-on, and database tier costs.
- The hours ledger
The same monthly arithmetic, run on your own time instead of your invoice.
- Spec sheet
The line-item sheet for any configuration — the specimen invoice above is one real example of it.
- Portability
The free handover pack this page names under "Changing something, mid-cycle", in full.
- SLA
The binding text behind this page's service-credit ladder.
- Terms
The binding text behind the billing cycle and cancellation terms on this page.
- Glossary: Money & billing
Plain-English definitions for every billing term on this page.
- Scaling
The rest of "changing tier" from this page's ledger: the ladder, the move minute by minute, and what a visitor sees.
- Under attack
What junk traffic — a bot or a scraper — does to the flat rate and the fair-use allowance on this page.
Want the number for your own workload?
Describe what you're running — a fixed monthly rate comes back in writing, within a business day.