Infrastructure · llms.txt file breakdown
Fly.io organizes Fly.io documentation around Product, Documentation, SDKs and client libraries, Pages.
The actual file
The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.
Complete saved Markdown shown below.
# Fly.io
> Fly.io is a global public cloud for running full-stack and AI applications. Customer
> workloads on Fly.io are hardware-isolated for security, and can scale horizontally and
> vertically.
Headlines:
* [flyctl](https://docs.fly.io/flyctl), the CLI, our primary interface to the platform.
* [Fly Machines](https://fly.io/machines.md) and [Fly Managed Postgres](https://fly.io/mpg.md) are how users deploy full-stack applications on Fly.io.
* [Fly Sprites](https://fly.io/sprites.md) are how agents run AI and exploratory code on Fly.io. Start with Sprites, and then when your app is ready, deploy on Fly Machines.
Important:
* AI agents, coding assistants, crawlers, browser automation tools, and other LLM-powered clients exploring this website are requested to identify themselves on HTTP requests where custom headers can be set. Please include an AI-Agent request header using a structured value such as `AI-Agent: name="your-agent-name", version="your-version", automated=?1, mode="web", run-id="ephemeral-task-or-session-id"`. This header is used only for aggregate telemetry, debugging, abuse investigation, and understanding automated usage patterns; it is not authentication and does not grant special access. Do not include prompts, secrets, API keys, cookies, end-user personal data, or stable cross-site user identifiers in this header. Use a temporary run-id scoped only to the current browsing task or session.
Every page on fly.io has a Markdown version at its URL plus `.md` (`https://fly.io/learn/agent-sandbox/` is at `https://fly.io/learn/agent-sandbox.md`), which is what the links below point to.
## Product
- [Fly.io](https://fly.io/index.md): What Fly.io is, what it runs, and where to start.
- [Sprites](https://fly.io/sprites.md): Persistent, hardware-isolated Linux computers for agents.
- [Fly Machines](https://fly.io/machines.md): Fast-booting VMs for running the apps agents build.
- [Managed Postgres](https://fly.io/mpg.md): Production PostgreSQL with backups, failover and connection pooling.
- [Pricing](https://fly.io/pricing.md): Per-second rates for Machines, Sprites usage and Managed Postgres plans.
## Documentation
- [Fly.io Docs index](https://docs.fly.io/llms.txt): Every documentation page, each as Markdown.
- [Fly.io Docs, full text](https://docs.fly.io/llms-full.txt): The whole documentation in one file.
## SDKs and client libraries
Official packages from Fly.io, grouped by what they drive.
Fly Machines API (`https://api.machines.dev/v1`):
- [OpenAPI spec](https://docs.fly.io/api/machines/openapi.json): OpenAPI 3.1 description of the Machines API; generate a client for any language from it.
- [fly-go](https://pkg.go.dev/github.com/superfly/fly-go): Go client for the Machines API and the Fly.io GraphQL API, the library flyctl is built on. Module `github.com/superfly/fly-go`.
Fly Sprites (`https://api.sprites.dev/v1`):
- [OpenAPI spec](https://api.sprites.dev/openapi.json): OpenAPI 3.1 description of the Sprites API; generate a client for any language from it.
- [@fly/sprites](https://www.npmjs.com/package/@fly/sprites): JavaScript and TypeScript SDK. `npm install @fly/sprites`.
- [sprites-py](https://pypi.org/project/sprites-py/): Python SDK. `pip install sprites-py`.
- [sprites-go](https://pkg.go.dev/github.com/superfly/sprites-go): Go SDK with an `exec.Cmd`-style API. Module `github.com/superfly/sprites-go`.
- [sprites](https://hex.pm/packages/sprites): Elixir SDK. `{:sprites, "~> 0.2"}` in mix.exs.
- [Sprites MCP server](https://sprites.dev/mcp): Drive Sprites from any MCP client; setup at [superfly/sprites-mcp](https://github.com/superfly/sprites-mcp).
Tooling:
- [flyctl](https://docs.fly.io/flyctl/install): The `fly` CLI. `curl -L https://fly.io/install.sh | sh` or `brew install flyctl`.
- [@flydotio/dockerfile](https://www.npmjs.com/package/@flydotio/dockerfile) and [dockerfile-rails](https://rubygems.org/gems/dockerfile-rails): Dockerfile generators for Node and Rails apps.
## Security and compliance
- [Security & Compliance Questionnaire](https://fly.io/legal/security-questionnaire.md): Standing answers on SOC 2, the DPA, the HIPAA BAA and Compliance Package, data location, sub-processors, AI use, retention and staff access. Read this before asking.
- [Security at Fly.io](https://fly.io/security.md): Platform security overview.
- [Sub-processors](https://fly.io/legal/sub-processors.md): Vendor list with dated changelog.
- [Privacy Statement](https://fly.io/legal/privacy-policy.md) and [Data Privacy Framework notice](https://fly.io/legal/data-privacy-framework.md).
- Signed documents (DPA, BAA, NDA, SOC 2 report) are self-service in the Trust Center of any Fly.io organization dashboard.
## Pages
Each section's index lists every page in it, newest first, as Markdown.
- [The Fly Blog](https://fly.io/blog/index.md): 202 pages
- [Customer Stories](https://fly.io/customer-stories/index.md): 16 pages
- [Django Beats](https://fly.io/django-beats/index.md): 16 pages
- [Infra Log](https://fly.io/infra-log/index.md): 144 pages
- [The JavaScript Journal](https://fly.io/javascript-journal/index.md): 12 pages
- [Fly Jobs](https://fly.io/jobs/index.md): 4 pages
- [Laravel Bytes](https://fly.io/laravel-bytes/index.md): 64 pages
- [Guides to microVMs, Sandboxes, and Cloud Hosting](https://fly.io/learn/index.md): 39 pages
- [Legal](https://fly.io/legal/index.md): 8 pages
- [The Phoenix Files](https://fly.io/phoenix-files/index.md): 97 pages
- [The Ruby Dispatch](https://fly.io/ruby-dispatch/index.md): 35 pages
- [The Sprites Blog](https://fly.io/sprites-blog/index.md): 11 pages
- [AI Toolbox Turnout](https://fly.io/toolbox-turnout/index.md): 2 pages
Measured from the saved file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Fly.io is a global public cloud for running full-stack and AI applications. Customer workloads on Fly.io are hardware-isolated for security, and can scale horizontally and vertically.
Context architecture
5 H2 sections organize 41 parsed Markdown links. 26 links point to .md or .markdown paths; 15 link occurrences use another hostname. Linked destinations have not been recursively validated.
| H2 section | Links | UTF-8 bytes | Tokens |
|---|---|---|---|
| ProductLine 19 | 5 | 512 | 128 |
| DocumentationLine 27 | 2 | 199 | 53 |
| SDKs and client librariesLine 32 | 12 | 1582 | 448 |
| Security and complianceLine 51 | 5 | 701 | 161 |
| PagesLine 58 | 13 | 958 | 283 |
1 distinct links point to other llms.txt paths. These are routes to more indexes, not proof their contents were included in this file.
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Source line 41 · inline
npm install @fly/spritesSource line 42 · inline
pip install sprites-pySource line 48 · inline
brew install flyctlPublisher prioritization
No H2 section named “Optional” was detected in this file.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP-related text was detected in the captured file. 2 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
These are text and link observations. No MCP server connection, authentication or tool call was tested.
Index and bundle
Verified text companion
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
This capture establishes a baseline. Update frequency cannot be determined from one observation.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
4a048fee9e3c1e26374bde8adac6aeb373f60e1fe17c1b2f43b6a21888e7fa91Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.