Base44 Custom Domain and Deployment Guide

By jocapps5 min read

Short answer: To run a Base44 app on your own domain, decide on the domain structure, add the domain in your Base44 app settings, create the DNS records Base44 shows at your registrar, wait for verification and the SSL certificate, then update email sender domains, login redirects and integrations. Treat publishing as a release process with testing before and checks after, even on a managed platform.

On this page

The short version

Base44 hosts and publishes your app for you, and on supported plans you can connect a custom domain. The core process is the same as with any modern host: you tell the platform which domain to serve, the platform tells you which DNS records to create, you create them at your domain registrar or DNS provider, and the platform verifies the domain and issues an SSL certificate. Menu names and plan requirements can change, so follow the current Base44 documentation for the exact clicks.

Most of the real work is around that process: choosing the right structure, avoiding DNS conflicts, and updating everything else that refers to your old address.

Plan your domain structure first

Decide where the app lives before touching DNS. Changing it later breaks bookmarks, emails and mobile app configurations.

  • App on a subdomain (app.example.com): the most flexible choice. Your marketing site stays on the main domain, possibly on a different platform optimized for content and SEO.
  • App on the main domain (example.com): simple for single-purpose tools, but the app then has to serve as your website, which Base44 apps are not usually designed for.
  • Separate domain per client: possible for white-label products, but every domain needs its own setup and certificate, so check what your plan supports.
  • Redirects: decide whether www redirects to the apex or the other way round, and implement it consistently.

Connecting the domain step by step

This sequence avoids the typical failure modes. Have access to your registrar or DNS provider ready before you start.

  1. Check which DNS provider actually controls your domain by looking up its nameservers; it may be Cloudflare or your web host rather than the registrar.
  2. Lower the TTL of any existing records for the chosen hostname a day in advance.
  3. Add the custom domain in your Base44 app's settings and copy the DNS records it displays, exactly as shown.
  4. Create those records at the DNS provider, usually a CNAME for subdomains or A records for an apex domain, and remove conflicting old records for the same hostname.
  5. If you use Cloudflare, start with the proxy disabled (DNS only) so the platform can verify the domain and issue its certificate.
  6. Wait for verification in Base44, then open the domain in a private window and on mobile data to confirm HTTPS works.
  7. Set up the redirect from the alternative hostname, such as www, to your canonical domain.

Need a hand? apprat.io helps with exactly this. Book a call for free and get a clear plan in 15 to 30 minutes.

When the domain does not work

Most problems fall into a few categories. If verification hangs, the record usually has a typo, sits at the wrong DNS provider, or conflicts with an existing A, AAAA or CNAME record for the same name. Some registrars append the domain automatically, so entering app.example.com as the host creates app.example.com.example.com; enter only app in that case.

If the domain loads but shows a certificate warning, the certificate may not be issued yet, or a proxy in front of the domain is serving its own certificate. If the app loads but login fails, the authentication settings still expect the old address. Patience helps with DNS, but if nothing changes after a few hours, recheck the records with a public DNS lookup tool rather than waiting longer.

Update everything that points to the old address

Changing the domain is only half done when the site loads. Go through every place that stores the app's URL: email templates and invitation links, login redirect settings and OAuth providers, payment success and cancel URLs, webhook endpoints registered with external services, and links in your marketing site, onboarding emails and help articles.

Configure email authentication as well. If the app sends emails from your domain, add the SPF, DKIM and DMARC records your email provider specifies, or messages will land in spam. If you plan to wrap the app for iOS and Android, point the native apps at the custom domain from day one and host any required association files there, so deep links keep working.

Publishing as a release process

On Base44, publishing is a click, which makes it easy to ship an untested change to everyone. Introduce a small routine: make changes in the editor, test them in the preview, run through your critical flows, then publish at a time when someone can watch for problems. Keep a short changelog of what was published and when, so you can relate user reports to changes. Before larger changes, export your data so you have a fallback.

If your app is growing into a product with paying users, apprat.io can take over this release discipline, including domain and SSL setup, environment separation and monitoring, through its Base44-to-App and Prototype-to-Production modules. Coding agents implement, senior AI Code Engineers review every change, and apprat.io documents the setup so your team stays in control.

Frequently asked questions

Does Base44 support custom domains on every plan?

Custom domain support is typically tied to paid plans on hosted app builders, and plan features change. Check Base44's current pricing and documentation to confirm which plan you need. If your app needs several domains, for example for white-label clients, confirm the limit before committing to that architecture.

How long does it take for a Base44 custom domain to work?

Once the DNS records are correct, verification and certificate issuance often complete within minutes to a few hours. Delays usually come from records at the wrong DNS provider, conflicting old records, a high TTL or a proxy in front of the domain. A public DNS lookup quickly shows what the internet currently sees.

Can I use Cloudflare in front of my Base44 app?

You can usually manage DNS at Cloudflare. Whether the Cloudflare proxy can stay enabled depends on how the platform verifies domains and issues certificates. Start with DNS only, confirm the domain and HTTPS work, and only then test enabling the proxy, watching for certificate and redirect issues.

Talk to an AI Code Engineer, free of charge

Tell us where you are and where you want to go. In a short call we map out the fastest path, whether that is a workshop, a launch in the App Store and Google Play or a full AI-native product.

No obligation. English or German. Run by jocapps, ISO 27001 and ISO 9001 certified. Prefer the phone? 24/7 call support: +49 761 519 751 50

Book a call for free

Related guides

Book a call for free