What changes in your first week.
Your first environment
You get it yourself, in minutes, and you do not have to learn a new toolchain to do it.
Mistakes found early
A wrong pattern or a missing control shows up in your editor, before anything is created.
The next project
It starts from something that already works, instead of a copy of another repository.
Security and compliance
It is already inside what you deploy, so it is not a separate step you have to plan for.
Three jobs, handled differently.
Ask for infrastructure in your own assistant
Describe what you need in the assistant you already use, whatever it is, and get back a working environment that already follows your security and compliance rules.
Provision only what you're allowed to
The assistant in the IDE picks the right Fractal for the job, filtered by your permissions, and refuses any configuration your standards do not allow.
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 reaches every project built on it.
From a sentence to a governed environment.
You ask, the assistant proposes, the platform checks, the environment exists. Every step is recorded.
Nothing new to learn on day one.
Your existing IaC
Whatever your organization already writes stays valid: HCL through the Terraform provider, or Java and TypeScript with an SDK.
Your editor
Types, autocompletion and policy feedback appear inline, before anything is created.
Your pipeline
Infrastructure is reviewed and merged in the same pipeline as the application code.
Your assistant
The platform speaks MCP, so assistants like Claude Code, Cursor or GitHub Copilot reach it through the same governed surface.
Everything through the interface you prefer
SDK, CLI, API, the platform UI or your assistant. Whatever you pick, the same rules apply underneath.