Own server deployment

Run the deployment control plane on your own server.

Self-hosted deployment fits teams that want to own servers, database state, upgrades, backups, and deployment credentials. The Appaloft CLI, Web console, GitHub Action, and AI entrypoint can still use the same deployment semantics.

Self-hosting comparison CLI deploy Install docs

Self-hosted starting point

curl -fsSL https://appaloft.com/install.sh | sudo sh
cd /opt/appaloft
docker compose --env-file .env -p appaloft ps
curl http://localhost:3001/api/health

Entrypoint

CLI / Web / AI / GitHub

Target

owned server or cloud VM

State

self-hosted control plane

Best for

BYOS and internal platforms

Recovery

logs, health, rollback

Keep control-plane state, database, and deploy credentials on infrastructure you operate

Works for VPS instances, cloud VMs, local Docker hosts, and internal servers

Cloud can still sit above it later for teams, permissions, marketplace, and collaboration

When to choose self-hosting

Start here when deploy state, server credentials, database, and backups need to stay in your environment. Cloud can be added later for team access, permissions, marketplace flows, and collaboration.

Choosing an entrypoint

Use the CLI for local operations, GitHub Action for team automation, start.md or the Appaloft skill for AI workflows, and the self-hosted Web console when operators need a UI.

Preflight checks

Confirm SSH, Docker or target runtime, domain/TLS ownership, database and object-storage backup plans, plus logs and rollback paths for failed deploys.

Deployment flow

Install control plane

Start Appaloft and its database on your server from the self-hosting docs.

Connect resources

Bring servers, projects, environments, and deployment credentials into one deploy path.

Deploy and verify

Trigger deploys through CLI/Web/AI/GitHub, then check URL, logs, health, and recovery commands.

Keep following the same deploy path.

Appaloft SEO pages are organized around real deployment tasks. Each page should lead to the next useful step, not stand alone.

Own server deployment

Tie the control plane, CLI, servers, rollback, and Cloud collaboration boundary into one self-hosting cluster.

GitHub deployment

Use GitHub Actions to connect repository events to Appaloft deployment while keeping explicit workflows.

Static site publishing

Connect build output, browser upload, CLI deploy, and one-click buttons for static site publishing.

AI deployment

Let the agent identify project shape first, then choose the skill, CLI, static publishing, or Cloud console path.