From prototype to deployable.
Bring a working prototype. Leave with a crosscut-complete, enterprise-grade application. Here’s the path your prototype takes through the factory.
Prepare your prototype
You don’t need to rewrite or re-platform anything first. A good prototype for the factory is:
- Working — it runs and demonstrates the core path end to end.
- Concrete — real screens, routes, and data shape, not slides.
- Scoped — one clear job done well, rather than a half-built platform.
- Portable — something you can share without exposing secrets or proprietary internals.
Bring it to the factory
During design-partner preview, onboarding happens through the community and a short intake conversation. We’ll look at the prototype, confirm scope, and run it through ESP.
Security — don’t post proprietary code, credentials, or confidential company information in the community. Sanitize the prototype before sharing, and we’ll establish a private channel for the actual run.
The factory generates & verifies
ESP parses the prototype into a structured spec, generates a Java / Spring implementation, and verifies it against all twelve crosscuts. Each verification failure feeds the next generation until the pass is clean.
What you get back:
- The implementation — generated Java / Spring, crosscuts applied.
- The crosscut report — a record of what was checked and how it passed.
- The spec — the structured spec the implementation was generated from.
Review & deploy
You review the generated application against the prototype’s intent, then deploy it to your target environment through the Liquid Compute Runtime — cloud, on-premises, edge, or hybrid.
Detailed deployment guides ship with design-partner access.
Keep going
- Read the ESP reference.
- Explore the factory loop in depth.
- Apply to become a design partner.