Documentation
If the instructions are wrong, that's a defect.
Documentation is written against the product as it actually behaves, and the install guide is tested by following it verbatim on a clean machine. If the instructions are wrong, that is a defect and it is treated as one.
Getting started
Working with Genie
Modules
Operations
Every module ships an audit document recording what was built, what was deliberately left out, and what is known not to work yet. We'd rather hand you an honest limitation than have you find it during an incident.
Every module documents its own limits
Alongside the how-to, each module ships an audit document recording what it does, what it deliberately does not do, and what it cannot determine.
Where a device class cannot be verified, where a vendor API does not expose a field, where a check is a partial control rather than a structural one — it is written down, in the documentation, before you meet it.
Not in the documentation
Ready to try it?
Thirty days read-only on your own estate. The install guide is tested verbatim on a clean machine.
These pages describe the version you are running
Signed in, you see documentation for your release — not the newest one. Where a fact changed in a later version, it says so and names the release that changed it.
Every build publishes what it actually does — its boundaries, its autonomy tiers, its configuration options and defaults, its tested integrations — derived from the code rather than written from memory. These pages render from that. A page describing a build you do not have is a page lying to you politely.
The prose is written by a person. The facts inside it come from the product itself.
Your staff can certify on the platform — nine tracks, earned by doing the work rather than watching a video about it. Certification.
Not running it yet? Start a thirty-day evaluation — read-only, on your own estate, no card.