Export and self-host

Your app is yours. Download its code at any time, push it to GitHub to hand over to a client, or run the whole Appbricx platform on servers you control so your users' data never leaves your environment.

When to use it

• Export: handing an app to a client or their developers, keeping your own copy, moving the frontend elsewhere.
• Self-host: data that must stay with you (regulated teams, customer contracts), full control of network and upgrades, internal tools inside your network.

Export the code

1. In the editor, use the download action for a ZIP of the project, or connect GitHub in the project settings and push.
2. You get standard React, TypeScript and SQL files plus the contract.
3. The app's runtime (@app/kit) talks to Appbricx over HTTP. Keep Appbricx as the backend, or point those calls elsewhere.

The contract alone is portable too: appbricx pull writes it to appbricx.json, and appbricx apply builds it in any project, on Appbricx Cloud or your own install. That is how the templates work.

Self-host with Docker Compose

You need a Linux host (Ubuntu 22.04 or 24.04, 2 vCPU and 2 GB RAM minimum, 4 GB recommended), Docker with Compose, a domain and ports 80 and 443.

git clone https://github.com/Naveenbhargav-m/appbricx.git
cd appbricx
DOMAIN=app.example.com EMAIL=you@example.com ./deployment/docker/setup.sh
docker compose --env-file deployment/docker/.env up -d
docker compose --env-file deployment/docker/.env logs -f

Behind Cloudflare Tunnel or another proxy, add --skip-ssl. The stack runs Postgres (with pgvector), a one-shot migrator, the API, the WebSocket server, the web app and Caddy for HTTPS. The first person to sign up becomes the platform admin; set INSTALL_BOOTSTRAP_TOKEN before first boot to control that.

Back up a self-hosted install

docker compose exec -T postgres pg_dump -U appbricx appbricx | gzip > appbricx-$(date +%F).sql.gz

Also back up the volumes for published sites and project files. Optional compose files add a read replica, WAL-G point-in-time recovery and a scheduled dump sidecar. Point your CLI and agents at your install with appbricx login --api https://app.example.com/api or APPBRICX_API.

Gotchas

• Self-hosting in production needs a one-time license with 12 months of updates; evaluation and development need none. See pricing and the self-host guide.
• You own the backups. On your own install, nightly snapshots and off-site copies are your job.
• Uploads need storage. Configure local disk or an S3-compatible bucket.
• Sign in with Google on a self-hosted install uses the Google client your platform admin configures; without one, each app brings its own.

Related

• Publishing, domains and rollback
• Run Appbricx locally
• Templates