Start an evaluation

Certification

A qualification earned by doing the work in the product — not by watching a video and answering questions about it afterwards.

Every vendor in this market has a university

ConnectWise, Kaseya, Datto. Hours of video, a multiple-choice test at the end, a badge. They exist because they work commercially — a technician with a certification has a reason to stay, and a practice with three certified staff has a reason not to switch.

They do not work educationally. A test taken immediately after a video measures whether somebody watched a video. Everybody in this industry knows it, and the people who know it best are the technicians holding the certificates.

We can do something none of them can. The platform knows what you have actually done in it.

EVERY OTHER CERTIFICATION watch recordings answer questions about the recordings a percentage expires on a calendar THIS ONE do the thing, in a sandbox the record is what you did expires against the product version no grade, ever A percentage is a number about a person that follows them, and it is the thing somebody optimises for. We do not produce one.

Demonstrated, not watched

A competency is earned by doing the thing, in your own deployment or in a sandbox that produces the situation on purpose. What you did is the evidence — the act, dated, resolvable.

RouteWhen it is used
Demonstrated in your own deploymentthe platform observed you do it — the strongest route, and the default
Demonstrated in a sandboxthe same act against a seeded scenario, for anything destructive or rare
Assessed by questiononly for judgement with no observable outcome — when would you not auto-approve this

The third route can never carry a competency on its own where an observable one exists. That is the line between this and a video course, and the gate that certifies our own build enforces it.

Genie teaches what you have never seen

This is the part a video library cannot do. He builds your path from the gap, not from a syllabus.

“You have run forty patch cycles and never once hit a supersedence conflict — your estate has not produced one. That is the single most misread screen in this product, so here is a sandbox that produces one.”

A person who has run a service desk for a year skips that track. A person who has never performed a restore is walked through one. Somebody with twenty years of experience does not sit through an introduction to SNMP.

Every explanation is grounded in the documentation for the version you run — not the newest one. And where he cannot ground something, he says so and does not teach it.

He never marks a competency earned. He teaches, he sets the scenario, and he explains what went wrong. What earns it is the platform's own observation of you doing the thing.

Nine tracks

  • Operator — install, upgrade, backup, restore, sizing, the support bundle
  • Monitoring — agents, SNMP depth, topology, baselines, suppression
  • Patching — rings, supersedence, maintenance windows, the evidence tiers
  • Service desk — intake, SLAs, the autonomy ladder in daily use
  • Security — SIEM, detections, forensics, email operations
  • Microsoft 365 — tenants, provisioning, joiners and leavers, posture
  • Backup — the three states, and why reported is not verified
  • Commercial — agreements, time, billing, the reconciliation
  • Working with Genie — what he does, what he refuses, and why a refusal is not a failure

What the certificate says, and what it does not

It names you, the track, every competency, how each one was earned, the release it was earned against, and the date.

And nothing wider. Certified on patching means certified on patching. It does not quietly become “certified administrator” because that reads better on a proposal.

Publicly verifiable from a link, because a client reading your proposal needs to be able to check it. The verification page shows exactly what it attests and nothing more.

It expires against the product, not the calendar

A certification earned on 1.4 is a statement about 1.4. When a later release changes what a competency covers, the certificate says so and names the release.

It does not silently become false, and it does not expire on a date somebody chose because annual renewals are good business. A certificate describing a build nobody runs is a badge.

What we will never do with it

  • Publish a pass rate, a completion percentage or a leaderboard
  • Rank your technicians. A certification used to rank people is one they will resent, and rightly
  • Treat your progress as telemetry. It belongs to your account and never enters anything we receive
  • Charge separately for it. It comes with the platform
  • Certify anything by clicking through. The moment that is possible it is worth nothing to you and nothing to us

Revocable, by a named person, with a reason — issued in error, earned fraudulently, or an assessment later found broken. A revoked certificate stops verifying immediately, and the record of it stays.

Why it is worth having

A certification that says you have demonstrated something is worth something. One that says you watched a video about it is worth a badge.

Your clients can check it. Your staff earned it on work they actually did. And when the product changes, it tells you what changed rather than pretending nothing did.

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.