> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Fly.io as a source - Docs

Copy page

# Linking Fly.io as a source - Docs

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

[Learn more](/wizard.md)

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The Fly.io connector syncs your infrastructure inventory – apps, machines, and volumes – into PostHog. Query your Fly.io fleet alongside product data for auditing, capacity planning, and correlating infrastructure state with user behavior.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.

2.  Click **\+ New source** and then click **Link** next to Fly.io.

3.  Create an organization-scoped API token. You can do this two ways:

    -   Run `fly tokens create org` in the [Fly CLI](https://fly.io/docs/flyctl/)
    -   Go to the **Tokens** section of your [Fly.io dashboard](https://fly.io/dashboard)

    A read-only org token is sufficient.

4.  Back in PostHog, paste your API token and enter your **organization slug**. Use `personal` for your personal org. Run `fly orgs list` to find the slug for other organizations.

5.  Select the tables you want to sync, set the sync frequency, then click **Import**.

Once the syncs are complete, you can start using Fly.io data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| apps | Apps in the organization. An app is the top-level unit that groups machines, volumes, and networking. | Full refresh |
| machines | Machines (Firecracker microVMs) across the organization, one row per machine with its owning app. | Full refresh |
| volumes | Volumes (persistent storage) across the organization, one row per volume with its owning app. | Full refresh |

All tables use **full refresh**, meaning they reload all data on each sync. Incremental sync isn't available for Fly.io tables.

> **Note:** The `machines` table includes a `config` column with the machine configuration overview (guest resources, image, and services). Secret-bearing fields – environment variables, secrets, inline file contents, user-defined metadata, and request headers on services and checks – are excluded for security.

## Configuration

| Option | Description |
| --- | --- |
| API tokenType: passwordRequired: True |
| Organization slugType: textRequired: True | Your Fly.io organization slug — use personal for your personal org. Find it with fly orgs list. |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| apps | Fly.io apps in the organization. An app is the top-level unit that groups machines, volumes, and networking. | Full refresh | — | id |
| machines | Fly.io machines (Firecracker microVMs) across the organization, one row per machine with its owning app. | Full refresh | — | id |
| volumes | Fly.io volumes (persistent storage) across the organization, one row per volume with its owning app. | Full refresh | — | id |

### Was this page useful?

HelpfulCould be better