RosettaCloud™ Infrastructure as Code
CloudFormation and Terraform
One person writes it.
Everyone gets to use it.
A good template is expert work, and it usually stays where experts are: in a repository, applied by the handful of people who know how. Wrapping it as a Formation turns that same file into something a colleague can launch from a form, with the budget, the owner and the lifecycle already attached.
Four things your template
gains on the way in
The file is untouched and runs as it is. What it acquires is everything a template has never been able to carry on its own.
It becomes a form
Whoever wrote the template decides what is fixed and what is a choice. Everyone else fills in the choices and presses launch.
It gets an owner
Cost lands on the person and the project that launched it, from the moment it runs, with nothing to tag.
It can be published
Give it to a person, a group or an organisation, and it becomes something they can use on their own initiative.
It has a lifecycle
Tracked to completion, outputs captured, listed with everything else you have, and removed when the Formation is.
The thing worth having
A repository becomes
a catalogue
Most organisations already have the templates. What they do not have is a way for anyone outside the platform team to run one safely, so the templates stay a specialist tool and the requests keep arriving as tickets.
Published as Formations, they become a set of things people can launch for themselves: the approved database, the standard analysis environment, the project scaffold. The expertise is still yours. The waiting is gone.
Curated, not open season
Only the templates you publish are available, to the people and groups you publish them to.
The same one every time
Everyone launches from the version you published, so what people are running is knowable rather than inferred.
Alongside everything else
A stack sits in the same catalogue as machines, clusters and notebooks, so people find infrastructure the way they find anything else.
Two languages, one treatment
CloudFormation
Stacks, tracked as Formations
A stack is created from your template, followed through to completion, and its outputs are captured and usable by whatever comes next.
It is listed with every other resource, and deleting the Formation deletes the stack, so the catalogue and the estate stay in agreement.
Terraform
The same treatment, for the estates that use it
Terraform is the common language for infrastructure spanning more than one cloud, and it gets the same wrapping: your configuration, run as a Formation, with state stored durably and the same ownership, budgets and sharing attached.
Your modules and your workflow stay exactly as they are. What changes is who else can now use them.
The limit belongs to the account,
not to the route in
Budgets and quotas are enforced at the cloud’s own API, which is the one thing every route has in common. A stack launched from the catalogue, a pipeline, a laptop or the provider console all meet the same limit, because the limit lives where the resources are actually created.
Publish a template to a wider group and the limit still holds, without depending on everyone taking the approved path.
How enforcement works →Common questions
What does wrapping a template give me?
It turns a template into something other people can use. Parameters become a form, so a colleague who has never written infrastructure code launches the thing your template builds without holding cloud credentials or reading a line of it. The template itself is unchanged and runs as it is.
Who owns the cost of a stack?
The person who launched it, and the project they launched it under, recorded at the moment it runs. Everything the stack creates rolls up to them without anyone tagging a resource, so a per-team or per-project figure is a report rather than an investigation.
What happens to the stack afterwards?
It appears alongside every other resource you have, with its outputs captured and usable, and it is deleted with the Formation. There is no separate console to check and no drift between what the platform thinks exists and what does.
Does this replace our existing IaC workflow?
It does not have to. Keep authoring and reviewing stacks however you do now, and use this to publish the ones other people should be able to launch for themselves, and to attach budgets, ownership and sharing to what they create.