Working with environments

Frontegg supports the creation of up to four distinct environments — Development, Staging, QA, and Production—to seamlessly align with your CI/CD workflows.

These environments are designed to provide structured support for your application lifecycle, enabling you to test, validate, and deploy changes with confidence. Environments must be created in the specified order, ensuring a logical progression that reflects your development pipeline. Each new environment can only be established after completing the integration process on the previous one, maintaining a clear and organized development flow.

Keys & domains

Each environment comes with its own credentials—Client ID, API Key, and a unique Frontegg domain. When working with multiple applications, it's recommended to use a dedicated App ID and API Key for each integration.

Allowed origins

Allowed origins use the {{APP_URL}} and {{LOGIN_URL}} variables, which are automatically set per application. To ensure full coverage, consider adding explicit origin values as needed. You can also use wildcards to support subdomain-level flexibility, for example, https://*.acme.com.

Publishing changes between environments

Environments are fully isolated, ensuring data and configurations remain separate by design. To maintain a consistent user experience, you can share your login box and self-service portal across environments using the Publish option. Keep in mind that other settings and configurations are not propagated and can be copied manually via APIs if needed.

Once you've published to the first environment—Development—navigate to the main page while in the Development environment. Click the Environments button, and you’ll see the Publish option enabled. From there, you can sync subsequent environments by publishing the changes directly from the Builder.