Seeing it for yourself
How to look at a populated console before enrolling a machine, and where the full documentation is.
On this page
Look at a populated console before enrolling anything
There is a switch in the organisation's settings that seeds a plausible fifty-device fleet with a month of history: devices with real-looking posture, tools, MCP servers, token cost and events. It exists because "what does this actually look like" is a fair question to ask before asking anybody to install software, and a console showing four empty states answers it badly.
Turning it off removes every trace. It is not a sandbox tenant or a separate environment — it is your organisation, with demonstration rows in it, and then without them.
Or start with your Microsoft tenant
If you manage devices with Intune, the Microsoft connection produces a real number about your real estate before a single machine is enrolled: how many managed machines endlayer cannot see. It is read-only, and it is the shortest path from "we are evaluating this" to a figure worth discussing.
A trial, in the order it usually goes
Your organisation is provisioned
An administrator you name receives an invitation. There is no self-serve sign-up — an instance is created for you, and the invitation lands by email.
Look around
With demonstration data, or with your Intune inventory, or both.
Enrol a handful of machines
Ten minutes each by hand, or one enrolment secret through your management tool. Start with machines whose owners know it is happening.
Set the policy baselines
This is the step that turns reporting into grading. Four inputs, and until they exist most controls sit
at ungraded on purpose.
Read it, then widen it
Devices, controls, usage. Then roll out to the fleet.
What to read next
Forty-seven pages: deployment on every platform, the configuration reference, the console view by view, self-hosting, operations and the HTTP API.
The security review pagesEvery signal and its privacy boundary, the trust model, retention, erasure and access control.
The FAQWritten for the reviews this product actually goes through — security, privacy, works council, procurement — and answered directly.
Enforcement, which is not builtThe planned control layer, written so an architecture review can assess the shape before it arrives.
Getting in touch
Through your account team at Holistic AI. If you are already running endlayer and something is wrong,
endlayer doctor is the first thing to run, and the
support page says what is safe to attach to an issue
and what to redact first.