Community
Runs on your server. You own the database, upgrades, backups, and public entrypoint.
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.
The Community install doc starts with Docker install, domains, and first admin setup.
Cloud
Runs at app.appaloft.com, with team access, billing, official Blueprints, and Cloud overlays.
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 credits
You pay for your own servers and providers.
Prepaid credit ledger
Successful deploys/static publishes are charged; failed or canceled attempts are not.
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 backups and upgrades
Database, object storage, registry, and restore drills are your responsibility.
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.