I build team tools

Working apps reach your team sooner.

You can build the app. Running it shouldn’t mean waiting for IT to find the time. Connect its repo and your agent deploys and runs it on Salus, within the rules IT sets, with a managed database, logs and rollback. Share it with colleagues without extra app user fees.

Start free See the platform
Illustrative product view

your agent · claude code salus · mcp

Deploy my expense tracker for the finance team, please.

Done. It went out through your company’s release rules, internal-only, and your colleagues can use it without a Salus seat.

  • security scan ✓
  • build ✓
  • release ✓
  • live

deployed with your access · within IT’s rules

Did the security scan find anything?

The scan ran before the build. Nothing critical, and two package findings to review in the pipeline.

It feels slow this morning. Can you check the logs?

The logs show database connection errors since 9:00. I can fix the setting and redeploy.

Rather roll back to yesterday’s version for now.

Rolled back. Yesterday’s version is live again. Both changes used your access, within IT’s rules.

  • rollback ✓
  • your access
  • Web expense-tracker Finance · internal-only live
  • Agent support-triage-agent Ops · internal-only live
  • Web budget-dashboard Finance · push detected building
  • Database expense-tracker-db managed Postgres live

Your agent

Ask your agent to deploy it.

Your agent carries out deploys, checks logs and rolls back for you, with your access and within IT’s rules, so routine releases don’t wait in a queue. Under the hood it’s 52 MCP tools. The salus CLI signs you in and starts the server. Everything else happens in the conversation.

  • deploy_repo

    Build, scan and deploy a connected repository in one call.

  • get_app_logs

    Read a running app's logs, by workload.

  • get_deployment_metrics

    Request rate, errors and response time for a deployment.

  • create_database

    Provision a managed Postgres database for your project.

  • rollback_deployment

    Put the last good revision back.

  • set_deployment_offline

    Take a deployment offline when it needs attention.

What you get

Everything you need to put a team tool into use.

Deploy from your repo

Connect a GitHub, GitLab or Azure DevOps repo. Salus builds it with buildpacks or your Dockerfile and deploys on every push.

Managed databases

Add a managed Postgres database and link it to your project. No separate vendor to set up.

Logs and metrics

Read build and app logs, and check request rate, errors and response time. Nothing extra to wire up.

Roll back in one step

If a new version misbehaves, roll back to the last good one.

Share it without seat fees

Make each deployment public or internal-only. Colleagues who use your app need no Salus account and add no seat fees, however many use it.

Your agent does the routine work

Your agent can deploy, roll back, read logs, add databases and move an app to another supported environment, using your access and nothing more.

How it ships

From your laptop to live, one approved path.

Every change goes through the same steps, so your app reaches your team sooner and IT stays in control.

Illustrative product view

  1. step 1

    git push

    connected repo

  2. step 2

    Scan

    no critical issues

  3. step 3

    Build

    image salus.app/api:9f3c

  4. step 4

    Release

    org release rules applied · rollout 100%

  5. step 5

    Observe

    logs · metrics · usage

On the engineering team?

See how Salus looks to the engineers who run the platform: pipelines, vulnerability scanning, logs and metrics, and agents over MCP.

See Salus for engineering

Get working apps to your team sooner.

Start free. You will need your code in a GitHub, GitLab or Azure DevOps repository.

Start free See the platform