For agencies & consultancies
One license. Every client app.
Build for many clients on one organization license — every builder, every client app, priced by the license rather than by per-seat or per-credit usage. Nothing you build, revise or run is metered.
- Fixed price stays fixed
No seats, no credits, no metered runtime — the fifth revision costs what the first did.
- One account, many clients
Multi-tenant per account, isolated row by row, with each client’s branding on their app.
- Show staging, promote on yes
Client-facing environments, one-way promotion, and rollback that keeps the audit trail.
- Hand over without the tail
Governed primitives the platform maintains — nobody inherits a pile of code.
For the person who has to say yes.
Every request authenticated. Promotion gated by RBAC, with versioned rollback. Tenant isolation at the data layer. And the agent builds through named, guarded operations rather than writing code into your backend. That is what twelve years in production buys: speed you can approve.
The full page, in writing
You quote fixed price. The tools you build on do not: a seat for each junior, a credit for each revision, and metered runtime the month a client’s app gets busy. Every one lands on your margin, because the client already signed the number — the mechanics, per vendor, with sources and dates, are on how the category bills (verified 14 Aug 2026).
CodeMonster is priced the way you sell: one organization license, and everything built on it is covered.
Unit economics without the meter
One organization license covers every builder on your team and every app you ship for every client. No tokens. No credits. No meter. You bring the AI subscription you already pay for. Nothing is metered — not the build, not the third revision round, not the client’s live app while their users are in it.
Two things follow. No per-project credit bleed: the fifth iteration costs what the first did, so a fixed-price engagement stays fixed price. And juniors build without asking permission — no seat to justify, no balance to protect. Put the newest person on the client’s intake form and let them iterate.
Run your numbers on the TCO calculator, or read how the category bills before you compare.
Serve many clients from one account
The platform is multi-tenant per account. One account hosts many tenants — one per client — and object data is isolated row by row: every table carries a tenant column, every query is filtered on it automatically, and every data write requires an explicit tenant context or fails fast. Your agent selects the tenant before it touches a record.
To be precise: that is isolation at the data layer inside your account, not dedicated infrastructure per client — say so before the client asks. Each solution carries its own branding, the client’s colors and logo, in the rendered app. Custom domains are not offered yet; every app runs on an HTTPS URL on our domain.
Show the client staging — on custom frontends
↩ rollback · owner / editor / viewer · production is owner-only
Custom frontends move develop → staging → production, strictly one way, and every environment has its own URL. Show the client staging. Promote to production when they sign off. Owners and editors deploy and promote to staging; only an owner promotes to production or rolls it back. Rollback is non-destructive — a new deployment pointing at the last good version, audit trail intact.
That log is your handover document: every deploy, promotion and rollback is an append-only record — version, environment, who, when, result. Platform apps publish in one step, Current → Testing → Production; the gated chain belongs to custom frontends, and we do not blur the two.
Answer the client security questionnaire
The client’s IT lead will ask. The answers: a bearer token validated on every request; an agent that acts with the builder’s permissions, never its own; row-level tenancy; groups that gate screens, actions and grids server-side; a per-solution freeze flag that turns every AI write into a 403. Apps run on managed cloud infrastructure we operate, built primarily on AWS; the backend is not self-hostable — stated up front, not discovered in procurement.
Send them the page written for the person who has to say yes and the compliance status page, which says what is in place, what is on request, and what is not yet documented. A DPA is available on request.
Hand over without the maintenance tail
The question at project close is “who maintains this?” With generated code the honest answer is you — or a client who did not hire you to inherit a repository. On CodeMonster a platform app is governed primitives on rails the platform maintains: auth, environments, permissions, the API. You maintain the app definition; nobody maintains a pile of code.
The client’s data stays theirs — real tables behind a documented REST API, exportable any time. Custom frontends are standard Vite/React repositories they can take anywhere. Platform-built apps run on the platform; that is the trade, and we spell it out so you can repeat it in the room.
Partner program
A partner program for agencies and integrators is forming. What it includes — early access, co-marketing, referral terms — is still being decided, and we will not describe perks that do not exist yet. Read where it stands and apply, or write to partners@codemonster.ai.
Starter prompt
A client portal in one prompt. Swap the nouns for your client’s own and run it.
Use tenant "northwind". Build a solution called Northwind Client Portal.
Objects: Request (title, category, priority, requested by, status, due date); Update (request, author, note, visible to client); Asset (name, type, owner, renewal date).
Create a group "Client Admins" that can create requests and see updates marked visible to client, and a group "Agency Team" that can see and edit everything.
Generate the screens, add a grid of open requests sorted by due date, and add a workflow that emails the agency team when a request is created.
Set the solution branding to the client's primary color and logo.
Preview the diff before you commit, and do not publish yet.See your use case built live.
Thirty minutes with a person, not a form. We scope what you want to build, show it on governed rails, and answer your IT lead's questions in the room. CodeMonster is invite only while we work directly with early adopters. Request an invite and we will meet, scope what you want to build, and get you productive.