Questions, answered.

No. A copilot autocompletes inside your editor. Avion is a company — an org chart of specialists that plans, builds, reviews, QAs, ships, and remembers. You set the outcome; the company owns execution end to end.

Six departments and twenty roles: Executive (CEO is you, plus a CTO), Product, Engineering, Quality, Operations, and Growth. Every role is a long-term hire with its own identity, responsibilities, memory, and definition of done.

Yes. Work happens on your real repositories and lands as real pull requests — with numbers — not in a throwaway sandbox. Planning is grounded in your repository intelligence before anything is written.

Your outcome moves through ten stages: outcome, repo analysis, plan, tasks, build, review, QA, deploy, docs, done. Product drafts the plan, the tech lead breaks it into tasks, an engineer opens a PR, and Quality gates it — all the way to merged.

At the Autonomous level, yes — a single request can be planned and driven to a merged, reviewed, QA'd pull request hands-off. At lower levels it pauses for your approval. The same code path runs in every mode; only the checkpoints change.

Every plan draft is validated against quality and grounding gates, with a deterministic fallback. It reads your repository and the company's accumulated memory, and it is never allowed to invent work.

Five levels: Manual (observes and remembers), Suggest (proposes, never acts), Assist (opens PRs, pauses for you), Delegate (escalates the exceptions), and Autonomous (outcome to done, hands-off). You decide how much rope to give, per project.

Guardrails never switch off. Protected paths stay protected, protected branches stay protected, and force-pushes are never allowed — at every autonomy level. To date there have been zero guardrail bypasses.

The Quality department: a Reviewer, QA, and Security role gate every change. Acceptance tests must pass and gates must be green before anything is marked done.

Platform v2 is live and running end-to-end on real repositories, with 19 of 20 milestones at 100% and roughly 1,350 tests across ~72 files. Reach out via the contact page to talk about access.

Memory is layered — employee, team, company, repository, feature, and conversation. Lessons captured from reviews and releases are promoted into company standards and fed back into planning, so the company improves the longer it works for you.