Deploy anywhere

Deployment options

Myndlab's managed preview is designed for iteration speed, not production workloads. When your app is ready for real users you have two paths:

• One-click publish — Myndlab builds a container image and deploys it to a production-grade environment with a managed database, SSL, and autoscaling. Fastest path; you stay on Myndlab infrastructure. Set up a custom domain and go live in minutes.
• Export and self-host — Download a ZIP of the generated code and deploy it yourself to any cloud or server. Full control; no lock-in.

The rest of this guide covers the self-host path. For one-click publish, see Project Settings → Deploy → Publish.

Export your code

Before you can deploy anywhere, you need the generated source. You can export as a ZIP or push to GitHub (which gives you a cleaner workflow for ongoing updates).

The exported structure looks like this:

my-project/
├── frontend/          # React + Vite app
│   ├── src/
│   └── package.json
├── backend/           # FastAPI app
│   ├── app/
│   ├── migrations/
│   └── requirements.txt
├── Dockerfile
├── docker-compose.yml
└── .env.example

VPS (any provider)

Any Linux VPS with Docker installed (DigitalOcean, Hetzner, Linode, OVH, etc.) works. This is the quickest self-hosted path.

# On the server
docker compose up -d --build

Docker Compose starts the frontend, backend, and a Postgres container. The frontend is served on port 3000, the backend API on port 8000.

yourdomain.com {
    reverse_proxy localhost:3000
}

api.yourdomain.com {
    reverse_proxy localhost:8000
}

AWS

The recommended AWS pattern is: Elastic Container Registry (ECR) for the image, Elastic Container Service (ECS) with Fargate for running it, and RDS for the database.

# Authenticate
aws ecr get-login-password --region eu-west-1 |   docker login --username AWS --password-stdin   123456789.dkr.ecr.eu-west-1.amazonaws.com

# Build and push
docker build -t my-project .
docker tag my-project:latest   123456789.dkr.ecr.eu-west-1.amazonaws.com/my-project:latest
docker push   123456789.dkr.ecr.eu-west-1.amazonaws.com/my-project:latest

Azure

The recommended Azure pattern is: Azure Container Registry (ACR) + Azure Container Apps + Azure Database for PostgreSQL.

az acr build --registry myregistry   --image my-project:latest .

GCP

The simplest GCP path is Cloud Run (serverless containers) with Cloud SQL for the database.

# Configure Docker for GCP
gcloud auth configure-docker europe-west1-docker.pkg.dev

# Build and push
docker build -t europe-west1-docker.pkg.dev/my-project/repo/app:latest .
docker push europe-west1-docker.pkg.dev/my-project/repo/app:latest

gcloud run deploy my-project   --image europe-west1-docker.pkg.dev/my-project/repo/app:latest   --region europe-west1   --platform managed   --allow-unauthenticated   --set-env-vars DATABASE_URL=postgresql://...

Custom domain

Regardless of hosting provider, the steps to attach a custom domain are the same: