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/Company/About

The company

Built by practitioners. For the work IT really does.

Seraph helps MSPs and enterprise IT teams complete support, maintenance, and project work with AI. Access is scoped, a person remains accountable, the target helps verify the result, and one correlated record carries the evidence.

The company, in facts you can check
what we sellAI-assisted support, maintenance, and project work with scoped access and a signed correlated record.
who it is forManaged service providers and internal IT teams in regulated verticals.
the ruleExplore the workflow, its controls and its evidence in a demo.
what we will not shipA mode where nobody's name is on the work.
certificationNone held. We say so on the trust page, in the first sentence.
how to test usThe Verified Operation Spec — six yes/no questions, written to be used against us.

The one line

Leased privilege, model-blind execution, target-verified completion, declared rollback.

That sentence is the whole company. Every screen, every runbook and every argument on this site is downstream of it, so it is worth drawing rather than repeating.

The product in one linedrawn
THE PRODUCT IN ONE LINE Leased privilege Model-blind execution Target-verified completion Declared rollback The signed receipt Admin rights for minutes, scoped to this one job. The model never receives a credential value. The machine that changed answers a fresh check. The undo is written down before anything runs. One locked record, one reference number. SKIP ANY ONE OF THE FIVE AND WHAT YOU HAVE IS AUTOMATION WITH A LOG FILE
The rail changes colour at the third station, and that is where the argument lives. Everything to the left of it is something a vendor can assert about itself. Everything to the right is something the machine you own had to agree with.

Who this is for

Three people, one record.

We built this for teams that need support, maintenance, and project work to move without losing who authorized it, what changed, or how the target verified it.

Managed service providers

You already carry the risk of every client's environment on a margin measured in single digits. Proof is the only thing on your invoice that a client cannot get cheaper elsewhere.

For MSPs →

Internal IT in regulated work

Healthcare, legal, finance, public sector. Your change process already exists and already works. What it lacks is a way to let something automated inside it without breaking separation of duties.

For enterprise IT →

And the person who asks

A practice manager, an underwriter, or an internal auditor may never log into our product. The record still has to make sense to someone who has never seen the tool.

Outcome receipts →
Where one record ends upOP-000217
THE SAME RECORD ANSWERS THREE DIFFERENT PEOPLE OP-000217 authorized · Marcus R lease · 8 min, expired confirmed · SRV-ACCT-02 Your client "What did you actually do on my network this quarter?" Their insurer "What is your automation allowed to do — and how would you know?" Their auditor "Who authorized it, and can the record be changed afterwards?" ONE EXPORT · THREE AUDIENCES · NOTHING RE-KEYED BY HAND
None of these three people wants a dashboard. They want one artifact that answers their own question without a phone call, which is why the export is designed to leave the building rather than to look good inside it.

Why the company exists

AI got good at doing the work before anyone solved checking it.

The industry answered "can we trust the AI?" with better prompts, longer transcripts and a confidence score. Those are all the model talking about itself. The only answer that survives a hostile question is an independent one: the machine that was changed says whether it changed.

  • Standing privilege was the original sin. Automation needed rights, so it got permanent rights, and every audit since has been an exercise in explaining an account nobody can remove.
  • The evidence and the actor were the same party. A tool wrote a line about its own work, and that line became the audit trail. Nobody designed that; it accumulated.
  • AI made both problems worse at once. Now the thing acting is non-deterministic, holds standing rights, and writes a fluent, confident account of what it believes it did.
  • So we inverted it. Privilege is leased and expires. The model never receives a credential. The target machine answers. The undo is written first. What comes out is a record, not a narrative.

This is a young company building an ambitious product, and we are not going to pretend otherwise on the page where we introduce ourselves. What we can defend is the architecture and everything that is already running — and we would rather you tested both than took either on trust. The trust center →

Constraints we chose

What we will not build.

These are not warnings about a future release. They are decisions, and each one costs us something in a sales call.

  • A mode where nobody's name is on the work. Autonomy changes when a human authorizes, never whether a human is accountable. Someone is always on the record.
  • Metered proof. Review the published package scope and evidence capabilities with your operating requirements before purchase.
  • A certification we have not finished earning. SOC 2 Type II is on the roadmap and the report is not in hand yet; until it is, we hand you the evidence directly instead of a badge. Where we stand on assurance.
  • A claim we cannot demonstrate. If it cannot be shown on a live system, it comes off the site — including off this page.
  • Invented proof. No customer names we do not have, no fabricated case studies, no metric we cannot source. The illustration on this site is a printer at a medical practice, and it is clearly an illustration.
  • Unclear enrollment allowances. $200 per tenant plus $299 per named technician monthly, with 30 enrolled endpoints per technician. Review the allowance before purchase.

The standard we hold this site to

Sixty seconds, or it does not belong here.

The sixty-second rule A claim on this site should be demonstrable on a running system. If a detail cannot be shown, ask us through the contact page; it reaches an engineer who can tell you what is available today.

There is no team page here, no headcount, no funding announcement and no customer logos. When those things are real and worth saying, they will appear with something you can check attached to them.

The short version

Support the ticket. Verify the result. Share the record.

Fifteen minutes to walk through one supported operation, its correlated record, and the recovery options available for that runbook. Bring the hardest question from your last client review.