Skip to main content
Fleack’s entire integration is one DNS record. You add a CNAME on a hostname you already control — the one your app calls today — and point it at the Fleack tenant hostname provisioned for you during onboarding. This page walks you through the setup, shows you how to confirm the edge is live, and explains three ways to test without touching production DNS.

​
What you’re configuring

You own your app’s API hostname. Fleack provides a tenant hostname. You connect them with a CNAME:
You controlFleack provides
api.your-game.comapi-<tenant-id>.fleack.io
The <tenant-id> is shown on your Fleack dashboard as soon as your account is provisioned. You do not need to configure anything on the Fleack hostname itself — Fleack reads the Host header from each incoming request to route it to your tenant.

​
Setting up DNS

1

Retrieve your tenant hostname

Sign in to the Fleack backoffice and open Settings. Copy the tenant hostname — it follows the format api-<tenant-id>.fleack.io.
2

Add the CNAME record

In your DNS provider, add a CNAME record on the hostname your app already calls:
api.your-game.com  CNAME  api-<tenant-id>.fleack.io
TTL can be left at your provider’s default. A shorter TTL (60–300 s) makes it easier to roll back quickly if needed.
3

Wait for propagation

DNS changes typically propagate within a few minutes, though global propagation can take up to 48 hours depending on your provider and any upstream caches. In practice, most providers complete this in under five minutes.
4

Verify the edge is live

Run the three commands below to confirm everything is working:
# Should resolve to a Fleack address
dig +short api.your-game.com

# Should return your real backend's response, unchanged
curl -sS https://api.your-game.com/api/health

# Should show Fleack's edge headers
curl -sIS https://api.your-game.com/api/health | grep -i x-fleack
If the third command returns x-fleack-tenant: <your-tenant-id>, the Fleack edge is correctly receiving and forwarding your traffic.
Until you launch a test, every response through Fleack is byte-identical to what your backend sends directly. Fleack acts as a transparent proxy until you activate a variant.

​
Testing without changing production DNS

If you need to validate the integration before touching your production hostname, you have three options:
Add a separate CNAME on a test hostname — for example fleack-test.your-game.com — pointing to the same Fleack tenant hostname:
fleack-test.your-game.com  CNAME  api-<tenant-id>.fleack.io
Configure your dev or staging app build to call fleack-test.your-game.com instead of api.your-game.com. You can run real tests against staging traffic for as long as you need before flipping the production record.This is the recommended approach for team-wide pre-production testing.

​
Rolling back

Removing Fleack from the path is as simple as deleting or updating the CNAME. As soon as DNS propagates, your app calls your real backend directly again. No code changes, no app update, no downtime window required.