Orloi overview ​

Orloi turns Airtable activity into operational memory.

Connect your Airtable base once. Orloi follows what changes, translates activity into readable business events, and stores that history in your Postgres database.

Most Airtable bases show what exists now. Orloi helps answer what changed, what keeps repeating, what is slowing down, and what deserves attention.

How it works ​

text
Airtable base
  ↓
Orloi capture and processing service
  ↓
Your Postgres database, orloi schema
  ↓
Dashboard, SQL, BI tools, and AI agents

For more detail, see How Orloi works.

Setup flow ​

  1. Connect Airtable.
  2. Select the base Orloi should observe.
  3. Connect an external Postgres destination.
  4. Let Orloi install its objects in the dedicated orloi schema.
  5. Activate the engine.
  6. Use the default dashboard, query Postgres directly, or connect your own tools.

Orloi only starts capture after the Postgres destination has been installed and verified.

For setup details, see Setup.

What to decide before setup ​

  • Which Airtable base should be watched.
  • Which tables are in scope.
  • Whether any fields should be included or excluded.
  • Which Postgres database should receive the history.
  • Who should be allowed to query the resulting changelog data.
  • Whether AI-derived reports and summaries should be enabled.

Capture starts at activation ​

Orloi captures new changes after activation. It does not backfill previous Airtable history by default.

At first, Orloi gives you fresh change visibility. As history accumulates, it can show patterns, repeated work, metrics, and process signals.

What you get immediately ​

The first output is a durable, readable changelog: records created, statuses changed, owners assigned, prices updated, bookings moved, tasks completed, and other in-scope activity.

In the first day, use Orloi mainly for freshness, recent activity, and confirming that capture is healthy.

What improves with history ​

After the first week or two, Orloi has enough activity to show early patterns: active tables, repeated manual edits, common status movement, and workflow friction.

After a month or more, reports, metrics, comparisons, and process summaries become more useful because they have prior windows to compare against.

What Orloi does not do ​

  • Orloi does not write back to Airtable.
  • Orloi does not modify your existing Postgres schemas.
  • Orloi does not backfill historical Airtable activity by default.
  • Orloi does not require AI for the core changelog.
  • Orloi is not intended for employee scoring, HR decisions, or workforce surveillance.

Where to go next ​

Most teams should open the Dashboard first.

As history accumulates, Orloi can surface higher-level views: daily reports, weekly reports, activity metrics, dashboard cards, process summaries, and AI-agent context.