Private stays private
Files with passwords and keys are unreadable where agents work, and your keys never reach them.
The neutral control layer for teams of people and AI agents. Your business rules block what AI may not do, the right person decides the rest, and everything is recorded.
It might spend money it shouldn't.
Pay a vendor, refund a customer, sign up for a contract.
Preflight: spending waits for the people your rules name, and your rules can block it outright.
It might share something private.
Customer data, contracts, passwords, prices.
Preflight: rules on your data classes block it, and passwords and keys never reach the agent.
Nobody can say who allowed it.
Approvals scattered across chats and inboxes, or none at all.
Preflight: every plan, action, decision and result is kept until the flow is deleted, and no entry can be changed.
Each action the agent asks for is checked here before it runs.
An example flow in a team of people and agents. Every Monday the Procurement agent, running on Claude, checks the cloud contract, which renews in 21 days. It proposes 6 steps and Gemini reviews the plan as advice; the Ops lead approves. The agent reads three vendor quotes and the budget report written by the Finance agent on GPT, compares them and drafts a recommendation, all without asking anyone; its attempt to open the file with the payment passwords is blocked as a secret file. Creating the €18,400 purchase order with Northwind Cloud, a new vendor, is held by two team rules: over €10,000 needs the Finance Manager and the CFO, and new vendors need Legal. Preflight asks the Finance Manager by email, the CFO on Slack and Legal on Discord; each approves in Preflight, and the order is created. Every event is kept in the record.
Routine work runs on its own. The decisions your rules keep for people wait for them.
Write the rules your business already lives by. Preflight checks them before every action of every agent, on any model, and a blocked action never happens.
When an agent wants to spend money
and the vendor status is Blocked
block it
Acme Hosting is Blocked on your vendor list. The agent is told it isn’t allowed, and nothing is paid.
No AI decides whether a rule applies. Unknown values never pass.
When an agent wants to spend money and the refund amount is greater than €500, block it.
Blocked before it runsWhen an agent wants to send a message and the data classification is Highly sensitive, block it.
Blocked before it runsWhen an agent wants to spend money and the budget status is Failed, block it.
Blocked before it runsWhen an agent wants to write to a connected service and the customer’s country is one of RU, IR, KP, block it.
Blocked before it runsWhen an agent wants to send a message and the customer tier is Enterprise, block it.
Blocked before it runsWhen an agent wants to send a message and the legal review is not Passed, block it.
Blocked before it runsRules cover what agents do through Preflight and the tools you connect to it. Keep payment details and passwords out of the folders agents work in.
n8n connects to more than 1,000 apps, and to almost any other system through its API. Your agents run your n8n workflows through Preflight, so every run passes your rules: starting a workflow asks a person first, and a rule can block it.
Integrations as listed by n8n on n8n.io. Logos are trademarks of their owners and don't mean they endorse Preflight.
Approvals go to the job role that signs off. Silence never approves anything.
| Action | Create a purchase order · €18,400 · Northwind Cloud |
| Asked by | Procurement agent (Claude), step 4of a plan the Ops lead approved |
| Rules | Spending over €10,000 · New vendorsversions 4 and 2 |
| Evidence | €18,400 from the request · vendor Newnot on your vendor list |
| Decision | Approvedby the Finance Manager, Legal and the CFO |
| Result | Purchase order created |
If an action can't be recorded, it doesn't happen.
Inside the plan you approved, agents read, compare and draft without asking. Only what your rules keep for people waits for them.
Files with passwords and keys are unreadable where agents work, and your keys never reach them.
Notion, Supabase, n8n, Linear, Sentry, Resend, GitHub and Railway: every action an agent takes there is checked like any other.
Claude, OpenAI, Gemini or Grok, with your own keys or the subscriptions you already have.
Always-on agents start work on a schedule, like every Monday at 8:00, and follow the same rules at night.
Each piece of work knows what it cost. Set budgets per task, per day and per team.
Up to 3 AI models from different makers review a plan before you approve it. They advise; you decide.
On your own computer or in the cloud, in a closed space of their own. Your team chooses.
| Capability | An AI agent alone | One vendor's AI tool | Sign-off over chat or email | Preflight |
|---|---|---|---|---|
| Works with any AI model | — | One vendor | Yes | Yes |
| Your business rules on amounts, vendors, customers | — | Limited | — | Yes |
| Blocks an action before it happens | — | Partial | — | Yes |
| Approval by job role | — | — | Whoever answers | Yes |
| A record whose entries can’t be changed | — | Partial | Scattered | Yes |
No. It controls agents. They can think with Claude, OpenAI, Gemini or Grok; Preflight decides what they may do.
No. Inside the plan you approved, agents work alone. Only what your rules keep for people, and risky or unexpected actions, ask.
No. Rules are checked by plain code, the same way every time.
Yes. A rule names what an agent wants to do (spend money, send a message, change your data…) and the values that matter (amount, vendor, customer, country, data class, time), then blocks it, asks a person, or requires 1 to 3 job roles. It’s checked before the action happens, so a blocked action never happens.
Only the people your rules name, by job role: the Finance Manager, the CFO, Legal. Each is told on their own channel, email, Slack or Discord, and decides in Preflight.
Notion, Supabase, n8n, Linear, Sentry, Resend, GitHub and Railway, each with your own account. Every action there is checked like any other.
Files with passwords and keys are unreadable where agents work, and your keys never reach them. Your rules can block sending anything you classify as confidential.
No. Your team's content is used only to run the service, and it's encrypted with your team's own key.
Yes. Every plan, action, decision and result is kept until the flow is deleted, or until your team's retention period ends if it set one. No entry in the record can be changed.
We're opening Preflight to a small number of software teams first. Leave your work email and we'll write when there's a place for you.