Not a feature list. The actual product.
Every screen in here has to survive a technician using it for eight hours.
So none of it is decorated, and nothing shows you a number it cannot prove. Where the product commits to something — billing the 95th percentile, showing drift in both directions, labelling what Genie estimated — the screen is where that commitment becomes checkable.
Reconciliation, running
Claimed state beside verified state, continuously, across every client. This is the thing no competitor can do — checking requires one shared model of what is true, and they have four.
Note the last row. Entra being unreachable is not "MFA is fine" and it is not "MFA is broken" — it is unknown, and the product says so. Absence is never reported as confirmation.
The local agent — where the work actually happens
A capture taken on the technician's own machine, on the client's VLAN, in the comms cupboard. The platform physically cannot do that, which is the entire reason this exists.
"Is it the network or the server?" is the most escalated question in IT and the one most often answered backwards. Most engineers cannot get that from a packet trace. Genie does it in seconds, on every capture — and when the capture cannot support the answer, he says what to recapture instead.
What your client sees
Branded to you, not to us. This portal is your shop window — your client judges you by it, so it is held to a higher standard than anything else in the product.
"92%" and "5 of 64 missed" sit together deliberately. A client who later discovers a hidden breach stops trusting every other number on the page. And "what didn't happen" is the panel no competitor can produce — it needs the reconciliation engine to evidence it.
Genie's shift
Step away for two hours and come back to work that happened, not a queue that grew.
Read the last line. Genie's refusals appear as work items with reasons, not as errors — which is how a technician learns his boundaries without reading documentation. AI does all the work. A human makes every commitment.
Describe the job. Get everything needed to deliver it.
A technician types what a colleague would understand. Genie reads the estate first, then produces the plan, the price and the documents.
The input
"Northwind needs their file server replaced. Old one's out of warranty, 2TB of data, twelve users, they'll want it done over a weekend."
The quotation
For your client's finance director. Priced from your rate card and live distributor pricing, every line tracing to the plan step that produced it, one-off and recurring shown separately, exclusions explicit. Your branding, not ours. And it prints in greyscale, because somebody will print it for the meeting.
The project plan
For whoever schedules it. Phases with their tickets, dependencies drawn, effort from your own history with the comparison shown — "your last three averaged 14 hours; this is 2TB rather than 800GB, so I've estimated 18." Where it can't commit, it says so.
The implementation runbook
For the technician at 2am. Ordered, not grouped. Every step carries its ticket, an observable check for "done", and what to do if it fails. The point of no return is marked before you reach it, rollback sits inline at each stage, and it works on paper with no signal — because a server room usually has none.
All three render from one plan. Change the plan and all three change — no figure in one can contradict another. On acceptance the tickets exist, procurement raises, preconditions block the first step, and the promise lands on the client's record beside everything else you owe them. Acceptance is a recorded human act. "Looks good, go ahead" in an email starts nothing.
What we won't tell you
Most platforms in this market sell failure prediction. We looked at whether it can work at your scale and concluded it cannot.
Every production system where hardware-failure prediction demonstrably worked ran on fleets of ten thousand to millions of machines. At that size a 1% annual failure rate still produces thousands of labelled events to tune and validate against.
A two-thousand-drive estate produces about twenty-seven failures a year. You cannot tune a threshold on twenty-seven events, and you certainly cannot tell a working predictor from a lucky one.
It gets worse: two independent studies nine years apart found more than a fifth of failed drives gave no warning at all — no SMART counter moved before they died.
So we don't predict hardware failure. We tell you what is running out and when — a disk at 94% growing 0.8% a day reaches full in eight days, and that is arithmetic you can check rather than a model you have to trust.
We would rather ship four things that are calculations than seven that are guesses. A prediction nobody can validate is a prediction nobody should act on.
Thirty days. Every module. Your real estate.
Run Dream-Genie read-only alongside your current stack. We'll show you what your tools are hiding, in your own data, in dollars.
If it doesn't catch something your current stack missed, walk away.
hello@dream-genie.aiSee it on your own estate
Read-only for thirty days. Nothing is changed and no client is contacted.
Genie is the AI at the centre of it — with tools, boundaries and an evidence standard, not a chat box over a knowledge base. What he actually does.
It scales by adding capacity, never by splitting your clients up
Reconciliation works here because there is one shared model of what is true. A cluster that partitioned your clients across nodes would have four models again — which is the incumbents' problem, reached by a different road.
So no client, site or tenant ever lives on a node. Every node answers every question about your whole estate, and adding one adds throughput. And every comparison reads one node in one transaction — a reconciliation assembled from two nodes would be comparing two different moments.
It reads from Microsoft 365, Entra ID, Active Directory, SNMP devices, Hyper-V and VMware, and writes to your accounting software. What it talks to, and what it refuses to.
Try it on your own estate
Thirty days, read-only, on your own hardware. No card, no call, and nothing to uninstall if you walk away.