Deploying Your App

Deploy any web application to QuikDB Compute in under two minutes.

Step 1: Connect Your Git Provider

From the Compute dashboard, click Connect Repository and authorize GitHub or GitLab. QuikDB needs read access to clone your code during builds.

Step 2: Select a Repository

Browse your repos and select the one you want to deploy. Choose the branch (defaults to main).

Step 3: Configure Build Settings

QuikDB auto-detects your stack by scanning your repo files. You'll see a pre-filled configuration:

• Runtime — The detected language/framework
• Build command — How to build your app (e.g., npm install && npm run build)
• Start command — How to run your app (e.g., npm start)
• Port — The port your app listens on (defaults to 3000)

You can edit any of these before deploying. To customize further, add a quikdb.json file to your repo root.

Detection Priority

QuikDB checks your repo in this order:

1. quikdb.json — If present, uses your explicit config
2. Dockerfile — If present, builds with your Dockerfile as-is
3. docker-compose.yml — If present, uses your compose file
4. Auto-detect — Scans repo files (package.json, requirements.txt, go.mod, etc.) and generates config

Step 4: Deploy

Click Deploy. QuikDB will:

1. Select healthy nodes from the network based on capacity and availability
2. Clone your repository on the selected node(s)
3. Build a container image from your code
4. Start the container and run health checks
5. Route traffic to your app once healthy

You can watch the build and runtime logs in real time from the deployment detail page.

Deployment States

State	Meaning
pending	Deployment created, waiting to start
building	Code is being built on the node
deploying	Container is starting, health checks running
live	App is healthy and serving traffic
partial	Some replicas are live, others failed
queued	No nodes available — will retry when capacity frees up
failed	All replicas failed to deploy
stopped	You stopped the deployment
sleeping	Auto-sleep (Hobby/Builder tier) due to inactivity

Redeploying

When you redeploy (e.g., after pushing new code), QuikDB uses a blue-green strategy:

1. A new container starts alongside the old one
2. Health checks run on the new container
3. Traffic switches to the new container only when it's healthy
4. The old container is drained and stopped

This means zero downtime on every redeploy.

Rollbacks

From the deployment history tab, you can roll back to any previous successful deployment instantly.

Build Quotas

Each tier has a daily build limit:

Tier	Builds per Day
Hobby	5
Builder	20
Startup	50
Team	Unlimited

Failed builds count toward your quota.