> ## Documentation Index
> Fetch the complete documentation index at: https://docs.skyfree.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Railway for SaaS

> Onboard whitelabel customer domains through Railway instead of Cloudflare.

## What is this?

The **Railway for SaaS** tab lets you optionally onboard whitelabel customer domains through [Railway](https://railway.app) instead of Cloudflare.

<Info>
  **Requires the White-Label add-on.** This tab is part of the White-Label add-on. Without it, the tab doesn't appear in Whitelabel Setup — use [Cloudflare for SaaS](/self-host/whitelabel-setup/cloudflare-saas) instead. See the [Self-Hosted overview](/self-host/overview) to compare the two levels.
</Info>

<img src="https://mintcdn.com/mail2skyfreegmailcom/TMRlP9xN8aYGfnKu/images/whitelabel-setup-railway-tab.png?fit=max&auto=format&n=TMRlP9xN8aYGfnKu&q=85&s=9c226937416b6bb1ccd99a4e71b17769" alt="The Railway for SaaS tab with the Enable Railway for SaaS and Use Railway for whitelabel setup switches, Railway API Token field, and Project ID / Environment ID / Service ID / Fallback CNAME Target fields" width="1282" height="953" data-path="images/whitelabel-setup-railway-tab.png" />

## What can I do here?

* Toggle **Enable Railway for SaaS** — allow storing Railway config for domain onboarding.
* Toggle **Use Railway for whitelabel setup** — if enabled, managed whitelabel purchases use Railway domain onboarding instead of Cloudflare.
* Enter your **Railway API Token**.
* Enter your **Project ID**, **Environment ID**, and **Service ID** for the Railway project that should host onboarded domains.
* Enter a **Fallback CNAME Target** (e.g. `example.up.railway.app`).
* Click **Test** to verify the Railway API Token is valid (confirms the connected account).
* Click **Edit** to unlock the fields, then **Save** to persist changes (or **Cancel** to discard).

## How to use it

1. Click **Edit** to unlock the form.

2. Paste your **Railway API Token**.

   <img src="https://mintcdn.com/mail2skyfreegmailcom/OO2U_FWAO_6BJhiB/images/whitelabel-setup-railway-edit.png?fit=max&auto=format&n=OO2U_FWAO_6BJhiB&q=85&s=efc295f483a8acb4fe7c633bacc8f382" alt="The Railway for SaaS form in edit mode with the API token and project fields active" width="1282" height="953" data-path="images/whitelabel-setup-railway-edit.png" />

3. Fill in the **Project ID**, **Environment ID**, and **Service ID** for the Railway service that will handle onboarded domains.

4. Set the **Fallback CNAME Target** — the Railway-provided hostname (e.g. `example.up.railway.app`) that customer CNAMEs should point to.

5. Turn on **Enable Railway for SaaS** to activate the integration.

6. If you want new whitelabel purchases to use Railway (rather than Cloudflare) for domain onboarding, also turn on **Use Railway for whitelabel setup**.

7. Click **Save**.

8. Use **Test** at any time afterward to confirm the API token still authenticates successfully against Railway.

\[NEEDS VERIFICATION] The exact end-to-end domain-onboarding flow a customer sees when Railway is the active provider (equivalent to the "How it works for users" steps shown on the Cloudflare tab) is not described in this component — it isn't shown to the admin here.