Base44 Custom Domain Setup: How to Connect Your Domain

Is your Base44-generated app ready to launch but still stuck on a generic Base44 URL?

As of August 2026, Base44’s Builder plan, the entry tier that supports custom domains, costs $40 per month when billed annually or $50 month-to-month, with 250 message credits and 10,000 integration credits (Source).

A branded address can make your app look launch-ready, but connecting one involves more than typing in a domain name. You must configure DNS records, verify ownership, activate SSL, and retest authentication, emails, payments, and other Base44 integrations.

This guide explains how to connect and troubleshoot a custom domain, what your Base44 subscription must include, and how to move the domain safely during a Base44 migration. It also provides a focused Base44 review of the platform’s domain support, integration requirements, and migration limitations, helping you decide when a domain upgrade is enough and when a more flexible Base44 alternative may be needed.

Requirements for Connecting a Custom Domain to Base44

Before changing your app’s web address, make sure you have the right Base44 subscription, ownership of the domain, and access to its DNS settings. Without these prerequisites, the domain may fail to verify or remain unavailable after setup.

Which Base44 Subscription Supports Custom Domains?

Every Base44-generated app receives a default address in the format yourapp.base44.app. Connecting a separate branded domain, such as yourbusiness.com, requires a plan that supports custom domains.

Check your current subscription before starting the setup process to confirm that the feature is available.

Choose a Domain for Your App

You can connect an existing domain or purchase a new one through Base44’s supported domain-purchase options.

Before using an existing domain, confirm that:

• The registration is active.

• You control the registrar account.

• The domain is not connected to another website you still need.

• You have chosen whether to use the root domain, www, or a subdomain.

For example, you may connect:

• yourbusiness.com

• www.yourbusiness.com

• app.yourbusiness.com

A subdomain can be useful when the main domain already hosts a website and the Base44 app needs a separate address.

Get Access to Your Domain’s DNS Settings

When connecting a domain managed through an external registrar, you must update its DNS records using the values shown in the Base44 dashboard.

Make sure you can access the registrar’s DNS management panel and edit the required A, CNAME, or verification records. Save a copy of the existing DNS configuration before making changes, especially when the domain is also used for business email or another online service.

After the records are added and verified, Base44 can connect the domain and enable HTTPS for the app.

How to Connect a Custom Domain to Base44: Step-by-Step

Connecting a custom domain requires you to add the domain in Base44, update its DNS records, and verify the connection. Use the exact values shown in your Base44 dashboard because DNS requirements may change.

Step 1: Add Your Domain and Choose the Right Format

Open the Base44 app you want to publish and go to:

App Editor → Dashboard → Domains

Select Connect existing domain, then enter the address you want visitors to use.

Common options include:

• yourbusiness.com for the root domain

• www.yourbusiness.com for the www version

• app.yourbusiness.com for a subdomain

Use the root domain when the Base44 app will serve as the main website or product. Use a subdomain when the primary website is hosted elsewhere, and the app needs a separate address for a portal, dashboard, booking system, or internal tool.

Enter only the domain name. Do not include https:// or a page path.

Base44 supports specific subdomains rather than wildcard entries, so each address must be connected separately.

Step 2: Add the Required Base44 DNS Records

Sign in to the registrar or DNS provider that manages your domain. Open the DNS settings and add the records shown in the Base44 dashboard.

For a root domain, Base44 recommends an ANAME or ALIAS record when the provider supports it:

Type: ANAME or ALIAS

Name: @

• Value: base44.onrender.com

For the www version, add:

• Type: CNAME

• Name: www

• Value: base44.onrender.com

When the DNS provider does not support ANAME or ALIAS records, the root domain can use:

• Type: A

• Name: @

• Value: 216.24.57.1

For a subdomain such as app.yourbusiness.com, add:

• Type: CNAME

• Name: app

• Value: base44.onrender.com

Do not change MX records unless you intend to modify the domain’s email service. MX records control email delivery and are not normally required to connect the app.

Step 3: Remove DNS Records That Conflict With Base44

Review any existing records attached to the same hostname.

Records that may prevent the connection include:

• Additional A records pointing the root domain elsewhere

• AAAA records for the hostname being connected

• CAA records that block SSL certificate issuance

• A or AAAA records that conflict with a CNAME

• Default parking records added by the registrar

Only remove records that affect the hostname you are connecting. Avoid deleting email, verification, or service records that are still required.

Step 4: Verify Your Custom Domain in Base44

Return to:

App Editor → Dashboard → Domains

Locate the domain and select Verify.

Base44 will check whether the DNS records point to the required destination. The status may remain pending until the updated records are visible across DNS networks.

If the domain does not verify immediately, allow time for the changes to propagate before editing the records again.

Step 5: Confirm HTTPS and Test Your Base44 Custom Domain

After verification, Base44 issues an SSL certificate so the app can load securely over HTTPS.

Test every connected version, including:

• https://yourbusiness.com

• https://www.yourbusiness.com

• https://app.yourbusiness.com

Confirm that the intended address loads the Base44 app without a certificate, privacy, or connection warning.

The domain is now connected, but the app should not be considered launch-ready until authentication, emails, payments, analytics, and other Base44 integrations have also been tested.

How to Disconnect or Transfer a Custom Domain From Base44

Disconnecting a custom domain removes its connection to the Base44-generated app. It does not cancel the domain registration or automatically point the address to another platform.

Make sure the new destination is ready before removing the domain to avoid unnecessary downtime.

Unlink the Custom Domain From Your Base44 App

To remove a connected domain:

1. Open the app in Base44.

2. Go to Dashboard → Domains.

3. Select the domain you want to remove.

4. Click Unlink Domain.

5. Use the delete option to remove it from the app’s domain list.

Complete both actions before connecting the same domain to another Base44 app or platform.

Remove the Existing Base44 DNS Records

Unlinking the domain from the app does not update the records managed by your registrar or DNS provider.

Remove or replace the records that direct the domain to Base44, such as:

• An A record pointing to 216.24.57.1

• A CNAME pointing to base44.onrender.com

• Any other Base44-specific routing record

Leave unrelated records unchanged, particularly those used for business email, domain verification, or third-party services.

Point the Domain to a New App or Platform

Add the domain to the receiving platform and replace the Base44 DNS values with the records provided by the new host.

When moving the domain to another Base44 app, confirm that it has been fully removed from the original app before reconnecting it.

The domain may continue loading the old destination temporarily while the new DNS records propagate.

What Happens After Disconnecting a Base44 Domain?

After the domain is removed:

• It no longer points to the Base44 app once the DNS records are updated.

• The app may remain available through its built-in base44.app address.

• Base44 stops managing SSL for the disconnected domain.

• Existing links using the custom domain may stop working.

• Services that still reference the old address may need to be updated.

Avoid changing the app’s built-in Base44 URL during the same transition unless necessary, because the previous built-in link may stop working immediately.

Best Domain Providers for a Base44-Generated App

Base44 can work with any registrar that allows users to manage the DNS records required to connect a custom domain.

The best provider depends on the level of DNS control, ease of use, support, security, and long-term pricing you need.

Namecheap for Base44 Custom Domains

Namecheap is a practical option for small businesses and users connecting a custom domain for the first time. Its dashboard makes it relatively easy to manage the A, CNAME, and other records required for a Base44-generated app.

Cloudflare Registrar for Base44 Custom Domains

Cloudflare Registrar is better suited to teams that want advanced DNS management, DNSSEC, and additional security controls.

When connecting a domain to Base44, keep the relevant records set to DNS only during verification rather than routing them through Cloudflare’s proxy.

Porkbun for Base44 Custom Domains

Porkbun provides a straightforward domain-management experience and is well suited to developers, startups, and small teams.

It offers the DNS controls needed to connect a Base44 app without adding unnecessary setup complexity.

GoDaddy for Base44 Custom Domains

GoDaddy may be convenient for businesses that already manage their domains and related services through the platform.

Before updating the records, confirm that the domain is using GoDaddy nameservers. When the nameservers point elsewhere, DNS changes must be made through the active DNS provider.

Name for Base44 Custom Domains

Name can be considered by users who want straightforward domain registration and DNS management.

Before choosing it for a Base44 app, confirm that its DNS dashboard supports the record types required by Base44 and that you can easily manage renewals, ownership verification, and future domain transfers.

How to Choose a Domain Provider for Base44

Compare providers based on:

• Renewal pricing

• DNS controls

• Account security

• Customer support

• Domain privacy

• Transfer policies

The right registrar should make it easy to retain ownership of the domain while giving you enough control to connect, troubleshoot, or move your Base44 app later.

Conclusion: When Should You Consider a Base44 Alternative?

A custom domain can make a Base44-generated app look more professional, but it cannot remove limitations related to application logic, integrations, permissions, deployment, or scalability.

For teams that have outgrown a basic prompt-to-app workflow, CodeConductor is the best Base44 alternative. It enables businesses to migrate their existing screens, workflows, data structure, and integrations into a more flexible application environment without rebuilding everything from scratch.

With custom logic, persistent memory, role-based permissions, advanced integrations, and greater deployment control, CodeConductor provides a clearer path from an early Base44 prototype to a production-ready application.

FAQs

Can I Connect a Custom Domain to Base44 for Free?

No. Base44 custom domains are available on Builder, Pro, and Elite plans. Free-plan apps use a built-in address such as yourapp.base44.app.

How Long Does Base44 Custom Domain Verification Take?

A domain may verify within minutes, but DNS changes can take up to 72 hours to propagate. Incorrect or conflicting DNS records may extend the process.

Do Base44 Integrations Work After Changing the Domain?

Most integrations continue working, but OAuth redirects, allowed origins, email links, payments, and analytics may need updating. Test every critical workflow through the live custom domain.

Can I Migrate a Base44-Generated App to Another Platform?

Eligible Base44 plans support GitHub synchronization and code export as a ZIP file. However, data, authentication, integrations, and Base44-specific services may require separate migration work.

What is the Best Base44 Alternative for Growing Apps?

CodeConductor is the best Base44 alternative for teams needing greater control over app logic, integrations, permissions, deployment, and scalability. It also provides a structured path for extending an existing Base44 app.