Every application deployed on Scalingo is automatically given a default public domain name, allowing immediate public access to the app. By default, this domain name also comes with a TLS certificate.

This default domain name is made of three parts, separated by a dot (.):

1. The name of the application.
2. The name of the region where the application is hosted: either osc-fr1 or osc-secnum-fr1.
3. A fixed suffix, common to all applications hosted on Scalingo: scalingo.io.

An app called my-app, hosted on osc-fr1 would be reachable using
my-app.osc-fr1.scalingo.io.

The same app hosted on osc-secnum-fr1 would be reachable using
my-app.osc-secnum-fr1.scalingo.io.

Default Public Domain Name for Review Apps

Review apps are also automatically given a default public domain name to ease their public access. This default domain name is made of the three same parts, except that the application name part is suffixed with -pr<Pull Request number>.

For instance, a review app deployed based on the pull request #123, openend for an app called my-app hosted on osc-fr1 would be reachable using
my-app-pr123.osc-fr1.scalingo.io.

Technical Considerations

• Even if it’s always available, the default Scalingo domain name only allows to route traffic to the web process type.
• Containers don’t have their own public domain name, so it’s not possible to target a specific container from the outside world.