Skip to main content

​
What is Gaia Autopilot?

Gaia Autopilot is autonomous. It runs on its own. It watches data against objectives Gainable infers from your app, drafts work when something needs attention, and lands that work in your inbox for you to approve, edit, or skip. Internally, Autopilot is a fleet of small, scope-bounded agents (one per objective). The umbrella, the inbox, the activity feed, and the playbook editor are all Autopilot. If Gaia Copilot is “the user asks, the Copilot answers,” Autopilot is “work shows up before anyone asks.” Two halves of the same intelligence layer. The Copilot is reactive. Autopilot is proactive.
Apps that work for you, not apps you work with. Autopilot does the thinking in the background. You stay in control through the inbox. Draft-and-approve is the default, so nothing leaves the building until you say so.

​
Test for which one applies

Does the user have to ask first?
  • Yes → Gaia Copilot
  • No (work shows up before they ask) → Gaia Autopilot

​
What Autopilot does

Watches data

Subscribes to change streams, schedules, webhooks, and explicit clicks. Reacts when something matches.

Maintains objectives

Inferred goals like “every claim resolved in 14 days” or “follow up on stalled deals.”

Drafts work

Composes emails, Slack messages, status updates, summaries, and SLA escalations.

Lands in the inbox

Drafts arrive in the Autopilot inbox with full reasoning, ready for one-click approve, edit, or skip.

​
How Autopilot comes to life

Every Gainable app moves through a five-phase build contract:
The autopilot phase is where agents are inferred from your schema and intent. Gainable reads your data model, looks at how the app is shaped, and proposes objectives, playbooks, tools, and risk tiers. You review the autonomy contract, edit it, and ship.
1

Data is connected

Datasets and data models give Gainable the schema to work with.
2

UI is built

Tables, forms, dashboards, and the Autopilot inbox are added to the app.
3

Autopilot is inferred

Gaia proposes objectives (“keep claims moving”), playbooks (“nudge after 7 days idle”), tools (“send_email”), and risk tiers (“draft, don’t auto-send”).
4

You approve the contract

Edit anything you want. Disable any objective. Tighten the risk posture.
5

Autopilot goes live

The runtime starts watching change streams, schedules, and webhooks. Drafts begin landing in the inbox.

​
Two scopes

Each agent runs in one of two scopes. The difference matters for permissions and visibility. See scopes for the full boundary rules.

​
What Autopilot does not do

Autopilot is not a magic wand. By default it:
  • Doesn’t send anything to a customer without approval
  • Doesn’t take destructive write actions without explicit graduation
  • Doesn’t run outside the risk tier you signed off on
  • Doesn’t see data the configured scope doesn’t allow
All of this is enforced by the risk tiers and tool registry, not by hope.

​
Autopilot at a glance

​
Prompt examples

You can describe Autopilot agents in natural language:

​
Learn more

Objectives

What agents are trying to maintain

Playbooks

Trigger, steps, and guardrails

Triggers

Schedule, data change, webhook, user-triggered

Tools

The fixed tool registry

Risk tiers

Draft-and-approve by default

Inbox

Where drafts land

Recipes

Worked examples of common playbooks

Gaia Copilot

Looking for the conversational side?