The people who use your apps are always free.
You pay for builders and admins, and for what runs — never for the colleagues and customers who use what you build. Start free, go to production at $9 per builder, and move into your own cloud when you are ready.
Free
Shared hosting
Start building, on us. Everything you need to get something real running.
- Up to 5 builders Soon
- $10 starter credit toward consumption — no card needed
- Deploy from a connected GitHub, GitLab or Azure DevOps repo — any framework, real containers
- One region for your organisation
- One build at a time Soon
- 7 days of logs and metrics
- Docs and community support
Pro
Most teamsShared hosting
Production apps, unlimited builders, more than one region.
- Everything in Free
- Unlimited builders
- Multiple regions per organisation
- Concurrent builds Soon
- Custom domains
- Package vulnerability reports
- 30 days of log retention
- Roles and access control across org, spaces and projects
- Audit log Soon
- Serve publicly or keep it internal-only
- Managed databases, provisioned with the app
- SSO and business-hours support
Enterprise
Salus Cloud or your own
Governance, support and contract terms — and the choice of where your workloads run.
- Everything in Pro
- Choose multi-tenant Salus Cloud, or a dedicated isolated target in your own cloud
- Full audit log, 180-day retention Soon
- Organisation-level environment variables and central config Soon
- Priority build lanes Soon
- Invoiced billing, in arrears Soon
- Dedicated account manager and custom SLA
- SOC 2 Type II & ISO 27001 (audits completing, 2026)
- Volume pricing as your rollout widens
- BYOC — your own cloud, private cloud or on-premise, priced per cluster
BYOC
Your own cloud
Added to an Enterprise plan, never bought instead of one.
- Everything in Enterprise
- Your own AWS, GCP, Azure or Huawei account, private cloud, or on-premise
- A dedicated, isolated target environment in the regions you allow
- Your IAM, your network boundary, your data residency
- You pay your cloud provider directly for infrastructure
- Start on Salus Cloud and move when compliance asks you to
Everything unmarked is available today. Soon marks a capability that is on our roadmap and not yet available. We would rather show you where we are going than let you find out later.
Every plan is + consumption
Two meters, not four: the builders you have, and what your apps run.
Seats are the predictable part. Consumption is the part that scales with success — so here is exactly what it is, before you commit to anything.
What meters
Compute, memory, storage, bandwidth, CDN, load balancing and managed databases — measured against what your workloads actually use, per deployment.
How you pay
On Salus Cloud, consumption draws from prepaid credits — top up as you go. Enterprise can be invoiced in arrears instead. On BYOC, your cloud provider bills you directly for infrastructure.
What never meters
The people who use what you build. Colleagues opening an internal tool, customers loading a public site, clients calling your API — free, and no Salus account needed.
An option on Enterprise, not a separate tier
How BYOC fits.
Most teams do not need this on day one, and the ones that do usually know already. BYOC is not a cheaper or bigger Enterprise — it is the question of whose cloud account the platform runs in, answered separately from what you are entitled to.
You buy Enterprise
for the governance, isolation, support and contract terms — priced per builder, the same either way.
You add BYOC per cluster
for the infrastructure it all runs inside — your public cloud account, your private cloud, or on-premise. Quoted on top of your Enterprise plan, not instead of it.
You can move later
start on Salus Cloud today and bring it into your own cloud when your compliance posture asks — same platform, same deploys, no change of plan.
What the meter actually sees.
Three real shapes of usage, priced in plain terms — because a pricing model you can predict is the pricing model you can approve.
A Finance analyst ships an expense tracker
1 builder + one small container
She built it with AI in an afternoon; 200 colleagues use it every day. The bill sees one builder and the little it runs. The 200 colleagues: free.
An engineering team runs 12 production services
The builders who shipped + what the services consume
Compute, databases and bandwidth meter as used, drawn from your credit balance. Deploys, rollbacks and logs are part of the platform — not line items.
An agent fixes and redeploys overnight
Only the compute its work consumes
The agent works with its builder’s access, so it needs no seat of its own. Its builds and scans bill as the compute they burn — same credits as everything else.
Pricing questions, answered.
How is consumption billed?
Salus Cloud runs on prepaid credits: start with your $10 starter credit and top up as you go. Credits cover the compute, databases and bandwidth your workloads use. Keep an eye on your balance — top up before it runs out so your apps keep serving. Enterprise plans can be invoiced in arrears instead.
Are the people who use my apps billed?
No — never. You pay for builders and for what runs. Everyone who uses what you build is free and does not need a Salus account: colleagues opening an internal tool, customers loading a public site, clients calling your API. This site runs on Salus, publicly, on one builder’s seat.
What counts as a builder?
A builder or an admin — someone who builds, deploys or administers inside your Salus organisation. Everyone consuming what those people ship is free, however many of them there are.
Do AI agents need their own seat?
No. An agent acts on behalf of the builder who invoked it, as a delegate using that builder’s access — so it never consumes a seat of its own. You pay for the compute its work burns, in the same credits as everything else. The individual grants their agent autonomy; the organisation sets the bounds of what any agent can reach.
Where do my workloads actually run?
Free and Pro run on Salus Cloud’s shared, multi-tenant infrastructure — your containers, isolated from other tenants, on capacity we operate. Enterprise gets a choice: stay on that managed multi-tenant environment, or deploy into a dedicated, isolated target inside infrastructure you own. That second option is BYOC, and it is only available on Enterprise.
Is Enterprise the same as running in my own cloud?
No — they are separate choices. Enterprise is the tier: governance, support and contract terms. BYOC is where you choose to run it — a dedicated, isolated target in your own public cloud account, private cloud or on-premise — quoted per cluster on top of your Enterprise plan. You need Enterprise to have the choice at all, and you can start on Salus Cloud and move later.
Can I control who can reach what I deploy?
Yes. Each deployment can be served publicly or kept internal-only, and you choose the cloud and region an environment runs in.
Try Salus for free.
Start with your $10 credit and ship in minutes. Go to production at $9 per builder, and move into your own cloud when you're ready to scale.