Skip to main content

Domain Configuration

Learn how to configure custom domains for your Skysize projects and understand the default domain structure.

Default Domain Structure​

Skysize automatically assigns domains to your deployments based on the branch type.

Production Domains​

Production branches receive a clean, simple domain:

project-name.skysize.io

Example: If your project is named "my-shop", your production URL will be:

my-shop.skysize.io

Staging Domains​

Staging branches get an auto-generated hostname based on the deployment's database name:

<db-name>.staging.skysize.io

Because the database name changes each time you rebuild a staging deployment, the staging hostname can change on rebuild.

Development Domains​

Development branches get an auto-generated hostname based on the deployment's database name:

<db-name>.dev.skysize.io

As with staging, this hostname is regenerated when the development deployment is rebuilt.

note

Default *.skysize.io hostnames are assigned and managed by Skysize automatically. For a stable, branded address, add a custom domain (see below), this is especially recommended for production.

Custom Domains​

Skysize supports custom domains, allowing you to use your own domain name instead of the default Skysize domains.

Benefits​

  • Professional branding: Use your company's domain
  • SEO advantages: Maintain your domain authority
  • User trust: Customers recognize your brand
  • Flexibility: Point multiple domains to the same deployment

Custom domains and the Cloudflare proxy​

A custom domain is served directly by your deployment, not through Skysize's Cloudflare proxy: Cloudflare cannot serve a domain that belongs to someone else. Visitors would get certificate errors, or Cloudflare error 1014 (CNAME Cross-User Banned) when your own DNS is on Cloudflare too. Turn the branch's Cloudflare proxy off before adding a custom domain (see Cloudflare Proxy below); the dashboard refuses the domain otherwise. Skysize still provisions and renews the HTTPS certificate for your domain automatically.

Setting Up Custom Domains​

  1. Open your project and turn off the Cloudflare proxy of the branch.
  2. Go to the branch's Domains section and add your custom domain (for example, shop.example.com). Leave SSL enabled so Skysize provisions and renews an HTTPS certificate for it automatically.
  3. At your DNS provider, add a CNAME record pointing your domain to your Skysize deployment.
  4. If your domain's DNS is on Cloudflare, create that record as DNS only (grey cloud). A proxied record pointing to Skysize is refused by Cloudflare.
  5. Wait for DNS to propagate. This is usually quick (minutes), but can take longer depending on your DNS provider's TTL.

When you add, change, or remove a domain on a running deployment, Skysize automatically reconfigures the deployment's web routing and TLS, you don't need to redeploy.

note

Each domain has its own SSL toggle. Keep it enabled for production traffic so the domain is served over HTTPS with a valid, auto-renewing certificate.

caution

You cannot claim a domain under skysize.io as a custom domain, those hostnames are managed by the platform and assigned automatically.

Cloudflare Proxy​

Skysize can route a deployment's traffic through Cloudflare. The proxy is enabled by default.

Enabled (Default)​

When the Cloudflare proxy is enabled (recommended):

  • Traffic is routed through Cloudflare's global network
  • DDoS protection is active
  • A global CDN improves performance for distant users
  • HTTPS certificates are managed automatically

Disabled​

You can turn the Cloudflare proxy off if you need a direct connection to your deployment:

  • Traffic reaches your deployment directly instead of through Cloudflare
  • Useful for specific technical requirements

Toggling the proxy reconfigures the deployment's DNS record immediately, no redeploy needed.

caution

Disabling the Cloudflare proxy removes DDoS protection and CDN acceleration. Only disable it if you have a specific technical reason.

note

On the free tier, deployments are always served through the Cloudflare proxy regardless of this setting. The ability to turn the proxy off is available on paid plans.

Best Practices​

  • Keep Cloudflare proxy enabled: Unless you have specific reasons, keep it enabled for security
  • Use HTTPS: Always use HTTPS for production domains
  • Test on default domains first: Verify deployments work on default Skysize domains before adding custom domains
  • Plan DNS changes: DNS propagation can take time, plan domain changes accordingly