Deploy on GCP
One-click PandaStack deploy on Google Cloud (n2d-highcpu-32 with nested KVM).
GCP is the recommended cloud for PandaStack. n2d-highcpu instances expose nested KVM with zero quota requests, and boot times are 175–205 ms (the same as bare metal).
Prereqs
gcloudCLI logged in (gcloud auth login)- A billing account
- The
computeandiamAPIs enabled
One-command deploy
git clone https://github.com/pandastack-io/pandastack
cd pandastack
./deploy/deploy-gcp.shThe script will:
- Create a project (or reuse one set in
GCP_PROJECT) - Create a VPC + firewall rules
- Provision a
n2d-highcpu-32VM inus-central1-a(Ubuntu 24.04) - Run
cloud-initto install Firecracker, mount the XFS-reflink loopback, lay downpandastack-agent,pandastack-api,pandastack-dashboard, and Caddy - Bake the first-party templates:
base,code-interpreter,agent,browser, andpostgres-16 - Issue Let's Encrypt certs for
*.pandastack.aior a domain you own
Total time: ~12 minutes.
Costs
| Component | Spec | Monthly |
|---|---|---|
| n2d-highcpu-32 | 32 vCPU, 32 GiB, 200 GiB pd-ssd | ~$540 |
| Cloud SQL (optional, multi-node) | db-g1-small | ~$50 |
| Egress | depends | varies |
For dev/staging, run --machine-type n2d-highcpu-8 (~$135/month, supports ~30 concurrent sandboxes).
Configuration
GCP_REGION=europe-west4 GCP_MACHINE=n2d-highcpu-64 PANDASTACK_DOMAIN=pandastack.acme.com ./deploy/deploy-gcp.shClients should then use the API endpoint you expose:
export PANDASTACK_API=https://api.pandastack.ai
export PANDASTACK_API_KEY=pds_abc123def456...Tearing down
./deploy/deploy-gcp.sh --destroyThis deletes the VM and zone — cert state in CF is preserved.