Built-In Architectures

Hundreds of tested, editable, deployable Azure architectures. Each architecture comes with documentation covering its purpose, data flow, chosen infrastructure, and further considerations.

Overview

Browse the catalog from the Built-In Architectures section. Every architecture comes with detailed documentation covering:

PurposeWhat the architecture is designed to do, and the scenarios where it fits.
Data flowHow data moves through the resources.
Chosen infrastructureWhich resources were selected, with the reasoning behind each choice.
Further considerationsLimitations, scaling concerns, and decisions you may want to revisit for your environment.

Built-In Architectures section with an architecture selected and its documentation visible

Adding an Architecture to Your Project

Infrastructure section populated with resources from an imported built-in architecture

When you find an architecture that fits to your needs, click Add to Infrastructure. Clophi imports the entire architecture into the Infrastructure section.

From the Infrastructure section, you have full editorial control:

Click any resource to open its form and modify configuration values.
Add new resources alongside the imported ones.
Remove any resources you don't need.

The architecture you started with becomes the foundation of your own infrastructure project — keep what works, adjust what doesn't.

Imported architectures land in the Infrastructure section as a fully editable set of resources.

Deploying or Exporting

Once the architecture matches what you want, ship it in one of three ways:

DeployDeploy directly through Clophi using the deployer service principal.
DownloadExport as Bicep, Terraform, or ARM Template, in either parameterized or non-parameterized form.
CI/CDPush the generated IaC directly to a connected Git repository, where Clophi opens a pull request for your existing pipeline to deploy from.

Archiving for Reuse

Clophi lets you archive a modified architecture under your own name, so the version you tuned for your environment is saved as a reusable starting point.

Share with your organization

While archiving your solutions is highly useful, Clophi also allows you to share them within your organization. You can build a centralized library of architectures tailored to your organization's specific patterns such as standard defaults, tagging conventions, and network topologies. Once your archived solution is saved as an architecture, it appears in the Built-in Architectures section together with the documentation you provide while saving it.

Next time a team member needs a similar setup, they can simply pull the shared solution instead of starting from scratch. Just like any other design in Clophi, your saved architecture is available in all major IaC formats (Terraform, Bicep, and ARM), enabling seamless collaboration between teams with different IaC preferences.

Building organizational knowledge

A saved architecture preserves not just the resource configuration but the decisions you made adapting it and the relevant documentation. Over time, your archive becomes a record of how your team actually builds on Azure.