Preview Environments

FluxNow creates a fully isolated preview environment for every pull request you open against your default branch.

How previews work

When a PR is opened, FluxNow:

1. Builds a new container image from the PR branch
2. Provisions an isolated environment in its own namespace
3. Posts the preview URL to your dashboard and as a PR check

The preview URL is unique per PR and available as soon as the build completes.

Services in preview environments

Each preview environment gets isolated instances of your enabled services:

• Postgres — each preview gets its own database, with the schema branched from staging
• Redis — previews share the staging Redis instance (no per-preview branching)
• S3 — each preview gets its own bucket prefix, isolated from staging and other previews

Environment variables

Preview environments use the same environment variables as staging by default. You can override specific variables per environment from the project dashboard under Settings → Environment.

Lifecycle

• Preview environments are created when a PR is opened or when a new commit is pushed to an open PR.
• They are deleted automatically when the PR is merged or closed.
• Preview environments are not intended for production traffic — no custom domain support, and storage is ephemeral.

Preview URL format

Preview URLs follow the pattern: <pr-number>--<project-slug>.openfab.dev

The exact URL is always visible in the project dashboard on the PR’s environment card.