Custom Domains & SSL Provisioning

NoCodeBackend enables you to attach your own branded domain or subdomain (e.g., api.yourcompany.com) to your databases. This allows you to deliver fully white-labeled REST APIs with automated SSL/TLS certificates and global edge routing.

1. Overview: Why Use a Custom Domain?

By default, all NoCodeBackend REST APIs are accessed via our standard domain:

https://api.nocodebackend.com/v1/{database_instance}/{table_name}

While great for development, attaching your own custom domain provides substantial advantages:

• Brand Professionalism: Client applications, mobile apps, and third-party webhooks communicate directly with your company's domain (https://api.yourcompany.com/v1/...).
• White-Label API Delivery: If you build SaaS applications or client solutions as an agency, your end users never see the NoCodeBackend infrastructure name.
• Enterprise Compliance: Meets enterprise security policies that require all traffic to be routed through company-owned domain namespaces.
• Zero-Maintenance SSL: NoCodeBackend automatically provisions, validates, and renews high-grade TLS 1.3 SSL certificates via Let's Encrypt and Cloudflare edge proxies.

2. Plan Eligibility

Custom Domain routing is an advanced feature available on the following plans:

• Professional Plan: Included.
• AppSumo Tier 3, Tier 4, and Tier 5: Included.
• Custom domain capacity limits can be reviewed at any time under Billing → Limits.

3. Step-by-Step Guide: Connecting a Custom Domain

Step 3.1: Add Your Domain in NoCodeBackend

1. Log in to your NoCodeBackend dashboard.
2. In the sidebar or navigation menu, click Custom Domain (or navigate to /custom-domain).
3. Click + Add Custom Domain.
4. Enter the subdomain you want to use (e.g., api.mycompany.com or data.mybrand.io).

   💡

   Recommendation: We strongly recommend using a dedicated subdomain like api. or backend. rather than your root apex domain (mycompany.com), so your primary marketing website remains untouched.

5. Click Submit.

Step 3.2: Configure DNS Records at Your Registrar

Once submitted, NoCodeBackend generates the exact DNS records required for verification.

Log in to your DNS provider (e.g., Cloudflare, Namecheap, GoDaddy, AWS Route 53, or Google Cloud DNS) and add the following record:

| Type | Name / Host | Target / Points To | TTL | | :--- | :--- | :--- | :--- | | CNAME | api (or your chosen subdomain) | proxy.nocodebackend.com | Auto (or 300s) |

💡

Cloudflare Users: If your DNS is managed via Cloudflare, set the Proxy status to DNS only (Grey Cloud) during initial verification so Let's Encrypt certificate challenges can reach our edge verification nodes directly.

Step 3.3: Automatic SSL Provisioning & Verification

1. Return to the NoCodeBackend Custom Domain dashboard.
2. Click Verify DNS & Check SSL.
3. NoCodeBackend will query global DNS servers:
   • Once the CNAME record is detected, our automated certificate manager requests and provisions a dedicated SSL certificate.
   • The status badge will change from Pending DNS → Active (SSL Secured).

4. Associating Domains with Databases

Once your domain is active, you can link it to one or more databases:

1. On the Custom Domain dashboard, locate your verified domain.
2. Click Manage Associations.
3. Select which database instance(s) should be served by this custom domain.
4. Click Save Changes.

5. Making Authenticated API Calls

Once associated, your custom domain behaves identically to the default API endpoint:

Example: Making a Request via Your Custom Domain

curl -X GET "https://api.mycompany.com/v1/your_database/users" \
  -H "Authorization: Bearer ncb_sec_your_secret_key" \
  -H "Content-Type: application/json"

Example: Frontend Fetch (JavaScript)

const response = await fetch("https://api.mycompany.com/v1/your_database/tasks", {
  method: "GET",
  headers: {
    "Authorization": "Bearer ncb_sec_your_secret_key",
    "Content-Type": "application/json"
  }
});
const tasks = await response.json();

6. Removing or Changing Domains

To disconnect a domain:

1. Navigate to /custom-domain.
2. Click the Remove (Trash) icon next to the domain.
3. Confirm the removal.
4. The SSL certificate and proxy mapping will be safely decommissioned, and you can delete the CNAME record from your DNS registrar.

7. Troubleshooting

Common Errors

Error: DNS record not detected (Status: Pending DNS)

• Cause: DNS changes can take anywhere from a few minutes up to 24 hours to propagate across global nameservers.
• Resolution: Use a free DNS checker (like whatsmydns.net) to verify that your CNAME record for api.yourcompany.com resolves to proxy.nocodebackend.com. Once it resolves globally, click Verify DNS again.

Error: SSL Handshake Failed / Certificate Error

• Cause 1: Your domain registrar has restrictive CAA (Certificate Authority Authorization) records blocking Let's Encrypt from issuing certificates.
  • Resolution: Add a CAA record in your DNS settings: 0 issue "letsencrypt.org".
• Cause 2: Cloudflare's Orange Cloud (proxied) was enabled before the SSL certificate was provisioned.
  • Resolution: Toggle Cloudflare to DNS only (Grey Cloud) for the record, wait 2 minutes, and re-verify in NoCodeBackend.