01Modernize Your Existing IaC, Without a Rewrite
PLATFORM ENGINEERS · DEVOPS
Years of existing Terraform keep running as-is; governance, drift control and lifecycle are added on top, with no rewrite.
WHY IT MATTERS
The IaC investment is preserved while gaining a versioned catalogue, continuous reconciliation and controlled rollout across environments. Adoption can be phased one team or customer at a time as the catalogue grows.
CONCRETE EXAMPLES
RETA IL / E-COMMERCE
A retailer keeps its 40 Terraform modules in production and bridges them into native Fractal components as they are. They add drift detection and a versioned catalogue without rewriting a line or losing control of the underlying state. INSURANCE · MULTI-CLOUD
An insurer brings its existing Terraform, spanning Azure and AWS, under Fractal without rewriting it, and now operates both estates from a single platform with one governance model, drift detection and lifecycle across clouds.
02The Fractal Catalog as a Golden Path
PLATFORM ENGINEERS · ENGINEERING MANAGERS
Approved standards are published once; teams provision from the catalogue instead of opening infrastructure tickets.
WHY IT MATTERS
By treating infrastructure as a product, a small platform team scales across many teams and accounts without becoming a ticket factory. Standards stop drifting: the 20th environment is built like the 1st, freeing engineers to iterate on Blueprints rather than manually provisioning resources. CONCRETE EXAMPLES
TELCO
A 4-person Cloud Ops team running AWS + Azure for 18 app teams or customers publishes 5 approved Blueprints (landing zone, AKS/EKS cluster, encrypted bucket, HA Postgres, standard 3-tier). Infra tickets drop from ~25/week to near zero.
SYSTEM I NTEGRATOR
A system integrator builds its golden-path catalogue once, a governed landing zone, an AKS/EKS cluster, a ready-to-use Databricks workspace, and reuses it across every customer engagement instead of forking IaC for each new client.
03Ephemeral Environments for Developers
DEVELOPERS · DEVOPS
Every pull request gets its own full environment, created automatically and destroyed on merge.
WHY IT MATTERS
Contention over a shared staging environment disappears. Instead of relying on fragile CI scripts and fighting with IaC state locks, the platform natively handles the complete lifecycle. Every ephemeral environment is spun up in pure isolation, guarantees clean teardown, and automatically inherits central guardrails without custom scripting.
CONCRETE EXAMPLES
SAAS
A product team running ~30 PRs/week wires Fractal into CI: each PR spins up an isolated full-stack environment and tears it down on merge, ending the fights over shared staging. FINTECH
A payments team gets per-branch sandboxes with seeded test data provisioned from a Blueprint, so QA validates each feature in isolation before merge.
04Your Infrastructure Is Always as You Defined It
PLATFORM ENGI NEERS · CISO
A manual change made in the cloud console is detected and reconciled automatically, with an audit record.
WHY IT MATTERS
Continuous reconciliation turns drift response into a deliverable SLA, and keeps regulated environments aligned after go-live without manual sweeps of the cloud console.
CONCRETE EXAMPLES
BANKING
An operator manually opens a security group on AWS during an incident; the Automation Engine detects the drift within minutes, restores the declared state, and logs the event for audit.
HEALTHCARE
A storage ACL changed by hand on Azure is flagged and reverted automatically, keeping a regulated environment continuously compliant.
05Workload Migration Across Clouds, On-Prem & Sovereign
CTO · CLOUD ARCHITECT · PLATFORM ENGINEER
The same Fractal deploys on VMware, AWS, Azure, GCP, OCI or a sovereign cloud; migration becomes redeploying, not rewriting. WHY IT MATTERS
Migration turns into a repeatable service line instead of a custom project each time. The same expertise is reused across targets, with no parallel IaC stacks to maintain per cloud.
CONCRETE EXAMPLES
UTILITY
A utility moves a workload from an internal VMware data center to GCP by re-deploying the same Blueprint to a new target, with no rewrite of the infrastructure definition.
PUB LIC SECTOR
An agency redeploys a cloud workload onto a sovereign-cloud region to meet data-residency rules, reusing the identical Fractal.
06Deploy the Application Workload onto a Live System
DEVELOPERS · DEVOPS
Application teams deploy their workload onto a Live System that already exists, using the SDK, without ever receiving cloud credentials.
WHY IT MATTERS
Operations keep ownership of the cloud accounts, credentials and platform, whileapplication teams get a clean, repeatable way to ship onto it. The two responsibilities stay cleanly separated, with no shared keys, yet developers maintain full application telemetry and observability.
CONCRETE EXAMPLES
SAAS
A product team ships its application container onto a managed Kubernetes Live System through the SDK; the platform team never hands out cloud credentials.
MEDIA / STREAMING
A streaming team rolls out a new microservice onto a shared, governed Live System without touching the cloud console or knowing how the cluster underneath is wired.
07Propagate an Update Across the Whole Portfolio
PLATFORM ENGINEERS · CISO · CTO
One version bump rolls a change across every dependent environment in controlled waves.
WHY IT MATTERS
Recurring work (CVE patches, version bumps, policy updates) goes from N separate apply runs to a single governed, auditable rollout, turning complex updates into a predictable SLA per environment instead of an open-ended effort.
CONCRETE EXAMPLES
BANKING
A critical CVE lands; the platform team bumps one shared component version and the Automation Engine rolls the patch across ~60 dependent Live Systems in controlled, auditable waves. TELCO
A mandatory logging-agent version is published once and propagated to every environment built from that Blueprint, with rollout status tracked centrally.
08New SaaS Customer Live Before the Kickoff Call
CTO · HEAD OF ENGINEERING · SALES ENGINEERING
New-tenant provisioning starts from a webhook and completes with no human in the loop.
WHY IT MATTERS
Onboarding leaves the critical path to time-to-revenue, and the standard delivery team handles it without bespoke setup for each new customer.
CONCRETE EXAMPLES
B2B SAAS
A closed-won deal in the CRM fires a webhook; a Fractal provisions the new tenant’s isolated environment and the customer is live in ~10 minutes. FINTECH SAAS
Tenant onboarding (dedicated DB + queue + namespace) is triggered from the signup flow, removing manual provisioning from the time-to-revenue path.
09Self-Service Infrastructure Without Cloud Access
DEVELOPERS · ENGINEERING MANAGERS
Production-grade environments are provisioned from a form or portal, without anyone seeing a cloud console.
WHY IT MATTERS
Networking, IAM and policy stay baked into the Blueprint, so self-service never means a loss of control: teams move fast within guardrails defined centrally, while retaining full observability over their isolated environments.
CONCRETE EXAMPLES
ENTERPRISE IT
A developer gets a full production-grade environment by filling three fields in a form, never touching a VPC.
RETAIL
App teams request standardized environments from an internal portal; networking, IAM and policy are baked into the Blueprint, invisible to the requester.
10Compliance Built In, Not Audited After the Fact
CTO · CISO · HEAD OF SECURITY
Environments are generated already compliant; non-conformant changes are blocked before they exist.
WHY IT MATTERS
Controls (encryption, RBAC, network policy, audit logging, tagging) live inside the Fractal, so regulated customers can be served by the standard team and audit evidence is queryable from the platform, not reconstructed after the fact. CONCRETE EXAMPLES
FINTECH · PCI - DSS / DORA
A fintech generates compliant environments without checklists: the controls live in the Fractal, not in a manual process, and non-compliant changes are rejected at deploy.
HEALTHCARE
Data-protection guardrails (encryption, network isolation, logging) are encoded in the Blueprint, so every new environment is conformant by construction.
11Fractal Cloud Inside Your Enterprise Tools
CTO · ENTERPRISE ARCHITECT
Infrastructure is provisioned straight from the tools your organization already runs on, an ITSM catalogue, a ticket, a CI pipeline, by calling the Fractal REST API. No one opens a separate console. WHY IT MATTERS
Provisioning plugs into existing request and approval workflows, so Fractal fits how the organization already works instead of becoming yet another tool to adopt and govern. Importantly, the resulting infrastructure relies on standard cloud resources, ensuring no proprietary lock-in.
CONCRETE EXAMPLES
ENTERPRISE IT · SERVICENOW
An employee requests an environment through the standard ServiceNow catalogue. Once it is approved, ServiceNow calls the Fractal API and the environment is provisioned automatically, leaving the existing approval chain untouched.
TELCO · CI PIPELINE
A merge in GitLab triggers the Fractal API to stand up the matching environment, so infrastructure is requested and tracked from the pipeline the team already lives in.
12Disaster Recovery On- Demand, Not On-Paper
PLATFORM ENGINEERS · CTO · HEAD OF INFRASTRUCTURE
Your disaster-recovery setup is defined as a Fractal, so the whole production environment can be rebuilt in another region in minutes, identical to production and on demand. WHY IT MATTERS
Because the DR environment is the same Fractal as production, recovery can be run as a routine drill and recovery time is proven, not estimated. There are no separate, stale DR scripts drifting away from prod.
CONCRETE EXAMPLES
BANKING
The team tests DR by deploying the full environment to eu-west in ~5 minutes from the production Blueprint, with no custom scripts, as a repeatable drill.
INSURANCE
A regional outage is simulated and the identical stack is brought up in a second region from the same Fractal, proving RTO instead of documenting it.