Skip to content
User guide

Addresses and domains

Where your project answers, how to protect it with sign-in or an address list, and how to put it on your own domain.

Your project's address

Every project answers at https://remcloudhub.com/project-name from its first deploy. The name you give in the New project wizard is the address; it shows on the project's header with Visit and Copy address. HTTPS is always on.

If your app expects to live at / rather than under /project-name, turn on Strip the path prefix under Project > Settings > Domains and health. Next.js apps are served under their base path instead.

Who may reach it

Under Settings > Domains and health:

  • Sign-in required: people sign in with REM CloudHub before they reach the app.

  • Allowed addresses: one IP address or range per line; empty means anyone.

  • Requests per second and Burst: callers above the limit get 429.

Your own domain

An organisation can serve projects on its own host names (for example app.example.com). Custom domains are managed by the platform team for each organisation:

  1. Write to support@remplatforms.com with the host name and the project.

  2. Create the DNS record you are given (an A record or a CNAME to REM CloudHub).

  3. Once the record resolves, the domain is verified and a TLS certificate is issued and renewed automatically.

Your organisation's policy decides which domains its teams and projects may use; a team can have its own default domain.

Uptime and a status page

Uptime checks watch your sites every 30 seconds: a failure below the threshold marks it degraded, a certificate that expires within 21 days too, and repeated failures open an incident that the next success closes. A public status page at remcloudhub.com/status/name can show your checks to your customers. Alerts from checks go to Activity > Alerts.

Download: PDF · Word · Markdown