Base44 guides

Connect a custom domain

1. Dashboard → Domains → Connect existing domain.
2. At your DNS provider add A @ 216.24.57.1 and CNAME www base44.onrender.com. Delete every AAAA (IPv6) record for those names.
3. On Cloudflare, set both records to DNS only (grey cloud). The orange proxy breaks verification and SSL.
4. Turn off any forwarding or parking at the registrar; it adds a hidden A record.
5. Click Verify. Allow up to 72 hours; after 30 minutes stuck, unlink and re-add.

The www → root redirect can't be changed. Keep the www CNAME so www loads.

GitHub sync: what's permanent

• Connecting is irreversible: you can't go back to Base44-only, and Version History from before the connection can't be restored.
• Sync is automatic only; there's no manual push. The default branch must be main.
• Entities aren't in the repo; they stay managed in Base44.
• Disconnect a repo and you can never reconnect to the same repository name.
• Needs the Builder plan or higher.

Public landing page on a private app

Visibility is app-wide, so a Private app asks for login on every page. Two working patterns:

1. One public app with RLS rules on every entity plus redirects for signed-out users on private pages.
2. Two apps: the public landing app on your main domain, the private app on a subdomain (app.yourdomain.com).

Why credits drain

• Building in regular mode when Discuss (0.3 credits per message) would do. Plan in Discuss, switch to build only to execute.
• "Small" one-line requests that touch many files (translate the app, make it mobile) cost 3–4 credits.
• Agents on expensive models, hourly workflows, and emails from a custom domain (2 credits each).
• Credits are pooled per workspace; one client's runaway automation spends another's budget.

Estimate your running cost