Skip to main content
About

Infrastructure should start with what you need — not with which vendor's syntax you happen to know.

Every organization running infrastructure ends up building the same middle layer: a way to check changes against its own rules, a way to approve them, and a way to prove afterwards that both happened. Most build it under time pressure, at companies that do not sell infrastructure tooling. We think that layer should be something you buy.

The problem we kept meeting

The bottleneck was never the writing.

Generative tooling made producing an infrastructure change faster and left everything after it as it was. The queue moved from authoring to reviewing, where it is more expensive and harder to see.

So teams either hand-roll the approval and evidence layer themselves — repeatedly, imperfectly — or skip it and rely on most changes being fine most of the time. Neither is a good position when someone asks who approved the change that took production down.

What it costs teams

  • Weeks of senior engineering time spent reviewing changes that are almost all routine
  • Approval that lives in a chat message and cannot be produced a year later
  • Infrastructure that quietly stops matching what anyone intended
  • A security questionnaire that is genuinely hard to answer honestly
  • Platform engineers rebuilding the same governance layer for the third time in their career
What we believe

Principles, not a feature list.

The decisions we made early and will not quietly reverse when they become inconvenient.

Software proposes. People dispose.

Automation is good at preparing a change and bad at deciding whether it should happen. A person authorizes every change by default, and nothing that changes, deletes or replaces what is already running ever skips one.

Rules come before action.

Your limits are applied to what a change would do — not to how convincingly it was requested. A rule that bends to better phrasing was never a rule.

Success is not correctness.

A change that reports success has told you the request was accepted. Whether your infrastructure now matches your intent is a separate question, and we ask it separately.

Nothing holds a permanent key.

Access to your cloud is granted for approved work and expires with it. If a credential ever leaked, the damage should end where the job ended.

The record is written as it happens.

Evidence assembled after someone starts asking questions is not evidence. What happened is recorded at the moment it happens, and it is exportable.

Your infrastructure is yours.

What we produce is standard and inspectable. If you leave, you keep the estate and lose only the workflow. A platform that traps you had to earn its keep some other way.

What it does

The whole path, from request to record.

What you get

  • The whole path — request, review, approval, application, verification and ongoing checks — on AWS, Azure and Google Cloud, with OpenTofu or Pulumi as the engine
  • The services teams actually stand up: databases, compute, storage, networking, delivery, messaging, and certificates on AWS and Google Cloud
  • Your rules, approval boundaries and roles, enforced, with five ready-made policy packs and policy code of your own
  • A console for the people asking and the people approving, a command-line tool for those who prefer it, and an MCP server so your own agent can propose a change but not approve one
  • A complete, exportable record of every request, decision and result
  • An inbox for what is waiting on you, with email, Slack and Microsoft Teams, and a spend view that keeps measured activity and the estimated run rate apart
  • A signup-free sandbox that runs the whole loop against a simulated AWS

What it does not do

  • Bill by usage: usage is measured and shown, but the subscription is set by the resources under management
  • Create certificates on Azure, or send transactional email on Google Cloud, which has no such service
  • Approve or apply anything on its own: the MCP server and the AI assistant can propose, and cannot do either
The company

Who is behind it

Kanata Florida, LLC, doing business as Intentric.

A successful change is not proof that the infrastructure is correct.

Intentric design principle

See what it does with a change of yours.

Start in the console, or book a demo and bring a change your team is putting off.