Skip to content
Deployment mode

Install it yourself, or use Cloud.

Both paths use the same Appaloft deployment model. The real choice is where the control plane runs, and who owns team access, billing, marketplace flows, and operations.

Install CommunityOpen CloudCloud pricing

The Community install doc starts with Docker install, domains, and first admin setup.

Appaloft Cloud console overview preview

Community

Runs on your server. You own the database, upgrades, backups, and public entrypoint.

Cloud

Runs at app.appaloft.com, with team access, billing, official Blueprints, and Cloud overlays.

Self-hosted operations

Take your data with you. Reach private services when needed.

These capabilities use the same Appaloft operations across CLI, API, and Web. A self-hosted instance enables its providers, owns credential custody, and proves the real recovery path.

Available

Scheduled and pre-deploy backups

Configure scheduled and pre-deploy policies for Storage volumes, verify each restore point, then apply retention. S3-compatible targets require a safely configured object-storage broker.

Read backup docs
Available

Encrypted whole-instance portability

Export control-plane data with a passphrase, dry-run it against an instance on the same schema revision, then choose merge or an explicitly acknowledged replace. External provider resources move as references and intent only.

Read portability docs
Self-hosted

Temporary tunnels

Start a time-bounded Cloudflare Quick Tunnel or ngrok session for a local or private HTTP origin, with status, revoke, expiry, and orphan cleanup controls.

Read tunnel docs
In progress

From a Git repository to a verified deployment

The connected-GitHub repository picker and deployment-plan foundation are available. Broader framework detection, real buildpack/OCI acceleration, and the full acceptance matrix are still in progress. When intent is ambiguous, Appaloft stops with a repair plan instead of guessing and shipping.

Feature differences

Based on the current code and Cloud source-of-truth docs: core deployment stays open; hosted collaboration and platform services live in Cloud.

Area
Self-hosted Community
Appaloft Cloud
Control plane

Runs on your server

Docker defaults to PostgreSQL; PGlite is available for the local path.

Hosted at app.appaloft.com

Cloud runtime adds overlays to the public Appaloft server.

Deploy entrypoints

CLI / API / Web console

Deploy straight to your VPS, VM, or cluster.

Same deployment path

Adds tenant, permission, usage, and managed deployment overlays.

Teams and RBAC

Basic org and team setup

First admin, local organization, and team data stay in your instance.

Cloud authz / tenancy

owner, admin, billing, developer, viewer roles plus operation guards.

GitHub

Bring your own Action and tokens

Secrets stay in your instance or GitHub Secrets.

Hosted GitHub integration

Sign-in, repository authorization, source events, and status feedback.

Blueprints

Open format and local registry

Blueprints are portable manifests, not Cloud marketplace records.

Official catalog and Marketplace

Install plans, installed records, upgrade dry-runs, and curated listings.

Managed deployment overlay

Default public deployment

Cloud policy, usage, and overlay behavior do not enter Community core.

Managed deployment overlay

Tenant context, entitlement, usage intent, and readback.

Static publishing

Deploy to your own server

Static output can deploy as a normal public Appaloft resource.

Browser upload and hosted URL

Staged upload, object-storage routing, and default-domain readiness.

Billing

No Cloud subscription

You pay for your own servers and providers.

Monthly subscription plans

Servers and hosted static capacity follow the active organization plan and add-ons.

Security and audit

Local security is yours

TLS, email, secrets, monitoring, and hardening are self-managed.

Hosted security controls

Security headers, email verification, audit, abuse controls, and readiness gates.

Backup and recovery

Own the policies and restore points

Supports scheduled/pre-deploy volume backups and S3-compatible targets; you operate storage and restore drills.

Hosted control-plane ops

Cloud keeps break-glass, readiness, and external restore paths.

How to choose

Community and Cloud are not separate deployment engines. Cloud depends on public Appaloft, then adds hosted collaboration, commercial features, and the default online entrypoint in the private layer.

Choose self-hosting

You want the control plane, database, and deployment credentials on infrastructure you operate, and you are fine owning upgrades and backups.

Choose Cloud

You want team sign-in, permissions, billing, official Blueprints, and quick browser-based publishing without standing up the control plane first.

Related topics

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.