Start on AWS. Told straight, without a date we can't keep.
Vendor support is the easiest thing in this industry to overstate, so here is the version we would give you on a call. AWS is live and complete. Azure is built and not yet selectable. Google Cloud is not built. We are not going to offer you a date for the other two.
One is live. One is close. One is not.
The difference between “built” and “live” matters, so we keep them separate rather than blurring both into “supported”.
Amazon Web Services
Live and complete. Everything on this site — rules, approval, access handling, verification, ongoing checks, the record — works against AWS in production today. This is the vendor to evaluate us on.
Microsoft Azure
Built, not yet selectable. The work exists and is exercised by tests, but we have not yet created a resource in a real Azure subscription — and a vendor does not become available on the strength of tests. When it is proven, it becomes selectable. Not before.
Google Cloud
Not built. It is a name in our roadmap and nothing more. If Google Cloud is where your infrastructure lives, we are not the right platform for you today, and we would rather say so now.
Why we are this specific
Because you will find out anyway, and finding out during a pilot is worse for both of us. If a vendor's status changes, this page changes with it — it is the page we hold ourselves to.
What we hand you works with what you already run.
Intentric produces standard infrastructure code, which means the tooling your team already uses to store, review and run it keeps working exactly as it does now.
OpenTofu
Available. Standard, inspectable, and runnable by your team without us.
Terraform
Available. The same output, for teams standardized on Terraform.
Pulumi
In progress, not available. Under way, and not something you can select today.
This sits upstream of what you have.
If your team already runs orchestration, state management or a review pipeline for infrastructure, none of it is wasted. Intentric produces the thing those tools were built to run — it does not compete with them for the same job.
- Infrastructure that lives in your repositories keeps living there, in sync
- Your review and deployment pipelines continue to work on standard code
- Single sign-on and automated user provisioning for organizations that need them
- Machine access for your own automation, held to the same rules as a person
You do not start from an empty account.
Existing infrastructure stays exactly where it is. You choose what comes under management and in what order — usually starting with whatever is least frightening to hand over first.
- Nothing is adopted or altered because it happened to be in the account
- Bring services under management gradually, on your own schedule
- Environments stay separate, with their own parameters and their own stakes
- Stop at any point — what has been produced is standard code and stays yours
Evaluate us on the vendor that's live.
If you are running on AWS, everything described on this site is available to try against a real environment. If you are not, tell us — it is useful to know.