Skip to main content

Fractal Cloud Architecture

As you can see from the simplified diagram below, Fractal Cloud maintains a repository of your Fractals. It allows your Centers of Excellence to define fractals, which then are made available to the organization teams, that can take them off-the-shelf and use them in all environments.

Architecture of Fractal Cloud

You can work on your fractals in one or combine multiple of the following options:

  • Use the Web application
  • Use our Java (and soon C#) SDK and commit on your git repos for Infrastructure as (actual) Code (IaC)
  • Use our APIs to integrate Fractal Cloud in other tools your enterprise already uses to enforce specific processes (such as ServiceNow, ZenDesk, etc.)

Fractal has security as a paramount requirement. Fractal Cloud does not store any credentials of its users' cloud environments, and no information on the subscription is accessible centrally. Instead, we have opted for a completely declarative approach, in which a set of Agents (we call the Cloud Agents) are deployed and running on the users' AWS accounts, Azure Subscriptions, GCP Projects, and OCI Tenancies. These agents regularly check the current state of the infrastructure in their environments and compare it to the state the environment should be in, which Fractal Cloud stores.

If the actual state differs from the declaration of the target state, the agents perform changes to the environment to reconcile the two.

You can read how to install the Cloud Agent in this how-to: 3.1 Fractal Cloud Agent Initialization

You can decide to use Fractal Cloud SaaS offering or have your private installation running on your cloud environment, whether that is private, hybrid, or public.