Publish & domains

Ship a public URL from the editor. Every project gets a default Appbricx subdomain; on Pro and above you can also attach your own hostname (for example crm.focode.cloud or focode.cloud).

Default publish

1. Open the project editor → Deploy / Publish.
2. Appbricx builds and serves the site at https://<subdomain>.apps.appbricx.com (for example https://crm360-uczkb.apps.appbricx.com).
3. Runtime paths /__appbricx/* and /hooks/* proxy to the API on published hosts.

The default URL always works after a successful publish. You do not need a custom domain to share or demo the app.

Custom domains

Custom domains are a Pro+ feature. The project must be published at least once before you can add a domain.

What you need

• A domain you control (example used below: focode.cloud).
• Access to that domain's DNS panel (registrar or Cloudflare).
• A Pro (or higher) workspace on Appbricx.

Step-by-step (recommended: subdomain)

Prefer a subdomain such as crm.focode.cloud or app.focode.cloud. Apex domains work too, but DNS is often harder (see below).

1. Open the project → Settings → Custom Domain.
2. Enter the hostname, for example crm.focode.cloud, and click Add Domain.
3. In your DNS provider for focode.cloud, create the record shown in the Appbricx UI. Typical values:

   Type	Name	Target / Value
   CNAME	crm	sites.appbricx.com

   Some registrars want the full name (crm.focode.cloud) instead of just crm — use whichever form their UI expects.
4. Wait for DNS to propagate (often a few minutes; sometimes up to an hour). Check with:

   dig +short CNAME crm.focode.cloud
   # expect: sites.appbricx.com.

5. Back in Appbricx, click Verify. When status is active, open https://crm.focode.cloud. TLS is issued automatically on first visit.

Using the apex (focode.cloud)

You can attach the bare domain focode.cloud the same way in Settings. Many DNS providers do not allow a CNAME on the apex, so use one of:

• A record → platform IP (shown in Settings when an A target is offered; production is typically 77.37.44.44), or
• An ALIAS / ANAME / flattened CNAME to sites.appbricx.com if your DNS host supports it.

Then click Verify and visit https://focode.cloud.

Cloudflare tip

• Prefer DNS only (grey cloud) when CNAMEing to sites.appbricx.com, unless Appbricx shows a Cloudflare Tunnel target and you intentionally orange-cloud that tunnel hostname.
• Orange-cloud proxy to the wrong target often breaks verification or TLS.

Multiple custom domains

A project can have more than one custom domain (for example crm.focode.cloud and app.focode.cloud). Add each hostname, point DNS, and Verify. Delete any domain you no longer need from the same settings panel — the default *.apps.appbricx.com URL is unaffected.

After a domain is active, Appbricx also allows that hostname on the project's publish API key (SDK / connector calls). If you see Request origin … is not in this key's allowed origins, click Verify once more on the domain (or re-publish) so origins sync.

• Settings shows the domain as active.
• https://crm.focode.cloud (or your chosen host) loads the same published app as https://<subdomain>.apps.appbricx.com.
• The default *.apps.appbricx.com URL still works.
• Browser shows a valid certificate for your hostname (Let's Encrypt), not ERR_SSL_PROTOCOL_ERROR.

Common failures

• Free plan — upgrade the workspace first.
• Project never published — publish once, then add the domain.
• DNS still pointing elsewhere, or CNAME not propagated yet.
• Trying to use an Appbricx hostname as the custom domain (blocked).
• Verify clicked too early — wait for dig / your DNS panel to show the correct target, then retry Verify.
• ERR_SSL_PROTOCOL_ERROR with HTTP redirect working — DNS reached the server, but HTTPS for that hostname was not configured yet. Click Verify again (even if status already says active) so Appbricx reloads the publish edge, then hard-refresh. First HTTPS visit mints the certificate (can take a few seconds).
• An A record pointing at the platform IP (for example 77.37.44.44) is also valid if the UI offered that path — it does not have to be a CNAME to sites.appbricx.com.

Preview vs published

• Preview — editor iframe / /preview/<id>/, hot reload while building.
• Published — immutable build for end users; use for demos you share externally (default subdomain or custom domain).

Related: Export & GitHub if you want to host elsewhere.