Codapult is sold as a one-time license to the full template source code. Plans differ by how many SaaS products you may ship, how long you receive updates, and support level — not by which modules are included.
Same code in every tier
Starter, Pro, and Enterprise all include the same full template: auth, payments, teams, admin, AI, SSO, infrastructure templates, and documentation. You are not buying a lite edition.
What counts as a project?
One project means one SaaS product you ship: one brand and one deployed app.
- A separate staging environment or a major rewrite of the same project still counts as one project.
- Starter: 1 project
- Pro: 3 projects
- Enterprise: unlimited projects
This is a license limit, not a code restriction.
What you may do
| Allowed | Examples |
|---|---|
| Host and sell your SaaS | Subscriptions, usage billing, seats, one-time access |
| Client work | Build client products when your tier covers the project count |
| Modify the code | Customize architecture, swap providers, self-host |
| End users | Your customers do not need a separate Codapult license |
What you may not do
| Not allowed | Examples |
|---|---|
| Resell the template | Selling source access, starter kits, or boilerplate packages |
| Redistribute source | Sharing private repo access, archives, or license keys |
| Competing boilerplate | White-label template resale or a “nearly the same” dev kit |
Rule of thumb: you may sell access to your SaaS; you may not sell access to Codapult’s source.
The full legal terms are on the marketing site at /terms (Sections 4 and 6).
Updates
Updates are delivered through a private Git repository. Pull from upstream or use the Codapult CLI update workflow.
| Tier | Update period |
|---|---|
| Starter | 6 months |
| Pro | 12 months |
| Enterprise | Lifetime |
After your update period ends, your code remains yours — you simply stop receiving new upstream commits until you renew or upgrade.