qeda-logo

DocsDeploy your Infrastructure

Deploying from the Marketplace (VMs, clusters, managed DBs)

A catalog of production-ready services — standalone apps and backing services alike — deployed or attached in a couple of clicks, no Dockerfile or repo required.

The Marketplace is a browsable catalog of ready-to-run services — Odoo ERP, WooCommerce, Nextcloud, Matrix, PostgreSQL, and more — searchable and filterable by category (Database, E-Commerce, ERP, Monitoring, Security, Storage…), each with a rating and a download count.

The Marketplace catalog, showing service cards like Odoo ERP, PostgreSQL, WooCommerce, and Nextcloud
Every card shows what it is, what category it's in, and how many times it's been deployed by the community.

Two kinds of services

A Marketplace service is either a standalone app (Odoo, WooCommerce, Nextcloud — a full deployment with its own capacity and domain, similar to a Docker or Template deploy) or a backing service that attaches to an app already running in a project (a database, most commonly). Qeda tells you which project already has an app to attach to before you even open the deploy drawer.

Note. A project hosts one app. Attaching a backing service to a project that already runs one is normal and expected; deploying a second standalone app goes into a new project instead — the deploy flow offers that in one click when it applies.

Attaching a backing service

Hovering a card reveals a deploy button; for a backing service like PostgreSQL, it opens straight to picking the target project and a preview of exactly what gets provisioned — the image, and which environment variables land in the app's Variables tab automatically.

The deploy drawer for PostgreSQL, showing the target project and what gets provisioned
DATABASE_URL and POSTGRES_* — the app doesn't need its connection details typed in by hand.

Review & deploy shows the estimated cost and checks the wallet before anything happens — same wallet gate as every other deploy path. Attaching a backing service reads "Attach to project" rather than "Deploy," since it's joining an existing service rather than starting a new one.

The review step, showing the summary, estimated monthly cost, and a "Wallet ready" check
The same wallet check every deploy path shares — nothing provisions on a wallet that can't cover it.
The project canvas after attaching PostgreSQL, showing the app and database cards connected
The database lands on the canvas connected to the app it was attached to, the same as a companion Qeda auto-detects from a repo.