One build,seven surfaces.
P22X is the reference implementation. Every one of these seven domains is served by a single artifact, rebuilt from one config file, with a public front of house and a gated back of house. Nothing here is a live service — it is the platform running, on real domains, so it can be looked at rather than described. Studio X is the first customer and it is in house.
What works today
What this isA reference build of Rail-Works: FOH/BOH, one artifact, seven hostnames. Running, inspectableLive
What this is notNot a live service. Nothing to buy, no signup, no pricing. Demo estate under Studio X TechNot yet
First customerStudio X, in house. The platform is proved on the house estate before anyone else is asked to trust itLive
Rebuilds from configOne JSON per door, one stamper, one deploy map, one audit. The estate is reproducible, not hand madeLive
Available to slot inThe framework can carry a client's FOH/BOH build. Scope and terms go through Studio X TechSoon
The block itselfSeven TLDs registered pre-AI, held deliberately. All answer as of 260813Live
Seven surfaces, one artifact
Each domain is a different face of the same build — the shape a real platform needs. Not seven sites: one system, addressed seven ways.
p22x.com — the frontFront of house. What a customer meets first, public and honest about what worksFOH
p22x.io — the developer surfaceWhere a partner integrates. Same build, different first viewAPI
p22x.app — the tenant clientA partner joins by installing something, not by signing somethingClient
p22x.cloud — the infrastructure storyWhere tenant workloads run. The hosting half of a platformCompute
p22x.ai — the routing layerWhich shop, which press, which lane. Registered before the AI wave, held on purposeRouting
p22x.link — the routerProven, not theoretical: this domain already served live redirects for house propertiesProven
p22x.email — the messaging railHeld clean and uncommitted, ready for the transactional layerRail
What the framework actually does
This is the part worth buying, and it is all visible from here.
Front of house and back of houseA public face anyone can read, and a gated side behind one key. Every door in the estate has bothPattern
One build, many hostnamesSeven domains here, one artifact. The hostname decides the first view. A second build would be a second thing to keep in syncLive
Tenant skinsA door declares its trade dress and gets it. Black-and-white for one tenant, the house glass for another, from the same templateLive
Rebuilt from config, never by handOne small JSON per door. Change the rule once and it cascades across the estate. Nothing is hand-styled per projectLive
It audits itselfEvery build is swept for the class of defect, not the instance. A door that breaks the pattern fails before it shipsLive
Every deploy target is written downA domain with nowhere to go is named loudly on every run. Silent partial coverage is what makes an estate unmaintainableLive
Where it stands, plainly
The framework is running todayNot only here. The same build serves the house estate — print network, brand doors, personal doorsNow
Studio X is customer one, in houseThe house estate is the proving ground. It carries real traffic before anyone else is asked to trust itIn house
P22X itself is not tradingNo service, no signup, no pricing, nothing to buy on this domain. That is deliberateNot yet
The framework can carry a buildIf a client wants a front-of-house and back-of-house platform, this is the shape it would takeOpen
Held and reviewed by Studio X TechScope, terms and any decision to build on this framework go through the house.
StudioXtech.com
Back of house
Back of houseProject records and the review board.
Use your key