Staging and Production

Build and test in staging, then promote to production in a controlled, versioned step with rollback. Production changes are locked to the promotion path.

Change without fear

Integration configuration is production infrastructure. A mapping, a workflow or a portal page serves real users and moves real data, and editing it live carries the same risk as editing any live system. STRAX is built around a discipline most organisations want and few achieve: nothing reaches production untested.

STRAX supports a paired staging and production setup. Integrations, portals, queries and reports are developed and tested in staging, where breaking something costs nothing. When a change is ready, it is promoted to production as a deliberate, reviewed step.

Promotion is reviewed, versioned and reversible

Before anything is applied, STRAX shows exactly what would change: what is new, what is modified and what differs, down to individual settings. The administrator approves a specific, visible difference rather than trusting that the environments match. A preview confirms the outcome before anything moves.

Every promotion is recorded with what was applied, when and by whom, and the state before the change is kept. If a promotion turns out to be wrong, it can be rolled back. Demo ISP can reshape its customer portal on staging for a fortnight, sign in as each user role to test it, and then put the whole change live in one recorded step, knowing the previous version is a rollback away.

Environment-specific values stay where they belong. A reference such as a billing API address resolves to the staging address in staging and the production address in production, so the same configuration behaves correctly in both places. Secrets never travel between environments at all; production credentials are entered in production and nowhere else.

Production is locked to the promotion path

The discipline holds because the platform enforces it. Production configuration is locked against direct editing, so the tested path is the only path, including under deadline pressure at five o'clock on a Friday. A controlled override exists for genuine emergencies, and its use is recorded.

Safe iteration inside one installation too

The same idea operates at a smaller scale within a single installation. A live portal, query or report can have an editable staging copy that is changed and tested while the original continues to serve. Pushing the copy live is versioned, and an incorrect push can be reversed. Day-to-day changes use staging copies; the paired-environment promotion moves the installation's whole configuration.

Why this matters

Auditors, customers and boards increasingly ask how changes reach production. With STRAX the answer is short: through a reviewed, versioned, reversible promotion, on a platform that enforces it. That is a maturity signal most integration estates cannot give.

Changes are verified after promotion with the same monitoring that watches production every day. To move configuration to an unrelated installation, such as a partner shipping a solution, see the marketplace and packages. Our commitments on change control sit alongside the rest of our trust programme.