yae Start a pilot

Put AI to work.
Keep control.

yae sits between the AI your business uses and the systems it works in. You decide what each AI can see, what it can do, and when a person has to approve. yae checks every action before it runs, and keeps the record.

Start a pilot
Works with Claude · Gemini, through MCP + your own agents
AIfinance-copilot ACTIVE
ACTIONS4 of 23
invoices.readAccounting✓ Allowed
email.draftEmail✓ Allowed
payment.createAccounting! Approval
payroll.readFiles× Never
19 actions not granted / off
RULES
→ Payments need a person to approve. → Never delete customer records.
SYSTEMS IT CAN REACH
email ✓ files ✓ accounting · ask payroll ×
THIS WEEK 212 allowed 6 approved 2 blocked

Bring the AI you already use, through MCP or an API

Claude Gemini Your own agents MCP apps Any system with an API
Supported by Google for Startups Cloud Program

Your AI can act. Who decides what it’s allowed to do?

Teams already use AI with customer and company data, and agents are starting to send, pay and change things. Access is usually all or nothing, and afterwards nobody can say who allowed what. yae gives every AI action one of three answers.

✓ Allowed Runs straight away, and it’s on the record
! Needs a person Waits until the right person approves that exact action
× Blocked Never happens, and the attempt is recorded
EXAMPLE · ACCOUNTING

A R12,000 payment, checked before it runs

Finance Copilot may read invoices on its own, but every payment needs a person to approve it. Here’s what happens when it tries to pay a supplier R12,000.

See how approvals work →
14:34Finance Copilot asks to pay Cape Components R12,000 from your accounting system.
14:34yae pauses it: payments need a person to approve.
14:37Marley sees the exact payment and approves it.
14:37The payment is made with a one-time authorisation for exactly that amount and supplier. Recorded.
AIsupport-agent RULES · V3

✓ CAN

Read support tickets and order history
Draft replies to customers

! NEEDS APPROVAL

Issue refundssupport lead
Email customers directlya manager

× NEVER

Delete customer records
Change its own rules
ADMINS Sarah · owner Marley · director

Clear rules

Give each AI exactly the access it needs, nothing more

Most AI gets far more access than it uses. With yae you set what each AI can do, what needs a person, and what it must never do. Anything you haven’t allowed is blocked, and you see exactly what changed before a new version goes live.

  • Can, needs approval and never, set for each AI
  • Choose which actions, on which systems, need a person
  • Only admins can change rules, and every change is recorded
YOUR RULES
canevery AI
needs approvalevery AI
neverevery AI
yaeCHECKS EVERY ACTION
YOUR AI
MCP apps
Claude
Gemini
Your own agents

Bring your own AI

One set of rules for every AI you use

People switch between AI assistants like Claude and Gemini, and teams build their own agents. yae isn’t another AI. It sits beneath all of them, so the same rules apply whichever AI is asking. Before an AI acts, it asks yae. It can’t vouch for itself.

  • No lock-in. Change AI providers without rewriting a single rule.
  • Set once. A rule you write applies to every AI that can reach that system.
  • Agents too. Your own agents and workflows check with yae the same way.

Systems and data

Connect the systems your AI works in

Connect the systems your AI touches and choose exactly which actions it may ask for. yae holds the keys, so an AI can’t reach a connected system without going through yae. Systems that support it also check yae’s one-time authorisation for each action.

  • Any system with a web API: helpdesk, CRM, records or your own services
  • yae holds the credentials, so your AI never sees them
  • Each connection lists the exact actions AI may ask for
CONNECTED SYSTEMS ACTIONS
Helpdesk4 actionsCONNECTED
CRM3 actionsCONNECTED
Records4 actionsCONNECTED
Accounting3 actionsPROTECTED
Payroll1 actionPROTECTED
+ connect any system with an API
× Blocked. Support Agent tried to delete a customer record. That’s never allowed.
YOUR AI 5 connected · 2 people approving
finance-copilotClaude · finance team● ACTIVE · 3 SYSTEMS
support-agentYour own agent · support team● ACTIVE · 4 SYSTEMS
sales-assistantClaude · sales team● ACTIVE · 2 SYSTEMS
research-helperGemini · research team● ACTIVE · 1 SYSTEM
invoice-workflowYour own workflow · finance team● PAUSED BY MARLEY
+ connect an AI

One place for all your AI

See every AI in your business, and stop any of them

Know which AIs are connected, which team they belong to and what they can reach. See exactly what a rule change adds or removes before it goes live, and stop any AI the moment something looks wrong.

  • Every connected AI, its owner and its systems in one list
  • See exactly what a rule change adds or removes before it goes live
  • Stop an AI in one step; it stays stopped until an admin lets it back in

Approvals

A person approves the exact action

Not blanket access for the afternoon. The approver sees exactly what will happen, and only that happens.

01The AI asksWhen your rules say an action needs a person, yae holds it before anything happens.
02The right person decidesThey see the exact action and its details, the system and the rule that applied.
03Only that action runsyae issues a one-time authorisation for it. Change anything and it needs a new approval.
AIfinance-copilot ! Needs your approval

Pay Cape Components R12,000

SystemAccounting ReasonInvoice #4883 RulePayments need a person to approve Asked byFinance Copilot Expires in4h 56m

Covers this exact payment only.

Evidence

Know what every AI did, and why

Every request, decision, approval and outcome is recorded. Calm and readable day to day, with the full detail there when you need to prove what happened.

01Every request is recordedWhich AI asked, what it wanted to do, and in which system.
02Every decision has a reasonThe rule that applied, and who approved or rejected it.
03Changes to the record showThe trail is tamper-evident. If an entry is altered, you can tell.
ACTIVITY · TODAY All AIs
finance-copilot read 32 invoicesAllowed09:12
support-agent drafted 14 customer repliesAllowed11:40
finance-copilot paid Cape Components R12,000Approved by Marley · one-time authorisation14:37
support-agent tried to send client records to another AI providerBlocked · never allowed15:02
Recorded · tamper-evident Open full record →

Connect your way

Works where your AI already runs

yae doesn’t replace your AI or rebuild your workflows. It sits at the step where an AI is about to do something, however that AI is built. Start with one action and grow from there.

MCP For AI apps and agents that support MCP. yae is the step they go through before they act.
API One call at the sensitive step of your own agent or app. The rest of your code stays as it is.
Workflow tools Automation tools that can call an API add yae as a step, before the step that sends, pays or changes something.

Security

Built to hold when things go wrong

Most tools assume everything works. yae is designed for the day it doesn’t: an outage, a misbehaving AI, a missed payment.

Fails closed One-time authorisations Tamper-evident record
Security & trust →
Never fails open If yae can’t confirm an action is allowed, it doesn’t happen. Protected actions wait rather than run unchecked.
Safety only tightens Stopping or restricting an AI is instant. Giving one more power always takes an admin.
Billing never controls authority If a payment on your account fails, your rules stay on. Your AI never runs unrestricted because of a billing problem.
An AI can’t vouch for itself It can ask. It can’t approve its own request or change its own rules.

Give AI access. Keep the authority.

Start with one team and one real workflow. Tell us which AI you use and what it should never do without asking, and we’ll set yae up with you.

Start a pilot