The Qeda beta is open, and it is free. No card, no subscription, nothing debited — and your project can be online at a public HTTPS address in about ten minutes.
You have a project that works on your machine. Maybe it's an API for a mobile app, a side project, a client prototype, or the thing you have been meaning to show someone for three months. This guide takes you from that to a link you can send, one step at a time.
What "free" means during the beta
We mean it plainly:
- No credit card at sign-up — not a local one, not an international one
- Nothing is debited while the beta runs: leave your project online all month, it costs you nothing
- You receive a welcome credit as soon as you confirm your e-mail address
- When billing opens, beta members keep preferred rates — in your own currency, payable with mobile money
In return, we ask for one thing: tell us what you think. More on that at the end.
What you can deploy
- Web apps and APIs from a GitHub repository — Node.js, Python (Django, FastAPI, Flask), Go, PHP, Ruby, and anything with a Dockerfile
- A public Docker image, straight from Docker Hub, GitHub Container Registry or Quay — no build step at all
- Managed databases next to your app — PostgreSQL, MySQL, MongoDB and Redis
You don't write a Dockerfile, configure a server or set up HTTPS. Qeda reads your repository, works out how to build it, and runs it.
Step 1 — Create your account
Go to dashboard.qeda.io and sign up. The fastest way is Continue with Google. You can also use an e-mail address and a password.
You'll be asked for your country. Pick the one you actually work from: it sets the currency and the price grid of your account, and it is a one-time choice.
Step 2 — Confirm your e-mail address
If you signed up with an e-mail and password, we send you a confirmation link. Click it before anything else. It is what releases your welcome credit, and deploying needs that credit to be there.
Until you confirm, a banner at the top of the dashboard reminds you and lets you send the link again. The link stays valid for 48 hours — and if you can't find it, check your spam folder.
Signed up with Google? Your address is already confirmed. Skip this step entirely.
Step 3 — Create a project
From your dashboard, click + to create a new project and give it a name. A project holds one application and the databases that go with it — so a project per app keeps things tidy.
Step 4 — Connect your GitHub account
In the launcher, pick the Github | Gitlab card and connect with GitHub. The first time, GitHub asks you to install the Qeda app on your account or your organization, and to choose which repositories it may read. You can share a single repository — you don't have to open your whole account.
Once installed, your repositories appear in the picker. If you have both a personal account and an organization, a switcher lets you move between them.
Step 5 — Choose your repository and check the variables
Select the repository. Qeda detects your language and framework and prepares the build — you don't declare anything.
Before deploying, open the Variables tab. Qeda has already read the environment variables your code expects — from your .env.example and from the code itself — and pre-filled what it could. Secrets such as a SECRET_KEY get a generated value. Add what only you know: API keys, third-party tokens.
Never commit a real .env file to your repository. Variables set here are encrypted and injected into your app when it starts.
Step 6 — Deploy
Click Deploy. The build logs stream live, line by line, so you can watch your dependencies install and your app build. The status on your service moves from Building to Running.
A first deployment usually takes one to three minutes, depending on how many dependencies your project installs. Later deployments are faster: layers that didn't change are reused.
Step 7 — Open your app
When the status turns to Running, your app has a public address ending in .apps.qeda.io, with HTTPS already set up. Open it in your browser, or test your API directly:
$ curl https://your-app.apps.qeda.ioThat's it. Send the link to a teammate, a client, a recruiter — it keeps answering long after you have closed your laptop.
Going further
Add a database. From your project, add a PostgreSQL, MySQL, MongoDB or Redis database. Qeda provisions it and injects the connection details into your app as environment variables — DATABASE_URL and friends. Read them from the environment in your code, never hard-code them.
Use your own domain. Point api.yourproject.com at your app from its Settings tab — the certificate is issued for you. Our custom domains guide walks through it.
Deploy an image instead. Already have a public Docker image? Choose Docker in the launcher, paste the image reference — nginx:alpine, ghcr.io/you/app:latest — and it goes live without any build.
Redeploy on every push. When you push new commits, the dashboard shows them and lets you deploy the new version in one click.
If a build fails
Read the top of the build log. Qeda names the cause in plain language and tells you what to change — a missing variable, a Python version your framework can't run on, a build step that expects a database. Most first failures are one of a handful of known problems, and the message points straight at the fix.
Deploying Django? Our Django guide covers the three errors that trip up most first deployments.
What we'd love from you
You are not testing a finished product — you are shaping it. Tell us what broke, what confused you, what took longer than it should have, and what you wish existed.
Join the Qeda Community on Discord. Every message is read by the people building the platform, and a lot of what ships next will come from there.
Deploy something real. Then tell us what got in your way.
Get started
Create your account, confirm your e-mail, connect GitHub and deploy. Ten minutes from now, your project can have its own address on the internet.