Sigilant · Control for AI agents

Put AI to work, without losing control.

AI agents are being switched on across your business faster than anyone can count them, and they already raise orders, change records and move money. Sigilant gives every agent its own identity, an owner and your rules, so you can say yes to AI and prove it is under control.

Isometric diagram: requests from AI agents on the left pass through the Sigilant gateway in the centre, where each is allowed, refused or held for a person, and the allowed ones go on to business systems on the right.

Proudly partnered with

SCX.ai logo Sovereign inferenceSCX.ai DekkoSecure

Does this sound familiar?

Three questions you will be asked about your AI.

Today, most businesses cannot answer them. With Sigilant, you can, and you can prove it.

Three AI agents on a register, each with its own identity and a named owner; one is linked to the person it is acting for

The audit

"Show me a list of your AI agents, and who looks after each one."

Today: a spreadsheet, if you are lucky. Some agents use a staff member's login. Nobody is sure what each one can reach.

With Sigilant: every agent has its own ID and a named owner, who checks in regularly to confirm it is still needed. When an agent works for someone, the record names both.

Three AI agents share one key into a business system

When something goes wrong

"What did the AI do, for whom, and who approved it?"

Today: all the agents share one password, so your systems cannot tell them apart. Nobody can say which one did it, or whether anyone agreed.

With Sigilant: every action is on the record: which agent, for whom, and who said yes. When an agent placed a $48,000 order, it waited for a named manager's approval, and the record shows it.

An AI agent stopped by a barrier in front of a locked business system

Your customer

"How do you control what your AI can access?"

Today: a paragraph of good intentions. Often the AI holds a password to the system, and nobody can say exactly what it can reach.

With Sigilant: the AI never holds a password. Sigilant lets it in for one allowed job, then locks the door again, and you can show your customer the rules and the record.

What it costs you today

Without control, four things go wrong.

Each AI agent needs its own ID, like a staff badge: which agent it is, who it works for, and what it may do. Without one:

01

You cannot explain what happened

Who did it, for whom, and who said yes? Nobody can tell you.

02

You cannot stop it quickly

Switching off a shared password breaks everything that uses it. So nobody does, until it is too late.

03

You do not know how many you have

AI comes built into the software you buy and the tools your teams make. The ones you cannot see are the risk.

04

AI projects get stuck

Without a safe way to say yes, the answer is no, and the business waits.

See it working

One AI agent, from start to finish.

From our demo: an AI agent that buys things, a manager called Priya, and a finance system. The rules for what the agent may do, and who must approve it, live in Sigilant, not inside the agent or the finance system.

  1. 1Priya logs in as usual. The agent is now known as hers.
  2. 2Her agent tries to place a $48,000 order.
  3. 3That is over the company's limit, so Sigilant holds it. The finance system has not seen it yet.
  4. 4Priya sees exactly what is waiting, and says yes to that one order.
  5. 5Only then does the order reach the finance system.
  6. 6Later, someone switches the agent off. It stops straight away, along with everything it started.
Console: the approval record for erp.create_purchase_order, approved by Priya for one exact call with a 48,000 limit
The approval: which agent, for whom, who said yes, for this one order only.
Console: the audit chain with 204,856 records and 112 anchors, and the button to verify the whole chain
Every decision, on a record nobody can quietly change. Your auditor can check it for themselves.
Console: the agent register, with each agent's owner, sponsor, tools and whether it is still wanted
The list of agents: who owns each one, what it can reach, and when its owner last confirmed it is still needed.

How it works

Every AI action goes through one checkpoint.

Your AI agents go through Sigilant to reach your systems, instead of going straight in. Nothing has to be rebuilt.

Step 01

Check

Before anything happens, Sigilant checks it against your rules: which agent, for whom, doing what.

Yes, wait or no

Step 02

Approve

Big or risky actions wait for a named person to say yes. They see exactly what they are agreeing to.

A person decides

Step 03

Access

The AI never holds the keys to your systems. It is let in for one job, then the door locks.

Nothing to steal

Step 04

Record

Everything is written down, yes or no, on a record that shows if anyone changes it.

Proof, automatically

What you get

Eight things you can tell your board.

Each one is something Sigilant does, in words you can repeat.

Every agent is known

Each one has its own ID and a named owner.

Rules, every time

Every action is checked as it happens.

A person says yes

Big or risky actions wait for approval.

Only what it needs

No more than its job, or its person, allows.

No passwords

Let in for one job, then the door locks.

An off switch

Stop any agent at once, even halfway through.

Hard to trick

Nothing it reads can change your rules.

Proof anyone can check

A record nobody can quietly change.

One agent cut off at the gateway while another continues
The kill switch
A chain of sealed records anchored to a vault
The record

Modules

One platform. Add what you need.

Start with control over your AI agents. Add finding and testing, and the same control for plant and machinery.

Available

Sigilant

Control for AI agents

Every agent has an ID and an owner, follows your rules, waits for a person's yes on big actions, and can be switched off at once.

Available

BugXHunter

Find your AI, and keep testing

Finds the AI you did not know you had, then keeps testing your systems for weaknesses, every day and after every change. Its own testing agents work under Sigilant's rules too.

In development · design partners wanted

Sigilant OT

Control for plant and machinery

No AI agent can change a controller without your rules and a named engineer's yes. Safety systems are out of reach, always.

In development

BugXHunter OT

Test the plant without risking it

Only listens on live sites, does active testing in a lab, and makes a live check only when two people approve.

Deployment

Works with what you already have.

Your people log in the way they already do, with Okta, Auth0 or Microsoft Entra ID. Sigilant runs on your own systems, so your rules and your records stay with you.

  • IdentityWorks with your existing logins
  • AgentsWorks with the AI agents you already use
  • HostingRuns in your environment
  • FailureIf in doubt, it says no
  • CryptographyProtected against future code-breaking
  • EvidenceRecords nobody can quietly change

Bring one AI agent. We will show you.

In one hour, we will show Sigilant controlling it, on your systems, with your rules. You leave with the record.

Get in touch

Request a briefing.

Tell us which AI agents you want to use and what they need to reach. We will reply within one business day.