Infrastructure
InfroStack: guided server provisioning and stack building
Plan a new server or stack with a catalog, validation and recommendations — a guided wizard that helps size and shape infrastructure before you build it.
Does this actually provision live servers?
No. InfroStack is a planning and specification wizard. It helps you choose and validate a stack and generates starter config files; it does not stand up real infrastructure. A saved stack can optionally be linked to a deployment target for later use.
Already live in the product
Running in production today: the stack catalog, configuration validation, and sizing recommendations.
Built around real workflows
Highlights below describe capabilities already present in the protected app behind this page.
- Server and stack catalog
- Configuration validation
- Sizing recommendations
- Guided setup flow
What teams can do here
- Step 1Pick a stack
- Step 2Validate the configuration
- Step 3Review recommendations
- Step 4Proceed to build
How it works
- 01
Choose your stack
Pick frontend, backend language and framework, database, cache, search, reverse proxy, SSL and deployment strategy from a version catalog. Each version is tagged latest, LTS, active, stable, beta or end-of-life.
- 02
Validate the combination
The compatibility engine checks the selection, warns on end-of-life versions and returns errors and warnings before you commit to anything.
- 03
Review recommendations
Opinionated recommendations by use case help you size and shape the stack, with an AI assistant available for questions grounded in the same catalog.
- 04
Generate starter artifacts
The wizard produces a Dockerfile, a docker-compose.yml and a .env.example from your selection — opinionated starter files, not full production manifests — and saves the spec as draft, validated or created.
A worked example
Say a fifteen-developer product team is scoping its next internal service. In InfroStack they select a Node.js backend, PostgreSQL, Redis, an nginx reverse proxy and Let's Encrypt SSL. The validator flags the chosen runtime line as nearing end-of-life and points at the LTS tag; they switch before a single container exists. With the selection saved as validated, the wizard emits a Dockerfile, a docker-compose.yml wiring app, database, cache and proxy together, and a .env.example listing the connection strings to fill — a scaffold the team refines instead of a blank page, and a spec the next hire can read.
Frequently asked questions
See also: Server monitoring · Backups & disaster recovery · Blog: Server monitoring tools · Blog: What is RMM? · Pricing
Book demo
Design the stack before you build a single server
Pick versions from a status-tagged catalog, let the compatibility engine veto end-of-life choices, and walk away with a Dockerfile, compose file and .env scaffold your team can actually start from.
