A way to manage cloud infrastructure from the needs of applications instead of starting from provider-specific resources. Teams describe what the application needs, while Fractal Cloud turns that intent into governed infrastructure.

Reusable infrastructure patterns created by platform teams. Blueprints give delivery teams a trusted starting point for secure, compliant and production-ready systems.

Lightweight agents that run inside customer environments and carry out provisioning locally. They let Fractal Cloud manage infrastructure without storing cloud credentials in the Control Plane.

A delivery model where security, operational standards and governance rules are encoded into reusable platform patterns before teams deploy. Compliance becomes part of the design rather than a late-stage review.

An outcome where teams use approved infrastructure patterns from the start. This reduces repeated reviews, shortens delivery cycles and helps teams make the right architectural choices by default.

The Fractal Cloud coordination layer. It stores infrastructure intent, reusable patterns and platform metadata while Cloud Agents perform the actual work inside each environment.

The ability for application teams to deploy approved infrastructure without waiting for manual tickets or direct cloud access. Fractal Cloud makes self-service practical by keeping governance embedded in every pattern.

A reusable architecture pattern that can be deployed as a running system. A Fractal packages the infrastructure blueprint and the approved ways teams can extend it.

Approved paths that help teams ship faster with fewer decisions to revisit. In Fractal Cloud, Golden Paths are expressed as reusable Fractals, Blueprints and Interfaces.

A delivery model where teams move quickly while staying inside policies defined by the organization. Fractal Cloud gives platform teams control without turning every deployment into a manual approval process.

Repeatable combinations of compute, storage, network, observability and security capabilities. Fractal Cloud turns these patterns into reusable assets that can be shared across teams.

The running systems created from Fractal Cloud patterns. A Live System is the real cloud deployment that application teams use, operate and evolve.

A consistent way to deploy across providers such as Azure, AWS, Google Cloud, OCI, Hetzner and on-premises platforms. Fractal Cloud lets teams reuse the same intent while each environment receives the right provider-specific implementation.

The practice of giving teams paved, reusable paths for software delivery. Fractal Cloud supports platform engineering by turning cloud standards into self-service infrastructure products.

Pre-approved components that teams can assemble into production systems. They reduce duplicated work and help organizations share proven designs across projects.

Infrastructure that teams can request, deploy and update through approved interfaces. Fractal Cloud enables self-service while keeping access, standards and lifecycle control in the platform.

Common operational practices embedded into infrastructure patterns. Examples include tagging, monitoring, backup policies, secure defaults and controlled emergency override.