Start an evaluation
Your account
Where your licence, your usage, your invoices and your support live — and where you can check every number we bill you for against your own records.
It is not where the product runs
Dream-Genie runs on your hardware. Your account here does not touch it, cannot reach it, and holds none of your data. There is no remote access path from us to your deployment and no code path that could open one.
What lives here is the commercial side: your licence, what you have been billed, the documents your accountant needs, and the people you have given access to.
A bill you can check
Every period we bill you for is computed from a record your own deployment signed and sent. That record is here, readable, before and after we invoice against it.
The rate is published. The rounding rule is published. So you can take your own signed record, do the arithmetic yourself, and arrive at exactly our number — and if you ever do not, that is a defect on our side and we want to hear about it.
We bill on p95, not peak. A day where you imaged forty machines is not a month where you managed forty extra. Committed, variable and outstanding are three figures and we never blend them into one.
The rate and how it is calculated is public, and it does not change based on who is asking.
Documents your accountant can file
An invoice per period carrying everything your jurisdiction requires — our legal identity, the tax treatment stated plainly, the period, the line items and their basis, and the currency.
An issued invoice is never edited. If something needs correcting you get a credit note and a new invoice, because an invoice you have already filed and one that can still change are two different documents.
And they outlive the relationship. If you leave, your invoice history stays readable. It is yours.
Support that has read your version
Not the current source — the source of the release you are actually running. If you are three versions back, the answer is about the code you have, and where the answer differs in a newer release it says so and names the one that changed it.
An answer correct about the wrong version is worse than no answer, and most vendors give you the first one.
“That message comes from collector/poll.go line 412 in the version you are running. It fires when an SNMP walk returns a partial table and the OID map has no entry for the trailing index. Your log shows it eleven times against the same device, which means the profile is incomplete rather than the device being unreachable.”
And most problems are not our code. A GPU driver that did not load, a firewall dropping SNMP, DNS pointing a collector at the wrong interface, a full disk. We diagnose those too — “that is not our software” is not an answer we are willing to give you.
Updates you pull
Your deployment asks. We never push. There is no path from us into your estate and no code that could create one.
You see what is available, what changed, and what is known not to work — because a release note listing only improvements is telling you half the story.
A withdrawn release stays visible with the reason it was withdrawn. You need to be able to explain what you were running last month.
What we actually receive
Ten fields and a signature. No client names. No hostnames. No addresses from your estate. No ticket content. No telemetry. No credentials in any form.
A payload carrying anything else is rejected in full, not stripped — because silently removing something would mean we never learn your deployment has a defect.
You can read the record before it is sent. The full field list is published, and it is the same ten fields for everybody.
Your people, and what each of them can do
An MSP is several people and usually one of them bought it. Add whoever needs access, with the role that fits — and roles are enforced where the action happens, not by hiding a button.
Changing what you run costs no more effort than buying it. Adding seats and removing them take the same number of actions. If growing were easy and shrinking were a phone call, we would be telling you something about ourselves.
A monthly note that is actually about you
Not a newsletter. It waits in your account rather than arriving in your inbox, and it is assembled from your own records: what changed in a release that matters to your version, a question you asked that is now answered better, what your numbers did.
And if there is nothing to say in a section, that section is not there. A monthly that is the same length every month is one somebody is filling.
What we will never do
- Contact your clients. Ever, for any reason. That relationship is yours
- Push anything into your estate. Your deployment asks; we answer
- Track whether you read something. No open tracking, no pixels, no read receipts
- Bill you for a period you cannot check against your own signed record
- Delete your documents because you stopped being a customer
- Report a number we did not measure, on any surface, for any reason
If something breaks, we would rather find out from you than from nobody
Optional, off by default, and a separate thing from your usage record. If you turn it on, a deployment that hits an unhandled error can tell us the shape of it: the version, the fault class, the file and line, and the state of the machine.
Never what the code was operating on. No client name, no hostname, no address, no log content, no query text. A report carrying what it was working on rather than what it was doing is a data leak with a stack trace attached.
You read every report before it leaves, and afterwards. And a refusal is not a fault — Genie declining to do something is the product working, and it is never reported as a failure.
An MSP who never enables it loses nothing. The platform behaves identically. What it buys, if you do, is that three deployments hitting the same thing is a defect we know about on the day — and you get told when the fix exists.
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.