Any agent.
Any model.
Your rules.

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.

  • For any AI agent, on any model
  • For any business with rules AI must follow
  • For a record you can show an auditor
The problem

Agents are fast.
Mistakes are faster.

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.

How it works

Agents do the routine work.
People make the calls that matter.

Renew the cloud contract · always-on agent · OperationsWaiting for work
Record0
  1. Nothing yet. Nothing runs before the plan is approved.

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.

  • People and agents, one team
  • Any agent, any model
  • Rules on amounts and vendors
  • Approval by job role
  • Told on email, Slack or Discord
  • Everything recorded
Rules, not guesses

Your business rules block AI actions.
Checked by code, every time.

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.

Team rules · checked on every action, by every agent, on any model

When an agent wants to spend money
and the vendor status is Blocked

block it

Try it: what the agent asks for
Result
Blocked

Acme Hosting is Blocked on your vendor list. The agent is told it isn’t allowed, and nothing is paid.

action
spend money
vendor
Acme Hosting
status
Blocked · your vendor list
rule
v2 · block it

No AI decides whether a rule applies. Unknown values never pass.

Rules can check

  • Block it, or require 1 to 3 roles
  • Amounts and currencies
  • Vendors and customers
  • Data classification
  • Environments
  • Files, commands, services, time

Rules for any business

  • Online shop

    When an agent wants to spend money and the refund amount is greater than €500, block it.

    Blocked before it runs
  • Clinic

    When an agent wants to send a message and the data classification is Highly sensitive, block it.

    Blocked before it runs
  • Finance team

    When an agent wants to spend money and the budget status is Failed, block it.

    Blocked before it runs
  • Trading company

    When 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 runs
  • Agency

    When an agent wants to send a message and the customer tier is Enterprise, block it.

    Blocked before it runs
  • Law firm

    When an agent wants to send a message and the legal review is not Passed, block it.

    Blocked before it runs

Rules 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.

Your tools

Connect to almost everything.
Through n8n, under your rules.

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.

  1. AgentAny model
  2. PreflightYour rules
  3. n8nYour workflows
  4. Your apps1,000+
  • Salesforce
  • SAPthrough its API
  • HubSpot
  • Stripe
  • Shopify
  • QuickBooks
  • Xero
  • Zendesk
  • Google Sheets
  • Jira
  • 1,000+more apps
  • APIanything with one

Integrations as listed by n8n on n8n.io. Logos are trademarks of their owners and don't mean they endorse Preflight.

People and agents, one team

The right person decides.
Only they are told.

Approvals go to the job role that signs off. Silence never approves anything.

Features

  • 1 to 3 job roles per rule
  • One inbox for every decision
  • Told by email, Slack or Discord
  • Reminders on your team's hours
  • Agents that keep working
The record

Every action, who approved it, and why.
No entry can be changed.

If an action can't be recorded, it doesn't happen.

Designed so that

  • No entry in the record can be changed
  • Each team has its own encryption key
  • Your content is never used for training
  • Every rule version is kept
Built in

Approvals only when they matter.
Everything else just runs.

Routine work runs on its own

Inside the plan you approved, agents read, compare and draft without asking. Only what your rules keep for people waits for them.

  • Read the three vendor quotesRan on its own
  • Draft the recommendationRan on its own
  • Create the €18,400 purchase orderFinance Manager + CFO

Private stays private

Files with passwords and keys are unreadable where agents work, and your keys never reach them.

Your tools, same rules

Notion, Supabase, n8n, Linear, Sentry, Resend, GitHub and Railway: every action an agent takes there is checked like any other.

Use the AI you already pay for

Claude, OpenAI, Gemini or Grok, with your own keys or the subscriptions you already have.

ClaudeOpenAIGeminiGrok

Agents that keep working

Always-on agents start work on a schedule, like every Monday at 8:00, and follow the same rules at night.

AI spend under control

Each piece of work knows what it cost. Set budgets per task, per day and per team.

A second opinion

Up to 3 AI models from different makers review a plan before you approve it. They advise; you decide.

Where agents work

On your own computer or in the cloud, in a closed space of their own. Your team chooses.

Neutral

AI does the work. Your rules decide what it may do.

CapabilityAn AI agent aloneOne vendor's AI toolSign-off over chat or emailPreflight
Works with any AI model—One vendorYesYes
Your business rules on amounts, vendors, customers—Limited—Yes
Blocks an action before it happens—Partial—Yes
Approval by job role——Whoever answersYes
A record whose entries can’t be changed—PartialScatteredYes
Questions

What people ask first.

Is Preflight an AI agent?

No. It controls agents. They can think with Claude, OpenAI, Gemini or Grok; Preflight decides what they may do.

Do I have to approve everything?

No. Inside the plan you approved, agents work alone. Only what your rules keep for people, and risky or unexpected actions, ask.

Does an AI decide whether my rules apply?

No. Rules are checked by plain code, the same way every time.

Can my business rules stop an AI agent?

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.

Who gets asked, and how?

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.

Which tools can agents use?

Notion, Supabase, n8n, Linear, Sentry, Resend, GitHub and Railway, each with your own account. Every action there is checked like any other.

Can agents see our private data?

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.

Is our data used for training?

No. Your team's content is used only to run the service, and it's encrypted with your team's own key.

Can we see what happened afterwards?

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.

Agents propose.
People approve.

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.