Skip to main content

Deploy an Express.js App on QuikDB in 60 Seconds

· 3 min read
Samson Ajulor
Samson Ajulor
CEO, QuikDB

You built your Express app. Maybe with AI, maybe by hand. Either way, it works locally. Now you need it online.

Most platforms make this harder than it should be. Write a Dockerfile. Set up a CI pipeline. Configure environment variables through three different screens. Wait 10 minutes for the build.

QuikDB skips all of that. Connect your GitHub, pick your repo, click deploy. That's it.

What you need​

  • A GitHub account
  • An Express.js app in a repo (any repo — public or private)
  • A QuikDB account at compute.quikdb.com

No Dockerfile. No quikdb.json. No config files. QuikDB auto-detects your stack.

Step 1: Connect GitHub​

Go to compute.quikdb.com, sign in with your wallet, and head to the Repos page. Click Connect GitHub and authorize QuikDB to read your repos.

One-time setup. Takes 10 seconds.

Step 2: Create a deployment​

Click New Deployment. You'll see a 3-step wizard:

Pick your repo and branch. QuikDB lists all your repos. Select the one with your Express app and choose the branch you want to deploy (usually main).

Review the config. QuikDB scans your repo and auto-detects:

  • Build command: npm install
  • Start command: node index.js (or whatever your package.json says)
  • Port: reads from your code or defaults to 3000

You can edit any of these if needed. Add environment variables here too — they're encrypted with AES-256.

Click Deploy.

Step 3: Wait ~30 seconds​

QuikDB does the rest:

  1. Clones your repo on a runner node
  2. Generates a Dockerfile (you don't need to write one)
  3. Builds the image
  4. Starts the container with health checks
  5. Gives you a live URL: your-app-name-abc123.quikdb.net

The deployment page shows real-time progress. You'll see it go from pending �� building → deploying → live.

That's the whole thing​

Your app is live. It has:

  • HTTPS by default (via Cloudflare)
  • Health monitoring
  • Logs you can view in the dashboard
  • Zero-downtime restarts when you redeploy

Environment variables​

If your app needs a database URL, API key, or any secrets:

  1. Go to your deployment's Environment tab
  2. Add variables one by one, or bulk-import from a .env file
  3. Keys matching SECRET, KEY, TOKEN, PASSWORD, or API_KEY are automatically encrypted

Changes take effect on the next deploy.

Redeploying​

Push to your branch and hit Redeploy in the dashboard. QuikDB does a blue-green deployment — your old version stays live until the new one passes health checks. Zero downtime.

What it costs​

The Hobby plan is $5/month. You get 3 containers, 0.5 vCPU and 512MB RAM each. Enough for side projects and MVPs.

If you need more power, the Pro plan at $19/month gives you 5 containers with 1 vCPU and 1GB RAM each.

No surprise bills. No per-request pricing. Flat monthly rate.

Try it​

If you want to test with a ready-made app, fork quikdb/quikdb-test-express and deploy it. It's a simple Express server that responds on port 3000.

Go to compute.quikdb.com and ship something.