Home/Contact
Contact
Four ways in. All of them reach a person.
We are small enough that every message is read by someone who can answer it. Pick the door that matches what you need — it changes who picks it up and how fast you get something useful back.
Four routes
What each one is for, and what comes back.
See a demo
Fifteen minutes, live: walk through one supported operation, open its correlated record, and review recovery options where the runbook provides them. Bring the hardest question from your last client review.
What comes back: times, and the ticket we intend to run — so you can tell us to run a harder one.
Book a demo →The Foundation Circle
Discuss how Seraph fits your first recurring operation. Standard monthly pricing applies; any special scope is agreed separately.
What comes back: a yes or a no on a seat, after the live run. There are eight, so we will tell you if they have gone.
Apply →Security and architecture
Model-blind execution, leased privilege, tenant isolation, how evidence is signed and what a recipient can verify without us. Read the trust centre first — it answers most of it, including the certification question, plainly.
What comes back: a written answer from someone who can read the code, not a sales summary of it.
Trust centre →You already have a workspace
Something is wrong, something is confusing, or you want a runbook certified for a client you just onboarded. Say which workspace and what you were trying to do.
What comes back: the people who actually run your workspace — the same ones who would handle the operation.
Write to us
Say which door, and be specific.
The more concrete the message, the more useful the reply. Name the vertical, name the thing that broke, or paste the question your client’s security questionnaire asked you — that is the one we are best at answering.
- If you want the demo, tell us what you want proven and we will build the run around it.
- If it is a security question, check the trust centre first; it is written engineer to engineer.
- If it is about price, it is already published in full — you do not need a quote to read the number.
SOC 2 Type II is on our roadmap and the report is not in hand yet. If a completed report is a gate in your review process, say so in the message and we will tell you exactly where we are on the first call rather than in diligence.
Two things worth knowing
Before you write.
Reporting a vulnerability
Use the security door and say so in the first line. Do not include credentials, tokens, real hostnames, device ids or tenant ids in the message — a description of the flaw is enough to start, and we will arrange a private channel for the detail.
How we handle disclosure →Data and privacy questions
What we collect, where it lives, how long evidence is kept and how tenants are kept apart is written down. Read it first, then ask us about anything it does not cover — the specifics that belong in an agreement are handled there, not on a web page.
Privacy →The shortest route is the demo
Fifteen minutes answers more than any email thread.
One supported operation, its target-side verification, and its correlated record. Where recovery is available for the runbook, we review that path with you. Bring the hard question.