qeda-logo
Features

Every Way to Ship.

One Platform.

CLI, Git, Docker, or Marketplace — choose the workflow that fits how you build.

Some developers live in the terminal. Others push to Git and never look back. Some bring their own containers.

Qeda supports all of it without asking you to change how you work.

01

Deploy with CLI

Your terminal is enough. Install the Qeda CLI and deploy any project with a single command — no dashboards, no clicking around.

~/myapp
$ npm install -g qeda-cli$ qeda login  $ qeda deploy→ Detecting stack: Node.js ✓→ Building in isolated pod…→ Deploy complete: myapp.qeda.app ✓✓ Deploying to high-availability cluster...✓ Deploying to high-availability cluster...
qeda deploy

Build and deploy the current directory.

qeda logs

Stream live logs from your running app.

qeda env set KEY=VALUE

Set an environment variable.

qeda rollback

Instantly revert to the previous deployment.

qeda status

Check the health of your running services.

No Yaml. No config.

Just your terminal and a working app.

Read the full CLI reference
Terminal-native

Some developers don't want
to open a browser to deploy.

Fair enough. The Qeda CLI gives you full control over your deployments from the terminal. Install it once and never touch a dashboard again.

Install once
any stack
full control
~/myapp
$ npm install -g qeda-cliadded 1 package ✓$ qeda deploy→ Detecting stack: Node.js ✓→ Building in isolated pod…→ myapp.qeda.app ✓
02

Deploy with Git

Connect your repo once. Every push to main triggers an automatic build and deploy — no extra config needed.

git pushto main becomes a production deployment.
Detected automatically
JavaScriptReactNext.jsNode.jsDjangoFastAPIFlaskDockerfile

Auto-deploy enabled — every push is a deploy.

Branch previews— every Pull Request (PR) gets its own preview URL.
Coming soon
Connect your first repository →

How it works

git push origin main
Qeda detects the push
Stack identified automatically
Build runs in an isolated pod
Rolling deploy — zero downtime
myapp.qeda.app updated ✓
03

Deploy with Docker

Already have a Dockerfile? Qeda runs it — with automatic SSL, a live domain, and zero infrastructure to manage.

~bash-- docker deploy
$ qeda deploy --dockerfile ./Dockerfile$ qeda login  $ qeda deploy→ Detecting stack: Node.js ✓→ Building in isolated pod…→ Deploy complete: myapp.qeda.app ✓✓ Deploying to high-availability cluster...✓ Deploying to high-availability cluster...

You built your container your way. Qeda just runs it.

No proprietary format. No forced base images. No rewrites. If it runs locally with Docker, it runs on Qeda.

WHAT QEDA HANDLES FOR YOU

Domain

Automatic *.qeda.app subdomain; custom domains supported.

SSL / TLS

Provisioned instantly, renewed automatically.

Isolation

gVisor kernel-level sandboxing, no shared surfaces.

Scaling

Add resources from the dashboard — no redeploy.

Monitoring

Live logs and health checks out of the box.

No lock-in.

Your image is standard Docker. It runs on Qeda today — and anywhere else tomorrow.

Deploy your first Container
04

Deploy Services via Marketplace

One click. One service. Ready to connect. Spin up a database or a cache — no configuration needed.

Service
Type
Use case
PostgreSQL
SQL database
Main app database, relational data.
MySQL
SQL database
Legacy apps, WordPress, e-commerce.
MongoDB
NoSQL database
Flexible schemas, document storage.
Redis
Cache / queue
Sessions, rate limiting, real-time.
Object Storage S3
Object storage
Files, backups, static assets.

HOW IT WORKS

1
Open the Marketplace from your dashboard.
2
Click the service you need.
3
Choose your plan (storage, memory).
4
Qeda provisions it — usually under 30 seconds.
5
Copy the connection string into your .env.
.env — auto-generated
DATABASE_URL=postgresql://user:pass@db.qeda.app:5432/mydb

Managed means managed. Backups, updates, monitoring and uptime — handled.

Coming soon:Redis ClusterQeda FunctionsQeda Agent

Choose your workflow. Ship today.

CLI, Git, Docker or Marketplace — Qeda meets you where you already work.