A spec sheet you can hand off.
Configure hosting in the estimator or the selector and it turns into this: line items with their codes, one monthly total, the terms, and a permalink — paste it into an approval thread, or print it as a clean PDF.
No configuration yet.
This page renders the exact configuration carried in its own link — there’s nothing to show until one exists. Build one in the estimator or the selector; each one hands you a “spec sheet” link back to this page, filled in.
Your configuration
This is an estimate, not a contract or an invoice — every value below is recomputed from the posted rate card, never carried in the link itself.
| Code | Item | Detail | Rate |
|---|---|---|---|
| Total | |||
What's included at every tier
The same for a $5/mo static site and a bespoke stack — nothing on this list is an upsell.
- TLS certificates
- DNS management
- Daily backups
- Monitoring & alerts
- Security patching
- A human who answers
The terms, in writing
Nothing here is negotiated per client — it's the same posted terms behind every rate on the site.
- Rate
- Flat, monthly — no per-request or usage billing
- Lock-in
- None — every stack is defined as code and fully portable
- Handover
- Full and documented, free at any time
- Rate changes
- 30 days’ notice, posted — never a surprise invoice
- Response time
- < 1 business day on any quote request
What "Iteration — CodeHerder" buys
The AD-CH line on the sheet above, explained where it matters — in front of whoever is deciding whether to pay for it.
CustomLabs designs and builds the first version of whatever this spec sheet is pricing. Because it then runs on this hosting and is defined as code, CodeHerder's agent can keep iterating on it directly once it's live: brief a change in plain language — a typo, a new pricing tier, a section rewrite — and the agent opens a pull request against the real repo. The same pipeline that shipped the first version ships the merge, once it's reviewed.
It's a flat add-on, not metered by how many changes you brief — add it here, or add it later once you see how much you're touching the site after launch. See exactly what that does to an invoice on Billing.
See how the loop works →What happens next
- 01
Build a configuration
In the estimator or the selector — either one hands you a link back to this sheet.
- 02
Share it, or print it
Paste the permalink into an approval thread, or print to a clean, chrome-free PDF.
- 03
Request the quote
Same configuration, one click over — you get a fixed monthly rate in writing within a business day.
Straight answers on the sheet itself.
01Is this a quote?
No. A quote is the fixed number you get in writing after you request one — this sheet is an estimate, built from the same posted rate card, so you can see the number before you ask for it.
02Will the price change?
Every line on this sheet is recomputed from the live rate card each time the page loads — nothing is carried or cached in the link itself. Posted rates only change with 30 days’ notice.
03Can I send this to a client?
Yes — that’s what the permalink is for. Paste it into an approval thread or print it to PDF, and whoever opens it sees the exact same configuration and total, no login or form required.
04What is the iteration line?
The Iteration — CodeHerder add-on (AD-CH). It keeps a site or app shipping small changes after launch — see the section below, or the full story at /loop.
Keep exploring
- Which do I need?
Answer three questions, get a hosting-shape recommendation — then open it as a spec sheet.
- The estimator
Pick a plan and add-ons, watch the rate update live, then copy the spec sheet link.
- The loop
What CodeHerder’s agentic iteration actually does once you’re live.
- Access
Who can actually merge, deploy, and roll back the configuration this sheet describes.
Ready to see your own number?
Tell us what you're running — one fixed monthly rate, within a business day.