You set the level.
Every agent can operate at one of three levels: it only suggests, it acts once approved, or it is fully automated. You choose per task, and you can change it at any time. Every action is traceable and reversible.
Nothing outside your rules.
Systems are built from a reusable architecture that already carries its policies, its security controls and the approved ways to extend it. What can be built is known in advance, not reviewed afterwards.
One definition, any cloud.
The same infrastructure can be deployed on a hyperscaler, a sovereign provider or your own data center, without being rewritten. Same architecture, same governance, different target.
Components, Fractals, Live Systems.
Components are assembled into a Fractal, a reusable architecture pattern that can be deployed as a running system. Deploy it and you get a Live System. Fractals stay provider-agnostic: the translation to a specific cloud happens at deploy. All of it follows the principles of Fractal Architecture →
Repeatable combinations of compute, storage, network, observability and security, shared across teams.
The blueprint and the approved ways to extend it, in one versioned, portable unit.
from v1.4
The running deployment, continuously reconciled with the Fractal it came from.
Three audiences, one platform underneath.
Development teams
Environments on demand through the platform UI, SDK, CLI, API or chat. The internal developer platform your teams get without building one first.
For developers →Platform & operations
Rules set once and enforced everywhere, full lifecycle, and agents that operate inside them.
For platform & operations →Business leaders
Faster delivery without losing control: every action is bounded, attributable and reversible, and no system is locked to one provider.
For business leaders →Six everyday jobs, handled differently.
Developers, platform teams, operations teams and agents all working together, each within what they are allowed to do.
Ask for infrastructure in your own assistant
Your team describes what it needs in the assistant it already uses, whatever it is, and gets back a working environment that already follows your security and compliance rules.
Start a new project without a fork
Deploy a versioned blueprint instead of copying it into a fork. One source to update and not n variants, so a fix or a new policy reaches every project built on it.
Provision only what you're allowed to
The assistant in the IDE picks the right Fractal for the job, filtered by that developer's permissions, and refuses any configuration your standards do not allow.
Reconcile drift without human intervention
A change made by hand in the cloud provider's console diverges from what you declared. The agent in that environment restores it within minutes and logs the event as audit evidence.
Reject non-compliant changes at deploy
Encryption, RBAC, network policy, logging and tagging live inside the Fractal your teams build from. A change that breaks them is refused at deploy, not flagged later in a review.
Keep the Terraform you already have
No rewrite, no migration project. Existing Terraform is imported as it is and gains what it never had: versioning, continuous reconciliation and updates rolled out under control.
Specialised agents, one per discipline.
Every agent uses your catalog and the same platform tools any assistant can reach, so it can only do things the platform already accepts. They act within the limits you set, ask for approval beyond them, and leave every action auditable.
Provisioner
Reads the repository, recognizes the kind of project and proposes the right Fractal. Serves environment requests in chat, and flags the cost before the deploy, not on the invoice.
Architect
Turns a plain-language requirement into a Fractal, reviews it as you save rather than at the pull request, and simulates the effect of a shared change on every Live System that depends on it.
Sentinel
Finds the likely cause of a failed deploy, learns what normal looks like for each system and says so in words when it drifts from it. The gap between “it’s broken” and “I know why” disappears.
Guardian
Turns the technical controls behind regulations and standards such as NIS2, DORA, SOC2 and HIPAA into deploy-time rules, then keeps probing them in an isolated copy so the gaps surface before an attacker finds them.
Advisor
Compares providers for a specific workload, finds oversized resources and orphaned environments, and proposes the fix on the originating Fractal so the saving holds instead of coming back next quarter.
Auditor
Assembles the evidence pack for a framework on request: inventory, logs, software bill of materials, proof of where the data sits. Weeks of manual collection become one query.
It fits the stack you already run.
Nothing has to be replaced to start. The same intent is reused everywhere, and each environment receives the right provider-specific implementation.
Real impact, measurable gains.
Fractal Cloud helps teams move faster with less overhead, cutting infrastructure costs, reducing complexity, and minimizing reliance on specialized staff.
Cut cloud infrastructure costs by 30% through optimized resource management.
No need for deep cloud expertise, multi-cloud enabled from day one.
Write and maintain 10x less Infrastructure as Code, simplifying management.
The future of infrastructure is autonomous.
We make it one you can trust.
Cut the wait, reduce the cost and keep control, on any cloud, on-prem or a sovereign region. Sign up or book a demo to see it running.