01
Connect your agent
Add salus mcp to your agent once to connect Salus to it over MCP.
Salus works with your favorite agent
Claude Code, OpenAI Codex, Cursor, Grok, OpenCode, Devin or your own agents can deploy your app on Salus and keep it running. Your access, your release rules, your scans.
Connect your AI assistant and earn $10 in credit, part of up to $25 as you set up. No card needed.
Claude Code
OpenAI Codex
Cursor
Grok
OpenCode
Devin- Your own agents
claude-code · Salus MCP zsh
~/expense-app $ claude "deploy this to Salus"
mcp salus.
scan ✓ vulnerability scan complete
build ✓ image expense-app:2a41
release ✓ running
~/expense-app $ claude "latency looks off, check the logs"
mcp salus.
[WARN] db pool exhausted (12/12)
~/expense-app $ claude "raise the pool size and redeploy"
mcp salus.
mcp salus.
release ✓ running
~/expense-app $ claude "anything vulnerable in what we just deployed?"
mcp salus.
scan ✓ 0 critical · 2 low
How it works
From agent session to live app
Your code stays in the GitHub, GitLab or Azure DevOps repository you connect to Salus.
02
Sign in as yourself
Run salus auth login. Your agent then acts with your own access and needs no seat of its own.
03
Ask it to deploy
Point your agent at a connected repository and ask it to deploy. Your release rules and scans apply.
What agents do
What your agent handles on Salus
Your agent connects over MCP and gets 50+ tools to deploy and run your app.
Repository deploys
Ship a new or existing project from its connected repository.
Pipelines and logs
Follow pipelines and read build logs, app logs and metrics to find what broke.
Rollbacks and offline mode
Roll back to an earlier release, or take a deployment offline and bring it back.
Databases and variables
Create managed databases, link them to a project and set environment variables.
Vulnerability checks
Ask for a vulnerability check on any environment you can reach.
Cloud and region moves
Create an environment in a supported cloud and region, then move a full-stack app into it.
On a move, your agent relinks a database, copies the environment variables and redeploys the app. The move copies no database contents.
See all 50+ toolsWhy IT can approve it
IT keeps control of agent deploys
Your agent works as your delegate, with no account or seat of its own.
Builder permissions
Permissions follow the person who invokes the agent. If that builder has no access to a project, space or environment, the agent has none either.
Release rules and scans
Your organization’s release rules and vulnerability scanning run on an agent’s deploy exactly as they do on a person’s.
Audit log entries
A deploy an agent starts shows in the audit log as Salus MCP acting as that builder. IT sees the person and that their agent ran it.
Apps run on managed hosting separate from your core systems, and IT can take any workload offline.
FAQ
Agent questions, answered
Which coding agents work with Salus?
Any agent that supports MCP. That includes Claude Code, OpenAI Codex, Cursor, Grok, OpenCode, Devin and your own agents. Connect one with salus mcp and sign in with salus auth login.
Does my agent need its own seat?
No. Your agent acts on your behalf with your access, so it needs no seat or account of its own. Its compute is usage from your organization’s prepaid balance.
How does IT see what my agent deployed?
In the audit log. A deploy your agent starts shows as Salus MCP acting as you, so IT sees the person and that an agent ran it.
What happens to my database when my agent moves an app?
The move copies no database contents. Your agent relinks a database, copies the environment variables and redeploys the app in the new cloud and region.
Does Salus create my repository?
No. Your code stays in your own GitHub, GitLab or Azure DevOps repository, and you connect that repository to Salus.
Ship your first agent deploy today
Let the agent you already use ship your app to Salus.
Connect your AI assistant and earn $10 in credit, part of up to $25 as you set up. No card needed.