You have just deployed your application on Qeda — it works, and you already have a URL like https://my-project.qeda.app. That's perfect to get started.
But if you already have your own domain, you'll probably want something like https://myproject.com, or for an API, https://api.myproject.com. It's easier to share, more professional, and lets your users access your application under your own brand.
With Qeda, you can connect your domain to your application without having to manage the infrastructure part yourself. In this guide, we will see how to do it in 5 steps.
Make sure your application is already deployed
Before connecting your domain, your application must already be online on Qeda — for example, at https://my-project.qeda.app. Open this address in your browser and check that it works correctly. If it works on its Qeda URL, you're ready to move to the next step: the idea is simply to connect the domain to an application that already works.
Add your domain in Qeda
From your Qeda Dashboard, open the application you want to connect your domain to. In its Settings tab, look for the Public Networking section — this is also where you can rename your .qeda.app subdomain. Below it, add your custom domain: something like myproject.com, or, for an API subdomain, api.myproject.com. Qeda will then show you the information needed to connect it.
Configure your domain
This step happens with the provider where you bought your domain — your registrar or your usual domain host. You'll simply need to add or update the DNS record requested by Qeda: a CNAME record pointing to the target address shown right under the Add Domain field. You don't need to understand all of DNS management to connect your application — just follow the information displayed in your Dashboard. The exact screens and values may vary depending on your domain provider.
Verify the connection
Once the DNS configuration is done, go back to your Qeda Dashboard: Qeda will check that your domain correctly points to your application. DNS propagation can sometimes take a little time, so there's no need to change your configuration several times if it doesn't work immediately — simply wait, then check again. When the domain is correctly configured, it appears as a clickable entry in your Public Networking list, and your application can be accessed with your own address, such as https://myproject.com.
Use your domain with HTTPS
Once your domain is connected, Qeda also handles HTTPS for your application — your URL becomes https://myproject.com, not just http://myproject.com. This matters for any publicly accessible application, especially one using user accounts, forms, or an API. You do not need to manage SSL certificates manually: the certificate is provisioned automatically as soon as your DNS resolves.
That's it
You went from https://my-project.qeda.app to https://myproject.com in just a few steps. Your application remains deployed on Qeda, and you can keep using your usual workflow — code, Git, Qeda, deploy — your domain stays associated with your application as it evolves, and you simply continue deploying new versions as before.
A few examples
A custom domain can be useful in several situations:
- For a website or application:
https://myproject.com - For an API:
https://api.myproject.com - For a SaaS application:
https://app.myproject.com - For a client project: use the client's domain directly instead of asking them to use a
qeda.appURL
The benefit is always the same: your application uses the address your users already know.
Conclusion
Already have a domain? Connect it to your Qeda application in a few steps and use your own address with HTTPS — your domain, your brand, your application: Qeda handles the rest.