Appaloft /ˌæp əˈlɔːft/ app aloft

From localhost to cloud.

Appaloft publishes http://localhost:3000 as https://your.awesome.app.
See examples Download CLI

Quick start

Install the self-hosted stack

Deploys the control plane and PostgreSQL on a VPS, cloud VM, or local Docker host.

curl -fsSL https://appaloft.com/install.sh | sudo sh
Install the CLI

Works on macOS and Linux. The desktop app is available with brew install --cask appaloft/tap/appaloft-desktop.

brew install appaloft/tap/appaloft
Install the CLI

Best when Node.js is already part of the environment. Run appaloft after install.

npm install -g @appaloft/cli
Download for your OS

Choose the macOS, Linux, or Windows archive. A system-detecting install script should be shipped from the main repository release.

https://github.com/appaloft/appaloft/releases/latest

Deploy paths

One release path across self-hosting, automation, and cloud.

Run the control plane on your Docker host first, then let CI, desktop, AI skills, and Cloud reuse the same publishing path.

AI-native skill-ready

Let your preferred AI deploy through a skill.

Appaloft does not ship its own AI agent. It is an AI-friendly deploy path that exposes server state, health checks, deploy actions, and logs so you can keep working inside the AI tools you already use.

  • Start deploy conversations inside your existing AI workflow
  • Use a skill to read health, environment, and deploy state
  • Keep release actions and troubleshooting in the same chat context
A preferred AI chat window sits beside Appaloft skill results showing health checks and deploy readiness.
Docker docker

Start the self-hosted control plane.

Run Appaloft and PostgreSQL on a VPS, cloud VM, or local Docker host.

  • Bring up the control plane first, then let every other path reuse it
  • Check compose status and the health endpoint right after install
  • Works on a laptop, VPS, or your own cloud VM
curl -fsSL https://appaloft.com/install.sh | sudo shcd /opt/appaloftdocker compose --env-file .env -p appaloft pscurl http://localhost:3001/api/health
GitHub Action github

Release after every push.

Put the follow-up deployment flow in the repository and keep server credentials in GitHub Secrets.

  • Move repeatable deploy steps into CI instead of manual SSH sessions
  • Keep credentials in GitHub Secrets with an auditable release path
  • Reuse the same control plane path as local, desktop, and AI flows
name: deployon: [push]jobs:  appaloft:    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v4      - uses: appaloft/deploy-action@v1        with:          server: ${{ secrets.APPALOFT_SERVER }}
Desktop App desktop

Open a local control surface.

Inspect servers, apps, deployment records, and log entry points without returning to the terminal.

  • See Overview, Apps, Deploys, Health, Logs, and Secrets together
  • Quickly confirm whether API, web, and worker services are healthy
  • Make status checks and log entry points easier to reach
Appaloft desktop console showing overview, health, recent deploys, and service status.
Cloud soon

Move up when hosting helps.

Teams, permissions, previews, and a shared dashboard can live in future Appaloft Cloud.

  • Keep the same release path and add hosted collaboration later
  • Move team access, previews, and shared dashboards into cloud space
  • Prove the self-hosted path first, then migrate when it helps
Preview envs Soon
Team access Soon
Team dashboard Soon