EXPERIENCE · STOREFRONT
InfrastructureProductWorks Storefront is a customer-hosted ordering experience for governed infrastructure products. Developers choose a product and provide bounded business intent instead of learning the provider topology, Terraform modules, Crossplane internals, IAM documents and implementation mechanics behind it.
INTERACTIVE DEMO · SYNTHETIC ONLY · NO PRODUCTION ORDERSTHE PROBLEM
A portal that exposes dozens of cloud primitives can still push architecture decisions onto every application team. Storefront takes the opposite position: define a small number of durable infrastructure products, give each one a stable contract, and let the platform own how approved ingredients become the requested outcome.
WHAT YOU ACTUALLY GET
Storefront gives developers a product-ordering experience instead of a form full of provider internals. The output is a bounded, reviewable product order that downstream systems can verify.
Teams can use the current Cloud Foundation Environment demo and see planned outcomes such as Managed Interconnect, Data Platform Environment and Kubernetes Platform without starting from raw AWS, Azure or GCP resources.
The order form captures business and product intent using closed, supported values so developers do not have to design networking, IAM, modules or provider topology themselves.
Required fields and contract rules are checked before handoff, catching unsupported values or incomplete requests before they enter the governed review path.
The selected product, inputs and handoff evidence can be cryptographically bound so downstream consumers can detect if the reviewed order was changed.
Organizations can use the canonical Storefront experience or a Backstage adapter while keeping the same underlying InfrastructureProductOrder contract.
Users can see that a valid request has moved into the next governed step without Storefront pretending that validation means approval or provisioning.
Storefront is the front door. It packages intent cleanly; it does not approve the order, create cloud credentials or provision infrastructure on its own.
CLOUD INFRASTRUCTURE DRIVE-THRU
The experience stays simple because implementation complexity remains behind the product boundary. Developers choose the outcome; the platform owns the governed process behind it.
Choose an approved infrastructure outcome from the curated catalog.
Provide bounded product and business intent through the stable contract.
Check closed values, required fields and deterministic contract rules.
Enter the authorized downstream review path without direct provisioning.
The public demo emits synthetic bounded intent only. A future customer workspace may require authentication and commercial entitlement before accepting real customer workflows; entitlement will not grant infrastructure approval or provisioning authority.
DESIGN DECISION
The standalone Storefront is the canonical product experience. Organizations already invested in Backstage can use an independently versioned adapter. Both surfaces preserve the same InfrastructureProductOrder contract so the experience can change without redefining the product boundary.
THE PRODUCT MODEL
The platform packages raw infrastructure complexity behind governed product contracts.
Demo product for governed foundation intent across approved provider and region choices.
DemoProduct direction for governed connectivity between immutable network-segment proposals.
Coming SoonProduct direction for governed data-platform outcomes.
Coming SoonProduct direction for standardized Kubernetes platform outcomes.
Coming SoonCOMMERCIAL BOUNDARY
Synthetic product selection and ordering experience for evaluation. No real customer execution or production authority.
Future real workflows can require organization identity, entitlement, retained evidence and governed integrations.
Enterprise licensing can support SSO, restricted-network deployment, support and negotiated operating boundaries.
A subscription or license permits use of the product. It never bypasses Guard, human authorization, Assurance or downstream reconciliation controls.
ENGINEERING PROOF
Consumer intent is constrained to the supported product vocabulary instead of accepting arbitrary provider configuration.
The order can be bound to an inert handoff and verification record so downstream consumers can detect mutation.
The Backstage surface is an adapter to the same contract, not a requirement that every customer adopt the same portal technology.
A valid order enters governed review. The Storefront does not acquire approval, cloud or reconciliation authority merely because validation passed.
The goal is not to hide infrastructure engineering. It is to put that engineering in the platform where it can be standardized, tested and improved without making every developer rebuild the recipe.
CURRENT MATURITY
The public Storefront remains synthetic-only. Durable customer data, production identity, billing/entitlement, authenticated external transport and downstream production action remain separately governed implementation gates.