Why Infrality exists.
Network documentation goes stale because drawing a network and checking it are two jobs, done in two tools, by people who rarely meet. Infrality makes them one board: a scanner says what is there, a team says what it means, and neither overwrites the other.
What it is built on.
Five rules every screen of the product answers to. When a feature would break one, the feature changes.
- 1
The map is documentation, not decoration.
Every element can carry an owner, a status, an explanation and its runbook, and every view can be read without the person who drew it.
- 2
Discovery is evidence; edits are authority.
A scan proposes and a person decides. Nothing a person wrote is silently overwritten, and nothing a sweep missed is silently deleted.
- 3
Nothing is invented.
Absent data reads as absent, never as a default. A router the agent had to assume is labelled as assumed.
- 4
Built for estates.
Density, keyboard, search and bulk actions over ornament: a board of a thousand nodes has to stay usable.
- 5
Teams, not authors.
Who changed what, who is looking at it now, and what is still unanswered are always on screen.
Where it comes from.
Infrality began as an Epitech Innovative Project, the final-year engineering project at Epitech, and is now being built into a product for the teams that keep networks running.
It is designed, built and hosted in France. The service runs on OVHcloud, and your data and its backups stay in the European Economic Area.
It is in beta: every feature is free while we learn from the people using it. What is not built yet is listed, under its own name, on the product page — and every message sent through contact is read by someone who can change the product.
Published by Robin Caboche. See the legal notice.
Start with one network.
Create an account, draw or import a board, and put the agent on one machine when you want the map to keep itself current. Every feature is free during the beta.