What Is Pilot?

The Short Version

Pilot reads your documents and works from them. You upload PDFs, Word files, research papers, old articles — whatever your organization has produced. Pilot organizes that material into a knowledge base by topic, then produces content drawn entirely from what you gave it. Every sentence traces back to a specific source document. You review everything before it goes live.

That's it. No prompt engineering. No copying text into a chat window. No wondering where the AI got its information. You upload your knowledge, configure how you want Pilot to communicate, and it produces cited, deployable content from your own material.

What Pilot Actually Does

Think of Pilot as a three-step loop:

Upload your documents. PDFs, Word docs, markdown files, HTML, plain text. Pilot accepts whatever format your knowledge lives in. These become source documents in your knowledge base — the foundation everything else builds from.

Configure your voice. Pilot doesn't have a default writing style. You set the tone: formal or conversational, concise or expansive, heavily cited or lightly sourced. Different audiences need different voices, and Pilot supports multiple voice configurations for different channels. A client newsletter doesn't sound like an internal research brief — and it shouldn't.

Generate and deploy. Pilot produces content from your knowledge base in your configured voice. You review it, edit if you want, and deploy to your channels — your website, your documentation site, your CMS, your newsletter, your social accounts. Pilot adapts the format for each surface.

This loop runs continuously. As you add new documents, Pilot identifies new topics and surfaces new content opportunities through Pilot Lights. Your knowledge base grows, and Pilot's ability to produce from it grows with it.

Three Output Modes

The same knowledge base and the same five-step workflow power every kind of output Pilot produces:

Articles and editorial content. Pilot writes cited articles, newsletters, and social posts from your knowledge base. This is the primary use case for publishers, research organizations, and knowledge businesses. You review drafts, then publish to web, CMS, email, or social channels.

Documentation. Pilot can power full documentation sites — structured, navigable, always current. Upload your source material, configure a precise voice, and Pilot produces documentation that stays grounded in what you actually wrote. Pilot Docs is a working example: the entire site is powered by Pilot's knowledge base and headless API.

Knowledge portals via Ask. The Ask feature lets anyone query your knowledge base directly and get cited, conversational answers. Embed it on your site, in your docs, or anywhere your audience needs access to what you know. Every answer traces to source documents, just like every article.

What Pilot Is Not

Pilot is not a chatbot. Chatbots answer questions in conversation. Pilot writes publishable articles, powers documentation sites, and provides cited answers through Ask. The output isn't a chat response — it's content your audience reads on your website, in your docs, or in their inbox.

Pilot is not a writing assistant. Tools like Jasper or ChatGPT wait for you to tell them what to write and how to write it. Pilot already knows what you know (because you uploaded it) and already knows how you want to sound (because you configured it). It identifies what to write and drafts it. You review instead of author.

Pilot is not a search engine. Pilot doesn't search the internet. It doesn't pull from training data or web results. Everything it produces draws from your documents and only your documents. If it's not in your knowledge base, Pilot doesn't write about it.

The Citation Model

This is the part that matters most. Every sentence Pilot writes traces to a specific source document you uploaded. Not "this was generated by AI" — but "this claim comes from page 14 of your Q3 market analysis, and this one comes from your 2024 whitepaper."

Citations appear inline as superscript numbers linking to a sources section. Readers can verify any claim. Editors can trace any statement back to the original material. This isn't AI-generated content in the way most people use that phrase — it's sourced, attributable content that happens to be assembled by a machine instead of a person.

For more on how this works, see Citations and Provenance.

Who Pilot Is For

Pilot works best for organizations that have substantial existing knowledge but limited capacity to turn that knowledge into accessible content.

Publishers and media companies sitting on years of archived reporting that could fuel new articles. See Pilot for Publishers.

Research organizations producing valuable work that never reaches the audiences who need it. See Pilot for Research Organizations.

Knowledge businesses — consulting firms, law firms, financial advisors — whose expertise lives locked in internal documents. See Pilot for Knowledge Businesses.

Documentation teams — product teams, developer relations, technical writers — who need to keep docs accurate, consistent, and grounded in source material. See Pilot for Documentation Teams.

The common thread: you already have the knowledge. You just don't have enough people or hours to turn it all into content. Pilot closes that gap.

A Wisdom Engine

The ideas behind Pilot draw from David Habib's Latent Vector, which argues that organizations sit on vast reserves of latent knowledge — knowledge that exists in documents and institutional memory but never reaches the people who could use it. Pilot is built to surface that latent knowledge as working content.

The term for what Pilot does is a wisdom engine: a system that doesn't just store or retrieve information, but exercises editorial judgment about what knowledge matters for a given audience and context. For more on this concept, see What Is a Wisdom Engine?

Getting Started

Pilot is in open beta. You can sign up, upload your first documents, and generate your first article in about ten minutes. See the Getting Started guide for a walkthrough, or visit Open Beta for details on what's included.

---

Updated 2026-03-17: This document now reflects the streamlined document update API (preserveStatus).