Pre-production zone · West Europe
IP4X-Staging
staging.ip4x.systems
A production rehearsal for IP4X: core and two region APIs on one server, installed the same way as production, so every release is proven here first.
What runs here
- core-api and the core admin portal, under pm2
- tenant-api twice, as the regions za-stg and eu-stg
- Postgres 17 with PostGIS, pgvector and pg_trgm, and Redis 7
- flagd for feature flags, and Mailpit so no real email leaves
Still to deploy
5 of 18 done
- Done: Server built in West Europe; it shuts down at 20:00 SAST1 Oct 2026
- Done: IP4X server baseline: /data and /opt/ip4x layout, ip4xadmin, Node 24, pm2, Caddy with security headers, health probe1 Oct 2026
- Done: Ports 80 and 443 open to the internet
- Done: DNS: staging.ip4x.systems points at this server
- Done: HTTPS certificate for staging.ip4x.systems
- To do: Key Vault for staging secrets, read with this server’s identity
- To do: Monitoring agent sending sign-in and sudo logs to the capped log workspace
- To do: Weekday 07:00 start from GitHub, and CI wake-ups for off-hours promotions
- To do: Postgres 17, Redis 7 and a private blob container on the data disk
- To do: Release store: one build per commit, installed here by digest
- To do: core-api and the core portal installed from the release store
- To do: Region APIs za-stg and eu-stg installed and registered in core
- To do: Safety rails: Mailpit, sandbox payment and SMS gateways, production endpoints blocked
- To do: flagd reading flags/staging.json
- To do: Synthetic seed data, and a weekly rebuild from zero
- To do: Tenant hostnames for staging on GoDaddy, with Caddy sites
- To do: Promotion pull request from staging to production, same artifact
- To do: Two weeks alongside the old staging server, then retire it