Join the waitlist
Capture & fix · Autopilot

It works the night shift.You set the rules.

Decide what Tore may pick up on its own, area by area. While your team is away it answers, investigates and drafts fixes inside the limits you set, and hands anything risky or uncertain to a person.

Join the waitlistSee how you set it

Tore opens soon. Join the waitlist and we'll email you the day you can start.

app.tore.ai/beacon-data/autopilot
Example data

Example: Beacon Data's inbox overnight, with the team away and Autopilot on. Between midnight and 5am Tore answers three questions on its own, investigates an error from Sentry, matches Priya's report that exports stop at 1,000 rows to it and drafts a fix with tests, prepared as pull request 482 and waiting for Alex's approval. A double charge goes to Hana because billing always goes to a person, and a question Tore isn't confident about goes to Lena. At 8am Alex gets a morning report: two conversations and one fix need him.

The safe work gets done.The risky work waits for you.

Autopilot is where you decide what Tore may pick up without asking, in numbers you can read before you turn it on. Everything else queues quietly for a person.

The night queue gets worked

Questions you allowed get answered and errors get investigated while your team is asleep.

a full queue waiting every morning

Noise never starts work

Thresholds and an ignore list filter errors before Tore acts on any of them.

reacting to every alert at 2am

It can't run away

Hourly and daily action limits, a budget, and a switch that stops everything at once.

babysitting the automation

Trust grows area by area

Start an area on observe and turn it up once you like what it does.

all-or-nothing automation

Autonomy you can readbefore you turn it on.

Rules

Choose what it may do alone, per area.

Write rules per source, project and environment, checked in the order you set. Each one says how far Tore may go on its own: answer, investigate, draft a fix, or only watch. The autonomy levels and approval rungs are the same ones you set on Fixes and approvals.

  • Rules per source, project and environment, in your order
  • Waits for five occurrences and an hour before acting on an error, and you move both
  • An ignore list for noise, an always-escalate list for what matters
  • An area's setting can only be tighter than the default, never looser
settings · autopilot rules
Example data
Autopilot ruleschecked top to bottom
1
How-to and plan questionswidgetemailall products
answer alone
2
Sentry errorsbeacon/webproductionafter 5 events, 1h
auto-draft a fix
3
Sentry errorsbeacon/apistaging
observe only
4
Anything touching billingevery sourcelocked risk class
a person
Ignore listResizeObserver loopChunkLoadErrorbot traffic
Always escalate/api/auth/*Acme Corp

The morning report

Wake up to what it did, not a pile.

Everything Tore took on by itself is accounted for, with who did the work: resolved by AI, AI-assisted or a person. The day starts with the few things that need you, not the whole night's queue.

  • Every resolution attributed: AI, AI-assisted or a person
  • Fixes it drafted wait for your engineer's approval by default
  • Handed-over conversations arrive with the full history
autopilot · morning report
Example data
While you were awayBeacon Data · 11:40pm to 8:00am
3 need you
Answered on its ownhow-to, plans, password resets
14
Errors investigated3 Sentry issues, root cause found in 2
3
Fix drafted, waiting for AlexPR #482 · export stops at 1,000 rows
1
Handed to a personbilling to Hana · not sure to Lena
2
Skipped by your ignore listResizeObserver loop, bot traffic
9
Who resolved what19 conversations closed
AI resolved 14AI-assisted 3Person 2

Limits

Budgets, limits and a stop switch.

Tore works inside numbers you set: automatic actions per hour and per day, and a budget for AI spend. The stop switch doesn't just pause new work, it ends what is already running.

  • Ten automatic actions an hour and fifty a day, and you move both
  • A budget and cap on AI spend; at zero, support keeps working
  • One switch ends work already in flight, not just new work
autopilot · limits
Example data
Automatic actions this hour7 of 10
Automatic actions today31 of 50
AI budget this month41% used
Autopilotrunning · 2 jobs in flight
Stopped by Alex8:14am · running work ended
INV-812Null guard on the export cursorrunningended
INV-813Retry a flaky webhook deliveryrunningended
INV-814Slow search on big workspacesqueuednot started
Inbox, widget and help center keep working

Handing over

It knows when to hand over.

When it isn't confident, Tore hands the conversation to a person with everything it found, instead of guessing. And anything touching the six locked risk classes goes to a person, whatever your rules say.

  • Hands over below the confidence bar you set, with the full conversation
  • Choose how hard it tries before involving a person
  • Auth, billing, migrations, personal data, tenant isolation and secrets always go to a person
autopilot · handovers
Example data
A
Ava · Lumen Labs"Dashboard numbers look off since Tuesday"
Confidence 58%your bar: 80%
Below your bar. Handed to Lena with the conversation and the three things it already checked.
O
Omar · Quillstack"We were charged twice in March"
Billing is a locked risk class. Sent to Hana, whatever rule 1 says.

Before involving a person

Hand over earlyBalancedTry harder

Your team can step inat any point.

Autopilot never locks you out. Take over a conversation mid-reply, ask for changes on a fix in plain words, or correct an answer so Tore gets it right next time.

inbox · Ava, Lumen Labs
Example data
A
Ava · Lumen LabsDashboard numbers look off since Tuesday
Take overLena has it
Since Tuesday our weekly totals on the dashboard are lower than the CSV export. Which one is right?
Tore AI · draft, not sentThanks Ava. I'm checking your timezone setting and the last import.
Internal note · Tore stepped backChecked so far: workspace timezone is UTC, Tuesday's import finished, dashboard cache is 6h old. Ava never sees this note.
Lena · supportHi Ava, the export is right. The dashboard was showing a cached week; I've refreshed it and your totals now match.

Tune it

Rules per source and environment 4 rulesAutomatic actions 10 an hour, 50 a dayHand over below 80% confidence
All AI controls →
4autonomy levels, from observe to verify on staging
5 + 1hoccurrences and wait before it acts on an error, and you move both
10 / 50automatic actions an hour and a day, until you change them
1switch that ends work already running

Keep exploring.

Capture & fixFixes and approvalsThe autonomy dial, approval rungs and the six locked risk classes.See how → Capture & fixError monitoringWhere overnight work starts: errors grouped by fingerprint.See how → PlatformAI controls and spendBudgets, caps and what every AI action costs, per product.See how →

Let it work the night shift.Wake up to a report.

Start every area on observe, read what it would have done, then turn it up one area at a time.

You're on the list. We'll email you the day you can start.

Get early access when Tore opens. No spam.