What changed in the new shared platform rollout
The platform now runs on one shared Wasp deployment while keeping the public brand surfaces separated by host.
That sounds like an infrastructure detail, but it matters for day-to-day usage:
One stack, three branded entry points
capital-call.comapp.comanufacturers.comsaucory.com
Each host lands on the same underlying platform, but the copy, navigation, and app routing still resolve to the right product context.
Why this shape is simpler
The previous deployment model encoded environment names and brand assumptions in too many places. The new shape reduces that surface area:
- one client app
- one server app
- one database
- one deploy path
That makes release work easier to reason about and lowers the risk of drifting configuration between stacks.
What this unlocks next
With the shared stack in place, the remaining work is no longer about infrastructure sprawl. It is about finishing the user-facing separation:
- branded transactional email behavior
- branded
/blog/*delivery on each host - later cleanup of the retired legacy apps and stale DNS records
The important change is not just that the deployment is smaller. It is that the repo contract and the live contract now match.