Create your workspace

Signing up creates your account and a first workspace — the space that groups your applications, environments and team members. You can invite colleagues right away and assign them a role (owner, manager, deployer or viewer) matching what they need to do.

One workspace per team or client, with its own applications and deployment history
Four built-in roles (owner, manager, deployer, viewer) to separate who configures from who deploys
Invite by email: the member joins the workspace as soon as they accept

Configure your targets

Add the servers you deploy to (over SSH), create an application, then its environments (Production, Staging...) and its targets (API, frontend, worker...). For each target, define the pipeline: the ordered list of shell steps to run, with their timeouts and failure behavior. Then add the environment variables specific to each environment.

SSH connection to your own servers — no imposed infrastructure, you stay in control
Fully customizable shell pipeline, step by step, with timeouts and failure handling
Environment variables (secrets included, encrypted) scoped to each target/environment pair

Deploy and supervise

Trigger a first deployment manually from the UI, or set up a Git webhook so every push to the right branch triggers one automatically. Watch progress step by step in real time, all the way to success — or step in immediately (cancel, check the logs) if something goes wrong. Rolling back to a previous version takes one click.

Manual trigger or automatic via GitHub, GitLab or Bitbucket webhooks
Live tracking of every step (console output included) through real-time notifications
Cancel mid-run, retry after a failure, or roll back to a previous deployment

Do I need my own servers?

Yes. App Deployer orchestrates your deployments but doesn't provide hosting: you connect your existing servers over SSH and keep full control over your infrastructure and data.

What happens if a pipeline step fails?

The deployment stops and the remaining steps are marked "cancelled", unless you flagged a step as allowed to continue on failure. You can immediately inspect the failing step's output, then retry the deployment once the fix is in place.

How does rollback work?

A rollback replays the pipeline against the branch and commit of a past successful deployment. It doesn't automatically restore server state — the pipeline itself needs to be designed to be replayable (reversible migrations, etc.).

Can I automate deployment on every Git push?

Yes, via GitHub, GitLab or Bitbucket webhooks: map a branch to an environment, and every push to that branch automatically triggers a deployment.

Up and running in three steps