Guides

Step-by-step guides for getting an app to a live URL on Salus, whether it was built with an AI coding agent or an AI app builder. Connect your agent to Salus once, and it can deploy, add a database, read the logs and roll back for you. The app-builder guides were each tested on Salus with an app laid out the way that tool exports it.

• Deploy with an AI coding agentHow an agent deploys through the Salus MCP server, what it can reach, and the note that makes every agent deploy your project the same way.
• Claude CodeAdd Salus with one command, approve read-only tools once, and make deployment part of the project's CLAUDE.md.
• OpenAI CodexAdd Salus to config.toml for the Codex CLI and IDE extension, and record how the project deploys in AGENTS.md.
• CursorAdd Salus to .cursor/mcp.json and let Cursor's agent deploy, with each action approved in the chat.
• Lovable or Bolt appDeploy the Vite app either tool exports, with working deep links and your Supabase backend kept as it is.
• v0 appRun the Next.js app v0 exports: one build flag, port 3000, and what replaces Vercel-only storage.
• Move a Replit appRun a Node.js or Python app from Replit on Salus: the port and secrets Replit set for you, and the database.
• It works locally but not on SalusThe usual causes, in order: the port, missing variables, localhost addresses, files that don't persist, and build settings.

New to Salus?

Start with the Quickstart to deploy your first app from the console, then see Supported Stacks for the frameworks Salus builds without configuration, and Regions for where your app can run.