Salus Cloud
Managed hosting in the United States (South Carolina) on GCP and South Africa (Cape Town) on AWS.
Unified rules across all your clouds
Run apps in Salus Cloud regions, your own cloud accounts, private cloud and on premise, with the same roles, release rules and audit log.
Plans starting at $25/seat/mo
Salus Cloud regions in Africa
- South Africa (Cape Town), AWS: Live
- South Africa (Johannesburg), Huawei Cloud, Azure, GCP: Soon
- Nigeria, Private cloud, managed by Salus: Soon
- Kenya, Private cloud, managed by Salus: Planned for 2027
- Egypt, Private cloud, managed by Salus: Planned for 2027
Also live: United States (South Carolina), GCP
Salus Cloud regions in the Americas
- United States (South Carolina), GCP: Live
Also live: South Africa (Cape Town), AWS
Managed by Salus. Choose the region for each environment.
Your own cloud, on Enterprise
- Your AWS, GCP or Huawei Cloud account
- Your private cloud
- Your data center, on premises
Salus runs the control plane; your infrastructure runs the apps.
Indicative. BYOC runs in your own cloud account, private cloud or data center, wherever that is.
What Enterprise includes
What Salus Enterprise includes
Enterprise is the Salus plan for governance, support and contract terms.
Governance controls
Roles, release rules new projects inherit and a 180-day audit log.
Account manager and SLA
A dedicated account manager and a custom SLA for your company.
Contract and invoiced billing
Company contract terms and billing by invoice.
SOC 2 and ISO 27001
Get the SOC 2 Type II report under NDA and the ISO certificate on request.
Your choice of hosting
Stay on managed Salus Cloud, or add BYOC in infrastructure you own.
Direct purchase
Buy Enterprise outright, or book a demo with our team.
Customers
Hosting
Run Salus Cloud and BYOC together
One organization can run environments in several regions and clouds at once. You choose the target for each environment when you create it.
Who BYOC is for
Teams that already run an AWS, GCP or Huawei Cloud account
Companies where a regulator sets where workloads run
IT teams with a private cloud or data center
How BYOC works
How BYOC works with Enterprise
Choose Enterprise
Buy Enterprise. BYOC sits on top of your Enterprise plan.
Add your own cloud
Our team sets up a dedicated, isolated environment in your cloud account, private cloud or on premise.
Pay your cloud provider
Your provider bills the infrastructure directly, and Salus quotes BYOC per cluster on top of Enterprise.
What stays the same
What stays the same with BYOC
Your roles and release rules
BYOC environments use the roles, release rules and audit log you set for Salus Cloud.
Salus runs the control plane
By default, your infrastructure runs the apps.
Start on Salus Cloud
Add environments in your own infrastructure later.
Acme / Environments5 environments
| Environment | Runs in | Apps | Release rules |
|---|---|---|---|
production | Salus GCP (USA)Salus Cloud · managed | 2Onboarding portal, Policy assistant | From the organization |
eu-customers | Your AWS accounteu-west-1 · BYOC | 2Campaign site, Lead scorer | From the organization |
asia-ops | Your GCP projectasia-northeast1 · BYOC | 1Ticket triage | From the organization |
finance | Your private cloudBYOC | 3Budget dashboard, Invoice checker, Spend approvals | From the organization |
plant-floor | Your data centerOn premises · BYOC | 2Inventory tracker, Shift planner | From the organization |
Illustrative. Each environment’s cloud and region is chosen when it’s created. Release rules are set once for the organization, and new projects inherit them, whichever environment they run in.
Supported infrastructure
Where Salus runs
Salus Cloud
United States (South Carolina) on GCP and South Africa (Cape Town) on AWS.
Your cloud accounts
AWS, GCP and Huawei Cloud.
Private cloud and on premise
Your private cloud or your own servers on premise.
Security
Security for apps your teams build
Scans in each pipeline
Vulnerability scanning runs on each deploy, whoever starts it.
Hosting apart from core systems
Team apps run separately from your core business systems.
Control plane without your code
It stores no code, workloads or resources such as databases.
Governance
Keep oversight as teams deploy
Enterprise also gets priority build lanes and central configuration for the organization.
Your rules, applied
Roles · who can deploy
- ada@yourco.comdeveloperdeploylogsenv vars
- sam@yourco.comviewerlogsmetrics
Agent actions stay within the access of the person who invokes them.
Release rules
- Organization release rulesinherited by new projectspassed
- Project overridehr · leave-planner · own rulespassed
- Vulnerability scanbefore build · enforced · critical package foundblocked
Monitoring
- Requests
- 42/s
- Errors
- 0.2%
- Response
- 210 ms
When you need it
Take offlineany deployment · bring it back or roll backarmed
Audit log · filter by space or project · deploys shown under the builder whose access was used
- humanada@yourco.comdeployfinance · expense-app
- humanlee@yourco.comdeployhr · leave-planner
- agentSalus MCP acting as ada@yourco.comdeployfinance · budget-agent
Roles at three levels
Decide who can view, change and deploy at organization, space and project level.
Inherited release rules
Set release rules and environment variables once. New projects pick them up.
Audit log for 180 days
Each deploy and who started it. Agent deploys show as Salus MCP acting as that builder.
Logs and metrics together
See logs and metrics in one place, and take any workload offline.
Report to leadership
Show leadership what is running
What runs and where
Each app and the cloud and region it runs in.
Who shipped it
Each deploy and the person behind it, including deploys their agent ran, for 180 days.
What each app uses
Usage for each app, project and environment, drawn from one prepaid balance.
Team apps · quarterly update
11 apps live
built by 4 teams — finance, HR, ops, support
3 agents
deployed the same way as the apps, within the same rules
4 deploys stopped
by an enforced vulnerability scan, before they ran
1 balance
usage by app and environment, from prepaid credit
illustrative figures · roles, release rules and scans applied by the platform, not by each team
FAQ
Enterprise questions, answered
Can we start without sales?
Yes. Buy Enterprise yourself on Salus Cloud. Only BYOC needs our team.
Is BYOC a separate plan?
No. You add BYOC to Enterprise, and our team sets it up with you.
How is BYOC priced?
Per cluster, quoted on top of Enterprise. Your cloud provider bills the infrastructure directly.
Which clouds does Salus support?
Salus Cloud runs in the United States (South Carolina) on GCP and South Africa (Cape Town) on AWS. With BYOC, Salus runs in your AWS, GCP or Huawei Cloud account, a private cloud or on premise.
Can we move to BYOC later?
Yes. Start on Salus Cloud and add environments in your own infrastructure later. Your agent can create an environment in a supported cloud and region and move a full-stack app there, and the move copies no database data.
Who operates what?
By default, Salus runs the control plane and your infrastructure runs the apps. The control plane is SOC 2 Type II and ISO 27001 compliant and stores no code, workloads or resources such as databases.
Can we host the whole platform?
Yes, where it is a hard requirement. Salus deploys the control plane and all its associated apps into your infrastructure.
Which compliance standards does Salus meet?
Salus is SOC 2 Type II compliant and ISO 27001:2022 certified, following independent audits. Ask our team for the SOC 2 Type II report under NDA or the ISO certificate.
Start Enterprise on your own today
Run team apps on Salus Cloud under one set of rules, and book a demo when you want BYOC.