Cloud deployment platform

# Support more team apps with less work for IT

Salus brings deployment, access, and monitoring into one platform. Give AI-built apps and agents managed hosting separate from core systems.

[Start free ](https://app.salus.cloud/register)

SOC 2 Type II and ISO 27001 compliant

Illustration: the same city as the homepage, seen from higher up. Across a canal from the old town and its core-systems power station, team apps run in their own district (cloud hosting, separate from core systems). New apps enter through an inspection gate where they are scanned, then built and released (software delivery). Every plot carries the organization’s lime code mark, so roles and release rules are set once and inherited (governance). A builder’s drone waits at the gate with its parcel: an agent deploys with the builder’s own access and passes the same scan (agent operations).

Capabilities

## Manage team apps from release to daily use

Cloud hosting

### Choose where team apps run

Choose a cloud and region when you create an environment. Run full stack apps and managed databases apart from core systems.

-   Salus GCP in the USA
-   Salus AWS in South Africa
-   Managed databases
-   Bring your own cloud on Enterprise

Software delivery

### Release team apps through your checks

Connect your repository so Salus can scan, build, and release your software under your organization rules.

-   GitHub, GitLab, or Azure DevOps repositories
-   Apps built with any framework
-   Vulnerability scanning in each pipeline
-   Release rollback

Agent operations

### Let builders deploy from the tools they use

Builders use Claude Code, OpenAI Codex, or another agent connected through MCP. Agent actions use the permissions of the builder.

-   Deploy apps and databases
-   Read workload logs
-   Roll back releases
-   Move full stack apps between supported environments

IT governance

### Keep access and releases under your rules

Choose who can view, change, and deploy workloads. Set organization release rules once so new projects inherit them.

-   Roles at organization, space, and project levels
-   Deployment records tied to builder access
-   Logs and metrics in one place
-   Usage per app from one prepaid balance
-   Take any workload offline

How IT runs it

## Set up once so teams can deploy

1.  ### Set up an environment for your teams
    
    Choose its cloud and region, set roles and organization release rules, then invite builders.
    
2.  ### Teams deploy within your rules
    
    Builders connect a repository or ask their agent to deploy full stack apps and databases within your rules.
    
3.  ### Review workloads and act when needed
    
    Check logs, metrics, the audit log, and app usage. Roll back a release or take a workload offline.
    

## Bring your first team onto Salus

Create your account, choose an environment, and invite your first builders.

[Start free ](https://app.salus.cloud/register)