Deploy your first app

Before you start

You need a Deplexo account and application source in a Git repository or ZIP archive. For a private repository, connect your Git provider and grant Deplexo access. Add credentials in the deployment form so they stay out of your source code.

Run the app locally first. Check how it starts, which port it listens on if it serves HTTP, and what storage or database it needs. Each official template lists these details in its README.

• Choose a template
• Connect a git provider

Prepare your repository

Commit a Dockerfile and your dependency lockfile. A Dockerfile gives you control over the build and startup process. For framework-generated builds, select the framework in the deployment form and use deplexo.yaml for repository settings.

Place deplexo.yaml at the repository or ZIP source root. For monorepos, set build.root_dir to the folder containing your app. The Dockerfile path is relative to that build context; keep the files needed by the build inside it.

version: 1
type: web
build:
  framework: dockerfile
  dockerfile: Dockerfile
run:
  port: 3000

• Docker and builds
• YAML configuration reference

Configure and deploy

Open Deploy, choose your repository or upload a ZIP, and review the application name, region, and resources. The form reads your YAML and marks the settings it controls. Explicit YAML values override dashboard defaults. Add the environment variables required by your application before submitting.

For a web service, set run.port to the port your server listens on and bind the server to 0.0.0.0. Deplexo supplies the matching PORT value. Without run.port, set PORT in the environment settings if your app uses a port other than 3000. For a polling bot or another background process, use type: worker and omit run.port; no HTTP server or public URL is required. Choose the correct app type before creation, because redeployment cannot change it.

• Deploy an application
• Environment variables

You can also deploy from your terminal with the Deplexo CLI or call the user API from a script.

Verify the result

Watch the deployment’s build logs. After startup, open a web service’s application URL and exercise a real route or action. For a bot, send a command through Telegram or Discord and check its runtime logs for a successful connection.

Test the features your app depends on, including sign-in and database access. If something fails, compare the deployed commit, environment variables, and logs with your local setup.

• Read deployment logs
• Diagnose a failure

Ship your next change

Commit and push a small change to the connected branch. With automatic deployment enabled, the Git webhook triggers a new deployment. Otherwise, redeploy from the application dashboard.

Once the app works on its default URL, attach a custom domain if needed. Set up your own backup process before relying on persistent data for production workloads.

• Connect a domain
• Plan persistent storage