Detect problems before they snowball
Catch stopped automations, unexpected changes, and unusual activity before they disrupt your work.
See what changed in Airtable, catch unusual activity,
and understand how your workflows perform over time.
Your changelog lives in your own database.

Catch stopped automations, unexpected changes, and unusual activity before they disrupt your work.
Follow what changes in your Airtable base. Reports and trends help you see what needs your attention.
Understand how work moves across records and tables. Improve your automations and provide helpful context to AI agents.
Connect Airtable once. Orloi automatically records each change into a structured history that is compared, explained, and understood over time.
Ask Orloi what happened across your records, then follow the trail from the first signal to the downstream changes.
An Airtable account with access to the base you want to observe and a Postgres database. Connect both, choose the tables and fields to include, then activate Orloi. AI reports are optional.
Yes. Orloi stores your captured history, reports, metrics, and findings in the Postgres database you connect. We recommend a database dedicated to Orloi; it can be part of your existing provider setup.
You can create a Postgres database in a few clicks with Supabase or Neon, both of which offer free plans to get started.
No. Orloi observes activity in the tables and fields you select. It can't write changes back to Airtable.
No. Capture starts when you activate Orloi and covers new activity within your selected tables and fields. It does not reconstruct earlier history.
Only when you enable an AI feature. Activity and metrics work without AI, and reports are off by default. If you enable AI, Orloi sends the context needed for that feature to the provider you choose.
Recording starts at activation. Changes appear in Activity after capture and processing, rather than instantly. Reports follow the schedule you enable; trends and process maps develop as enough activity accumulates.
For setup details and data handling, see the setup guide and data and privacy guide.
Recording starts immediately, then richer reports,
maps, and alerts emerge as patterns form.
Day 0
Day 1
Day 3-4
First Monday
Day 10-11
Day 14
Start building operational memory and uncover patterns as your base evolves.