Get access

Aegis by Salanor

Aegis
Verifiable decisions for automated actions.

Check sensitive actions against your rules before they run, ask a named person when needed, and keep a signed record you can show an auditor.

Rule → record → proof

Three questions most teams cannot answer quickly

  • What data was used?
  • Which rule applied?
  • Who approved it, and when?

Check, decide, prove

Check

Match the action against your rules and authority limits before it runs.

Decide

Allow, stop, or ask a named person when your policy requires it.

Prove

Keep a signed record that cites sealed events you can verify later.

From the action to a record you can show later

Four steps. Technical terms are explained on the for engineers page.

01

Connect one workflow

Send the attributes for one sensitive action from your system or agent.

02

Check before it runs

A rule runs before the risky action. It can allow it, stop it, or ask a person to approve.

03

Keep a clear record

Each step is written down: who decided, what ran, and which rule applied.

04

Hand over the proof

Export a signed bundle. Risk can verify it offline without digging through logs.

Illustrative example: a loan decision

  • Your system sends the event. Aegis checks your rules before the action runs.
  • It can allow, stop, or hold for a named person. Approvals are logged with role and time.
  • A signed receipt cites the sealed events underneath, so an auditor can verify the record offline.

Synthetic data. Banking walkthroughs live on the banks page. Same pattern for claims, payments, or data access.

Your cloud or ours

Hosted by Salanor, or on your side. You choose per deployment. Keys stay under your control where you configure them.

What is stored, signed, and not provided yet

  • Stored. Decision attributes you send, policy versions, approval metadata, and signed event hashes. Field policies can mask or omit sensitive values.
  • Signed. Events and forensic receipts are signed with keys you register. Offline verification checks signatures, hashes, and sequence continuity.
  • Not yet. We do not claim FedRAMP or HIPAA authorization. Cloud KMS Sign and production TSA are available when you configure them; development keys are refused in production.

Full detail on the security page.

Pricing in brief

  • Free tier for evaluation.
  • Team plan at $299 per month.
  • Regulated institutions: custom.

Full pricing page

Evidence for audit, not slide decks

Export bundles map to frameworks we support today. See trust center for live status. Mapping is not certification.

Available in exports today

SOC 2Control mapping in export ZIPs · Mapping, not certification
EU AI ActArt. 12 record-keeping mapping in exports · Mapping, not certification

Roadmap

NIST AI RMFPlan — not available yet
HIPAAPlan — not available yet
FedRAMPPlan — not available yet
ISO 42001Plan — not available yet

Short answers

What is it?
Aegis checks sensitive automated actions against your rules, asks for approval when needed, and keeps a signed record.
Does it replace our systems?
No. Your systems still run the action. Aegis sits in front for rules, approvals, and evidence.
What data does it see?
The attributes you send for the action. Field policies can mask, hash, or omit sensitive values.
Where does it run?
Hosted by us, or on your side. You choose per deployment.
What if it is unavailable?
Each workflow sets hold or proceed-and-flag. Queued decisions can be replayed when Aegis returns.
How do we know a record was not changed?
Export a bundle and verify it offline. Tampered facts, signatures, or sequence gaps are reported by name.
Is it certified?
No. Export bundles include control mappings. Mapping is not certification.
How do we start?
Pick one workflow, often in record-only mode. Agree success criteria, then talk to us.

One next step

Tell us the workflow you want to govern. We will reply with a short scoping plan.

Talk to us