---
title: "Overview"
summary: "What Gyre is, where it sits in a design-optimization stack, how it is put together, and what it does not do."
section: overview
order: 0
level: 1
keywords: [overview]
---
<!-- gyre docs: expanded Markdown of overview/index.md (generated tables, verification numbers and chart data are written out). Base level of this page: L1 Essentials; passages at another level are bracketed by 'begin level N' / 'end level N' comments and start with [LN Name]. Built from revision ceb1f4b0be. -->

Start here. These pages explain the purpose of the project in plain terms, show how a request travels from an interface to the numerical core and back, and state the limits of the current capability.

- [What Gyre is](what-is-gyre.md) (L1 Essentials): Gyre is a differentiable high-order flow solver delivered as a service. It gives a design-optimization framework what it needs from an aerodynamics discipline — converged flows, outputs, coupling fields and exact derivatives — and deliberately nothing more.
- [Architecture at a glance](architecture.md) (L1 Essentials): A case specification flows through one pipeline — mesh, discretization, discipline — that every interface shares. The service wraps that pipeline in isolated worker processes and exposes it to programs, people and agents.
- [Capabilities and limits](capabilities-and-limits.md) (L1 Essentials): What Gyre does, how well each part is verified, and what it does not do yet. Read this before planning work on top of it.