FAQs

Quick answers to the questions we hear most, with links to the full docs.

Getting started

Which Git providers can I connect?

GitHub and GitLab, connected at the organization level. See Git Management.

Which languages and frameworks are supported?

JavaScript/TypeScript projects and .NET (C#) build with zero configuration via buildpacks; anything with a Dockerfile runs as a custom Docker build — Python, Go, Java, PHP, Ruby, and more. See Supported Stacks.

Do I need a Dockerfile?

Only for stacks the buildpacks don’t cover. For supported stacks, Salus detects your project and builds it without one. See Buildpacks.

Can my AI coding assistant use Salus?

Yes — the Salus MCP server connects assistants like Claude Code, Cursor, and Claude Desktop to your projects, deployments, logs, and databases. See MCP.

Organizations and teams

What’s the difference between the roles?

Owner, Maintainer, Developer, and Viewer range from full control to read-only, and they’re scoped — a member can hold different access in different workspaces or projects. See Access Control.

Why does a member show as “Guest”?

They accepted an invitation to a specific workspace or project without being an organization member — Salus creates the Guest placeholder automatically. Their real access is the scoped role from the invitation. See Organizations & Teams.

Who can deploy to which region?

Admins enable regions and set the default on the organization’s Regions page; environments pick from the enabled set when they’re created. See Organizations & Teams.

Deployments and networking

Is my application public by default?

No — deployments are private unless you enable Expose application to public on the release configuration. See Access Control.

What domain does my app get?

Every publicly exposed application gets a free Salus domain automatically, and you can configure a custom domain. See Environment Configurations.

What port should my app listen on?

Whatever you configure — Salus defaults to 8080.

A release went bad — can I roll back?

Yes. Each environment keeps a history of deployment revisions, and you can roll back to an earlier eligible revision. See Deployments.

Environment variables

Where should I set a variable that several projects need?

At the highest level that owns it: variables merge down Organization → Workspace → Project → Release configuration, with the closest level winning. See Environment Configurations.

Why can’t I create a variable starting with SALUS_?

That prefix is reserved for values Salus injects — like a linked database’s connection details — so they can never be shadowed by your own variables.

My variable change isn’t taking effect.

Variable changes apply only after the deployment is redeployed.

Databases

I lost my database admin password.

It’s shown only once, at creation. Rotate the password to set a new one. See Databases.

Can a project use a database in a different region?

No — a database can only be linked to an environment in the same region as the database.

Logs and billing

How long are my logs kept?

Per your plan’s retention policy. Download anything you need to keep before it ages out. See Logs.

How does billing work?

Your plan, credit balance, payments, and usage are managed at the organization level. See the Billing Dashboard and Salus Credits.