> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/readme.md).

# Introduction

![](/files/15STeyw0mrH5c6QFrblB)

AI writes code faster than teams can review, merge, and release it. The bottleneck moved — from typing the change to everything that happens after.

Aviator is a suite of building blocks for that *everything-after*: capturing intent, verifying behavior, queuing safe merges, coordinating releases, and routing reviewer attention to where it matters. Some pieces are open and free, designed to drop in beside what you already use. The rest are the power tools we build for teams pushing thousands of PRs a day.

## Getting started — free tools

Two entry points. Adopt them in isolation; combine when you're ready.

<table data-card-size="large" data-column-title-hidden data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>Inbox</h4></td><td>One feed for every change that needs your attention — across every repo. Stops the polling-Slack-and-GitHub-notifications habit and replaces it with a single ranked queue.</td><td></td><td><a href="/pages/cdRRYKA7T3Mz8STnKHQI">/pages/cdRRYKA7T3Mz8STnKHQI</a></td></tr><tr><td><h4>Stacked PRs CLI</h4></td><td>An open-source CLI for managing stacked PRs natively in GitHub. Smaller, focused reviews; cleaner history; no extra hosting.</td><td></td><td><a href="/pages/ylZefdDmSp7omt3SgJoZ">/pages/ylZefdDmSp7omt3SgJoZ</a></td></tr></tbody></table>

## Power tools

Four products that compound on each other once you're shipping at scale.

<table data-card-size="large" data-column-title-hidden data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>Verify</h4></td><td>Capture the intent for every change and verify the running code against it before merge. Deterministic guardrails for AI-generated code — catches the slop that diff review misses.</td><td></td><td><a href="/pages/JjM4YfnStrk7xzBdxUrR">/pages/JjM4YfnStrk7xzBdxUrR</a></td></tr><tr><td><h4>MergeQueue</h4></td><td>The most popular and most scalable merge queue in the industry. In production at Figma, DoorDash, Notion, Meta, and others — tens of thousands of PRs through the queue every day.</td><td></td><td><a href="/pages/g5wtKxOBFem6y5iZEBGZ">/pages/g5wtKxOBFem6y5iZEBGZ</a></td></tr><tr><td><h4>Releases</h4></td><td>One dashboard for deployments, rollbacks, and cherry-picks across every environment. Replaces the spreadsheet-and-Slack release ritual with a single source of truth.</td><td></td><td><a href="/pages/P0eU9BLUbW60pnfDTwK6">/pages/P0eU9BLUbW60pnfDTwK6</a></td></tr><tr><td><h4>Runbooks</h4></td><td>Multiplayer AI coding with standardized playbooks. Your team's repeatable work — refactors, migrations, upgrades — turned into agentic runbooks anyone can launch.</td><td></td><td><a href="/pages/GUH1AzgC7aRs0QtEoSB2">/pages/GUH1AzgC7aRs0QtEoSB2</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aviator.co/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.