Fabrik
Fabrik is a visual operations console for Cisco ACI. Query, automate, and audit your fabric without writing REST calls or YAML by hand.
Fabrik is a visual operations console for Cisco ACI. You draw a query on a canvas, Fabrik turns it into an APIC REST path, runs it, and streams results back — no moquery, no hand-crafted URL, no YAML until you actually want one.
It is built for the people who live inside the fabric every day: operators chasing a change that broke something, automation engineers who need bulk moves done safely, and team leads who need to see who did what and when.
Run Your Fabric.
Who Fabrik is for
Network operators use Fabrik to answer a question quickly — "which EPGs on this tenant are missing contracts?", "what changed on this BD since yesterday?" — without leaving the UI or stitching together REST calls.
Automation engineers use it to turn those questions into repeatable actions: save a query, schedule it, pipe its output into an Ansible job through AWX, and keep an audit trail of every execution.
Team leads and admins use the permission model, audit logs, and Time Machine snapshots to keep the fabric observable and the team accountable — without giving everyone raw APIC admin access.
What you can do
Visual Query Builder
Drag ACI classes onto a canvas, connect them along the MIM hierarchy, apply filters and post-processors, then execute against a live APIC.
Library
Save queries, turn them into parameterised templates, and share them with your team.
Time Machine
Snapshot your fabric on a schedule, diff any two points in time, and spot drift with a visual heatmap.
Ansible Automation
Connect to AWX, define typed input schemas for your templates, validate before you run, and watch executions live.
Task Management
Schedule recurring queries, monitor background jobs, and review run history in one place.
Administration
Manage users, groups, and permissions. Every privileged action lands in an immutable audit log.
Notifications
In-app and email alerts, digest delivery, and escalation rules when something really needs a human.
How it works at a glance
You register an APIC connection once. From then on, every query you draw on the canvas is translated into an APIC REST path, executed by the backend, and streamed to your screen over a WebSocket. You can save the result, schedule the query, feed its output into an AWX job, or compare it against a Time Machine snapshot from last week.
Under the hood, Fabrik keeps a local copy of the ACI Managed Information Model (MIM) in Neo4j — the class hierarchy, relationships, and property metadata — so the canvas can validate connections and suggest what comes next. It does not mirror your live fabric state; queries always hit the APIC directly.
Why visual, not CLI
Every ACI operator has done it: a contract isn't being applied, so you ssh in, run moquery against three classes, pipe the output through grep, and try to reconcile what you see with what the GUI shows. It works. It is also slow, hard to share, and impossible to audit.
Fabrik takes the same intent — "walk the MIM from this tenant down to its endpoints and filter for X" — and expresses it as a diagram you can read in a glance, save by name, and hand to a teammate. The generated REST path is right there if you want to copy it. The result is right there if you want to pipe it into Ansible. And six months from now, the audit log still knows who ran it.
The CLI isn't going anywhere. But most fabric questions don't need a CLI; they need a good interface.
Next steps
Getting started
Sign in, connect your first APIC, and run your first query.
Explore the Query Builder
Learn the canvas, filters, post-processors, and execution pipeline in depth.
Deploy your own instance
Self-host Fabrik with Docker Compose — requirements, environment variables, SSL, backups, upgrades.
New to ACI itself? Fabrik assumes you know your way around tenants, BDs, EPGs, and contracts. If those terms are new, keep the Cisco ACI Fundamentals guide open in another tab — the Query Builder will make a lot more sense.