Portals
Create, publish, archive and restore portals, and route domains to them
A portal is one player-facing site with its own game servers, content and commerce. The plan sets how many portals the organization can run.
Creating a portal
- On Overview, choose New portal.
- Enter the Portal name and the Subdomain identifier — lowercase
letters, digits and hyphens. The identifier becomes the portal address:
<identifier>.forgeport.net. A Tagline is optional. - Create the portal. You land in its Admin Console, where the Game Servers page walks through connecting the first server.
Launch Checklist
Admin → Launch Checklist tracks the gates between a fresh portal and a launched one, with a completion percentage. Each row links to the page where it is completed.
| Gate | Required | Done when |
|---|---|---|
| Portal identity | Yes | The portal has its name and included address |
| Game server connected | Yes | A connector is connected and ready |
| Portal published | Yes | Players see the full portal |
| Stripe (or Stripe test) | Yes | The connected Stripe account is active |
| Coin packages | Yes | At least one coin package is enabled |
| Custom domain | Optional | A custom domain is active |
The two payment gates appear in deployments where Stripe payments are enabled.
Publishing
A portal is Live or Not published. While unpublished, players see the Coming Soon page and the configuration and data remain unchanged — publishing is the switch that opens the full portal. Publish portal and Unpublish sit on the portal page in the organization console and on the Admin Console dashboard.
Archiving and restoring
Archive on the portal page removes the portal from your workspace immediately; its content is deleted after 30 days. Until then it appears under Archived on Overview with a Restore button and the days remaining. Restoring returns the portal with the content it had when archived.
Purchases inside the refund window
Archiving keeps the refund route open. Purchases still inside the 14-day refund window are honored: affected players are emailed within an hour with a link to claim a refund, and refunds keep working while the window is open. Restoring the portal within that hour cancels the email.
Domains
Every portal ships with its included subdomain, <identifier>.forgeport.net.
Its switch lives on the portal page and under Domains → Included
subdomains — turn it off once a custom domain is active, if you don't want
both reachable.
Adding a custom domain
- On Domains, choose Add domain and enter the hostname, e.g.
play.example.com. The plan sets how many custom domains the organization can hold. - Add the two DNS records the domain card displays at your DNS provider:
- a TXT record that verifies ownership;
- a CNAME record pointing the hostname at
customers.forgeport.net. This routes the domain to Forgeport and allows Cloudflare to issue SSL. Keep proxying off at your DNS provider.
- The domain shows Provisioning until ownership is verified and the certificate is issued, then becomes active.
- Assign the domain to a portal with its portal selector.
For a root domain, use ALIAS, ANAME, or CNAME flattening. Otherwise, use a
subdomain such as www.
An active domain has a status switch that pauses Forgeport routing while DNS and the certificate stay configured, and a Remove domain action that disconnects it from Forgeport for good.