PlatformDelivery BoardAutomation & RunbooksOutcome ReceiptsJust-in-Time ElevationCredential VaultGoverned SessionsDevices & DiscoveryPatch ManagementReporting & ExportsRoles & Multi-Tenancy
Verified AI OperationsThe Operation LoopCommanded AutonomyCompare the operating modelThe Verified Operation Spec
SolutionsFor MSPsFor Enterprise & Internal ITHealthcareLegalFinancial servicesMunicipal & Education
ProofOperation walkthroughSecurity & architectureVerified Operation SpecFive questions for your RMM's AIChangelog
CompanyAboutFounder's noteContact
PricingBuy 1–20 technician licenses onlinePlans — from $499 per monthCustom requirementsFoundation Circle
Log in

Home/Book a demo

Fifteen minutes, live

Bring a workflow. See the whole operation.

Not a slide deck and not a recorded walkthrough. We take a supported ticket, walk through the scoped plan and human oversight, inspect the target's verification, and open the correlated record. Bring the hardest question from your last client review; we will tell you what the live workflow can show today.

What we open at minute 11OP-000217
operationservice recovery
requested byDana K · Teams #it-help
authorized byMarcus R · 09:40
admin accessleased 8 min · expired 09:47
ranrestart print spooler · signed job
the machine saidservice running · queue clear
undodeclared 09:39 · executed 09:53
after the undothe machine said: back as it was
chain 9f3a…c47e DONE & LOCKED

The run

Fifteen minutes, and what to watch for in each of them.

The shape never changes, because the shape is the product. What changes is the ticket — and you can pick it.

What the fifteen minutes coversone operation, live
ONE OPERATION, END TO END — MINUTE BY MINUTE 00:00 05:00 10:00 15:00 00 – 02 The ticket arrives 02 – 05 The plan, and the say-so 05 – 09 The work, under a lease that expires 09 – 11 The machine confirms it 11 – 13 The record, opened 13 – 15 The rollback, executed WATCH: WHO IS ASKING A real person in Teams, not a form we filled in. WATCH: WHO ANSWERS The target machine answers, not the AI. WATCH: THE NAME ON THE APPROVAL A person says yes before anything runs. WATCH: WHAT ELSE IS IN THERE Retries and failures are recorded too. WATCH: THE CLOCK, NOT THE TASK Rights expire on the timer, not on completion. WATCH: WHEN THE UNDO WAS WRITTEN Before the change ran. Check the timestamp.
The four minutes in the middle are the only part the AI drives, and it is the part where the model is holding a reference, never a credential. The eleven minutes around it are a human authorizing, a machine answering, and a record being read.
You pick the ticket

Ask us to run something other than the printer. A stopped service, a stuck queue, a piece of software that needs installing on a machine you name. If it is a certified runbook we run it live; if it is not, you watch the planner say so and ask for a human instead — which is worth seeing too.

Bring the hard one

The question from your last client audit. We answer it on the call.

Most demos end with “great question, let me get back to you”. That answer is worthless to you and it is easy for us, so we would rather not have it available. Send the question in the form and we will build the run around it.

“What did your automation have permission to do at 2am?”

We show you the lease: what it covered, which machine, and the minute it expired on its own. Then we show you the month with a standing account, drawn to scale.

Just-in-time elevation →

“Prove the AI never saw the password.”

We show what the model received — the operation, the target, the runbook, the outcome to reach — and where the credential value stopped. The connection was authenticated before any script existed.

The credential vault →

“Could someone edit that record afterwards?”

We open the chain and show what happens to every later record if one is altered. You can walk the same check yourself on an export, without us.

Outcome receipts →

If the honest answer is “that is not built yet”, you get that on the call too, with what is built instead. A demo that cannot say no is a demo that cannot be trusted when it says yes.

The last two minutes

Then we review recovery, if the runbook supports it.

A recovery path should be declared before the change, when the options are clear. If this runbook has one, we review its timestamp and its place in the same operation record; if it does not, we say so.

The rollback, minute 13 to 15OP-000217
THE UNDO IS OLDER THAN THE CHANGE — THAT IS THE WHOLE POINT WRITTEN AT 09:39, TWO MINUTES BEFORE ANYTHING RAN 09:39 BEFORE · 09:38 spooler: stopped Dana cannot print. THE CHANGE · 09:41 spooler: restarted under an 8-minute lease THE UNDO · 09:53 executed on your word the reversal declared first AFTER · 09:54 back as it was and the machine says so OP-000217 · one operation record The change, the machine’s confirmation, the undo, and the machine’s answer after the undo — all on the same id, in the same chain.
The rollback does not open a second ticket or a second record. It lands on the same operation id, so a client reading the export sees the whole arc — including the part where you put their machine back.

Practicalities

Who should be on the call, and what we will not do on it.

Bring these people

  • A technician. They will spot the shortcut faster than anyone in the room, and we want them to
  • Whoever answers your clients’ security questionnaires. The export is aimed at them
  • Whoever signs. Fifteen minutes is short enough that they can actually attend
  • Your hardest audit question, written down before the call
  • A machine or a ticket type you want us to try, if you have one in mind

What we will not do

Book it

Tell us what to run, and who is coming.

No calendar widget on this page — we would rather read what you want to see first and build the run around it. The more specific the question, the better the fifteen minutes gets.

  • What you send. Your details, your rough size, and the thing you want proven.
  • What we do with it. Pick the ticket and the target so the run answers your question, not ours.
  • What you get on the call. One supported operation inspected, one correlated record opened, and a straight answer about available recovery.

Your request is sent to our team. It does not reserve a time by itself.

15 minuteslive, not recordedyou pick the ticket

Online requests are not available yet. Please check back shortly.

You can also email sales@serverseraphim.com directly.

Fifteen minutes, live, with the person who built it. If you would rather apply for a Foundation Circle conversation at the same time, say so in your message.

Come to check, not to be sold to

Pick a claim on this site and make us show it.

Bring one of the six tests from the spec. We will show the relevant workflow and evidence surface available today, with its limits stated plainly.