INFRAHUB REFERENCE DESIGN

What you need to automate an AI data center build—ready to run.

From the first fabric through Day Two changes, get a complete example of design-driven automation you can take and make your own.

Clone and run a working Infrahub build of a complete fabric— Fabric → Pod → Rack—with an EVPN/VXLAN overlay, rendering configuration for Cisco, Arista, and Dell. Open source and free to run.

Build on automation that already runs

Start from a proven automation architecture instead of assembling one yourself. Run it, read it, and adapt it to your design and vendors.

Build a complete fabric from a small set of design inputs: The Generators produce the devices, addressing, cabling, and configuration.
Keep every site consistent, and change it without rebuilding: Design intent is stored with the infrastructure it produce so Day Two changes stay scoped to what changed.
Adapt it to your environment: The patterns extend to your own topology, vendors, and standards.

Evaluating Infrahub for a data center build?

Run the reference design to see how it delivers.

Already building?

Use it as the working reference that shortens your implementation.

What's included

From design to device configuration

The data model and automation, already built

You get pre-built schemas, four modular Generators, resource pools, and per-vendor device templates. It's all the code you'd otherwise write before a build can start.

Describe the design, get the implementation

Define the fabric's shape—pods, racks, addressing—and the Generators produce the devices, IP allocations, cabling plan, and configuration for Cisco, Arista, and Dell.

Change one layer without touching the rest

One Generator builds each layer—fabric, pod, rack—with a separate Generator for EVPN/VXLAN tenant services. Understand, test, and adapt each layer in isolation.

How it works

Define the design, generate every layer

Your design lives as structured data in Infrahub. Generators read that intent and produce the implementation.

Design-driven

Intent persists as queryable data, independent of the devices generated from it.

One design, per-vendor output

The same design renders Cisco, Arista, and Dell configuration, each device routed to its template.

Scoped Day Two changes

Add a rack by creating one object and running one Generator. Changes go through branches, review, and CI.

Running an Arista fabric with AVD? The AVD reference design is built for that toolchain.

Get started

See it in action

Watch the Generators build a complete fabric from design inputs, then a scoped Day Two change—adding a rack without touching the rest.

Then run it in your own environment

Clone the repository and run it locally.

Follow the demo guide in the docs, step by step.

Adapt the schemas and Generators to your design.

Get started  your way →

Infrahub Community

Open source and forever free. All the schema flexibility and Git-style version control you need to explore at your own pace.

Download on GitHub →

Infrahub Enterprise

Built for scale, complexity, and production reliability — HA, advanced integrations, and SLA-backed support.

Request a demo →