Our past selves needed this, so we built it for you
Infrastructure on autopilotFull control. No effort
Start from nothing, or bring in what you already run. Either way you get your infrastructure automatically managed. Nothing to babysit, no time wasted in the loop, and you can step in any time.
- Nothing to migrate
- No legacy dependencies
- Zero to running in minutes
- Any cloud
Featured in
"formae is a significant evolutionary leap forward in both DevOps and software development. It represents a shift in thinking as fundamental as source control, as practical as package management, and as vital as observability. formae's impact will extend beyond improving the lives of DevOps and engineering teams to creating lasting and reliable value for businesses and their customers."
Harry BrumleveFounder of strategic technology firm Thoughtful SoftwareUsed to manage real infrastructure
formae is for you, whoever runs your infrastructureClick your role and see which offering fits
Signer of the cheques
Best fitformae IaCYou sign for the estate, the audit and the migration, and you are asked for one number by people who will not read the detail.
- Risk on the record
- Fewer tools
- Cost you can defend
- Estates nobody can list
- Headcount to make up for tooling
- Migrations that stall
- An inventory of what is really running, across clouds, without a discovery project
- Most of what your teams do by hand is automated out of the box, with nothing to build
- Adopt it on the estate you already have, with no big-bang migration to approve
Maker of the map
Best fitformae IaCYou decide how infrastructure is described across a company that has already decided nine different ways.
- One way to describe it
- Standards people actually follow
- Choices that survive a reorg
- A dialect per team
- Wiki pages nobody reads
- Exceptions that become the rule
- One way to describe infrastructure instead of one per team and per vendor
- The standard is executable: a forma is the document and the deployment
- Roll it out against what already exists, team by team, without a mandate
Wearer of every hat
Best fitformae CloudYou write the product code and ship it. Then you get woken up when it breaks, and you pay the cloud bill. And neither of those is the job you took.
- Ship fast
- Everyone on the product
- Nothing to babysit
- Own infrastructure
- Hire DevOps to run it
- Anyone stuck on plumbing
- Your team stays on the product instead of looking after infrastructure
- A new service is live the day you write it, not the week after
- It stays in order as you grow, with nobody babysitting it
Winner of the bake-off
Best fitformae CloudYou have to show the thing running on somebody else's infrastructure, this week, before anyone has agreed to buy it.
- A PoC in no time
- On any infrastructure
- Something that survives questions
- Owning where you demo
- Access requests
- Setups that take a week
- Point it at an account and it tells you what is already there
- Stand up a proof of concept from nothing, then tear it down on a timer
- Nothing to install in the customer's estate to show them their own estate
Shipper of the feature
Best fitformae CloudYou wrote the service. Getting it somewhere it can serve traffic should not be a second profession.
- Ship it yourself
- Live the same day
- Nothing new to learn
- Waiting on a ticket
- Learning the platform
- Dealing with infrastructure
- Your agent sets up what the service needs while you are still writing it
- Staging and production come out the same, every time
- No infrastructure team in the loop to deploy your own service
Builder of the golden path
Best fitformae IaCYou build the thing other teams build on, and you are judged on whether they use it or go around it.
- Abstractions nobody looks behind
- Room to change what is underneath
- Adoption without a mandate
- Ticket queues
- Copy-pasted modules
- Shadow infrastructure
- Teams ask for what they need and never see what it is made of
- You change what is underneath without anyone rewriting anything
- Policies travel with the stack, so a guardrail is not a review meeting
Owner of the worst case
Best fitformae IaCYou are accountable for what is actually running, who can reach it, and what happens when the answer turns out to be wrong.
- Provable state
- Least privilege
- An audit that ends
- Resources nobody declared
- Exceptions that became permanent
- Evidence gathered by hand
- Everything is found and described without anybody being asked to declare it
- Order is applied continuously, not when somebody remembers to run something
- The same rules run whoever is on shift, and every change is a versioned diff
Holder of the pager
Best fitformae IaCYou spend the error budget, and you are the one awake when a change lands badly at 2am.
- The smallest possible blast radius
- Patch now, not after the pipeline
- Knowing what changed
- Waiting on a deploy to fix prod
- Fixes nobody wrote down
- "Who touched prod?"
- Minimal blast radius by design: change one thing without touching its neighbours
- Patch mode for the incident, reconcile afterwards, and the drift is recorded
- What you are reading is what is running, not what somebody committed
Keeper of the pipeline
Best fitformae IaCYou own the road from a merged branch to something running in production, and everything that goes wrong on the way.
- Repeatable applies
- Small, safe changes
- No surprises on Friday
- Drift
- Snowflake servers
- Being the only one who knows
- State comes from what is really running, not from a file that claims to know
- Apply at any granularity, from one resource to the whole stack
- Out-of-band changes are captured and versioned instead of overwritten
