product · network automation
alembic
translates infrastructure data between systems through a shared model.
one network, described differently by every system
the problem
a device is a record in netbox, a host in ansible, a target in prometheus, a name in dns. keeping them consistent usually means scripts written pair by pair, rewritten whenever a system changes.
alembic’s role
alembic owns the translation. you define one model of your infrastructure, and every system connects to it instead of to each other.
what teams use it for
moving between inventory platforms
migrate from nautobot to netbox, from netbox to infrahub, or consolidate several instances into one, without losing relationships along the way.
keeping systems in sync
run inventories side by side and let them exchange data through one model instead of pairwise scripts.
driving fabric and ops from data
generate ops tooling inputs from the inventory you have instead of keeping it up to date by hand.
supported systems
every system connects to your model through a connector. each is an input or an output.
open source
included in the release. inventory systems.- netbox
- nautobot
- infrahub
- generic restany rest apigeneric connector
- peeringdbread only
commercial connectors
annual licence. fabric and operational tooling. supported operations differ by connector.- config
- ansible ·, avd ·, nornir ·, ssh
- validation
- batfish ·, via avd
- lab
- containerlab ·, eve-ng
- monitoring
- prometheus
- naming
- dns
- diagrams
- dot ·, mermaid
supported operations differ by connector.
not listed? new systems connect through an open source interface. we build them for you or you build your own.
how it works
source data →read
connectors read from your source systems.
shared model →map into your model
each source is mapped in your model. transformations are written down in one place and validated against the types and relationships of the model.
planned changesplan, review, apply
alembic compares the model with the destinations and produces a plan. you review it, and apply it explicitly.
open source, with a commercial layerpricing
free
the model, the engine, and connectors for the main inventory systems.
model, engine, and inventory connectors. apache-2.0.
from €6,000 / year
fabric and operations connectors, priced by the connectors you need.
annual licence, priced by the connectors you need.
€1,400 / day
most initial deployments land between €10,000 and €20,000, including integration.
most initial deployments: €10,000–20,000 including integration.
next steps
evaluate it yourself
the source, documentation, and examples are public. install a release and point it at your lab.
github.com/cyberwitchery/alembicplan a deployment
tell us what you run. we confirm connector availability and scope the integration.