Pricing # Keep control as more teams put apps into use Run team-built apps and agents with managed hosting, access controls, and spending you can review by app. [Start free ](https://app.salus.cloud/register) No card needed · [up to $25 in credit as you set up](https://salus.cloud/pricing/#credits) ## Hobby Evaluate with a team app $0 Seat fees · Plus usage Set up a team app and earn up to $25 in credit toward running it. - Up to 3 people in your organization - Up to $25 in starter credit toward usage as you set up — no card needed - Deploy from a connected GitHub, GitLab or Azure DevOps repo — any framework, real containers - One region for your organization - One build at a time - Vulnerability scanning in every pipeline, with a severity summary - One managed database - Serve publicly or keep it internal-only - 7 days of logs and metrics - Docs and community support [Start free](https://app.salus.cloud/register) ## Pro Manage apps across teams $9 Per builder per month · Plus usage Manage team access and run production apps on shared Salus Cloud. - Everything in Hobby - Unlimited builders - Multiple regions per organization - Up to 5 builds at a time - Custom domains - Full vulnerability reports, the vulnerability dashboard and rescans of running apps - Block a deploy on vulnerability findings - 30 days of log retention - Environment variables set once for the organization or a space - Roles for each space and project, not just the organization - Audit log, 30 days of history - More managed databases, in larger sizes - SSO and business-hours support [Get started ](https://app.salus.cloud/register) ## Enterprise Set company hosting terms From $25 Per builder per month · Plus usage Choose company support and contract terms on Salus Cloud or your own cloud. - Everything in Pro - Choose multi-tenant Salus Cloud, or a dedicated isolated target in your own cloud - Audit log, 180 days of history - Up to 10 builds at a time - Organization release rules that every new project inherits - Priority build lanes - Invoiced billing, in arrears - Dedicated account manager and custom SLA - SOC 2 Type II and ISO 27001 compliant - Volume pricing as your rollout widens - BYOC — your own cloud, private cloud or on premises, priced per cluster [Book a demo](https://salus.cloud/talk-to-sales/) ## BYOC — Enterprise add-on Keep apps in your cloud Custom Per cluster · Added to Enterprise Includes all Enterprise features. Add a dedicated environment in your cloud. - Everything in Enterprise - Your own AWS, GCP or Huawei account, private cloud, or on premises - 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, then deploy the same app to environments in your own cloud [Book a demo](https://salus.cloud/talk-to-sales/)[How BYOC works ](https://salus.cloud/byoc/) A seat covers a builder or admin. App users need no paid seat or Salus account. Starter credit ## Up to $25 in credit as you set up Get $5 in credit when you create your organization, and up to $20 more as you connect your code, connect your AI assistant and make your first deploy: up to $25 in all. That’s enough to run a full-stack team app at low demand for about two to three months. 1. Create your organization+$5 2. Connect your code+$5 3. Connect your AI assistant+$10 4. Deploy your first project+$5 No card needed, and credits don’t expire. Each step pays once per organization and once per person. Usage ## Understand what you pay as teams deploy Seat fees depend on your plan and builder count. Usage depends on the resources your apps and agents consume. - ### Share an internal tool across your company. Your builders and admins count as seats. Colleagues can use the tool at zero extra seat cost, while its resource usage stays billable. - ### Run a public site on one builder seat. A site managed by one builder uses one seat plus app usage. Visitors need no paid seat. The Salus website runs this way. - ### Let an agent handle deployment. Agents acting on your behalf need no separate seat. Builds aren’t charged, and the apps they deploy draw on the same prepaid balance. - ### Track spending by app. On Salus Cloud, app usage draws from one prepaid balance. Check which apps use your credits and top up as needed. Your prepaid balance can go below zero. Treat it as a payment balance rather than a spending limit. [Start free](https://app.salus.cloud/register) Enterprise ## Run in your own cloud when you need to 1. ### Choose Enterprise. Your Enterprise plan covers builder seats, company support, and contract terms. 2. ### Add your own cloud. Pay a custom fee per cluster for a dedicated environment in your cloud account, private cloud, or on premises. 3. ### Pay your cloud provider. Your cloud provider bills infrastructure directly. You can start on Salus Cloud and move later. [Book a demo](https://salus.cloud/talk-to-sales/) Before you start ## Check how seats and usage affect your bill - ### Your credits pay for app usage. Salus Cloud draws usage charges from one prepaid balance. New organizations earn up to $25 in starter credit as they set up, then top up as needed. Balances can go below zero. - ### You can review usage by app. Salus meters usage per app. Charges cover compute, memory, storage, data transfer, content delivery, load balancing, and managed databases. Builds aren’t charged. - ### App users need zero paid seats. Colleagues and customers who use your apps are free and need no Salus account. App resource usage still incurs charges. - ### Agents work through builder access. An agent needs no separate seat. It uses the permissions of the person who runs it, and its compute draws from the same prepaid balance. - ### You add your own cloud to Enterprise. BYOC requires an Enterprise plan plus a custom fee per cluster. You also pay your cloud provider directly for infrastructure. - ### Your plan sets access and support options. Hobby and Pro run on shared Salus Cloud. Paid plans add controls and support. Enterprise adds company contract terms and the option to host in your own cloud. FAQ ## Pricing questions, answered ### How is usage billed? Salus Cloud runs on prepaid credits: start with your free starter credit, then top up as you go. Credits pay for the compute, memory, storage, data transfer and managed databases your apps use, metered by app, project and environment. Builds aren’t charged: your plan sets how many run at once. Your balance can go below zero, so treat it as a payment balance rather than a spending limit. ### How much free credit do I get? Get $5 in credit when you create your organization, and up to $20 more as you connect your code, connect your AI assistant and make your first deploy: up to $25 in all. No card needed, and credits don’t expire. Each step pays once per organization and once per person. Credit pays for what your apps use once they run. Builds aren’t charged. ### Are the people who use my apps billed? No. You pay for builders and admins, and for what your apps use. Everyone who uses what you build is free and needs no Salus account: colleagues opening an internal tool, customers loading a public site, clients calling your API. This website 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 organization. Everyone who uses 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 runs it, with that builder’s access, so it never uses a seat of its own. It can do only what that builder’s role allows, and your organization sets the roles. What it deploys runs on the same prepaid balance, and builds aren’t charged. ### Where do my workloads run? Hobby and Pro run on shared, multi-tenant Salus Cloud, in the cloud and region you choose for each environment. Enterprise adds a choice: stay on multi-tenant Salus Cloud, or deploy into a dedicated, isolated environment in infrastructure you own. That second option is BYOC. ### Is Enterprise the same as running in my own cloud? No, they are separate choices. Enterprise is the plan: governance, support and contract terms. BYOC is where you run it: a dedicated environment in your own cloud account, private cloud or on premises, priced per cluster on top of Enterprise. You can start on Salus Cloud and add your own cloud later. ### Can I control who can reach what I deploy? Yes. Each deployment can be served publicly or kept internal-only, and roles at the organization, space and project levels decide who can view, change and deploy it. ## Assess Salus with a team project Use a team project to assess deployment, access, and app usage before a wider rollout. [Start free ](https://app.salus.cloud/register)[Book a demo](https://salus.cloud/talk-to-sales/)