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

# Linking Koyeb as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/koyeb

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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`

![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

The Koyeb connector syncs apps, services, deployments, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

Enter a Koyeb API token to pull your Koyeb apps, services, deployments, instances, event streams, and usage details.

Create an API token under [API settings](https://app.koyeb.com/user/settings/api) in the Koyeb console. Tokens are scoped to the organization they were created in.

You'll be asked for:

-   **API token**

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All Koyeb tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `projects` | Projects in your Koyeb organization. A project groups related apps and services. | Full refresh | — | id |
| `apps` | Applications in your Koyeb organization. An app groups services and holds the public \*.koyeb.app domains assigned to them. | Full refresh | — | id |
| `services` | Services running inside your Koyeb apps: web services, workers, and databases. | Full refresh | — | id |
| `deployments` | Deployments of your Koyeb services. Each deployment captures the full definition of a service version and its rollout status. | Full refresh | — | id |
| `regional_deployments` | Per-region rollouts of a deployment, one row per region a deployment runs in. | Full refresh | — | id |
| `instances` | Compute instances backing your Koyeb services, one row per instance (replica) of a regional deployment. | Incremental, Full refresh | created\_at | id |
| `domains` | Domains in your Koyeb organization: auto-assigned \*.koyeb.app domains and verified custom domains. | Full refresh | — | id |
| `secrets` | Secrets defined in your Koyeb organization. Metadata only — secret values are never returned by the list API and are not synced. | Full refresh | — | id |
| `volumes` | Persistent volumes attached to your Koyeb services. | Full refresh | — | id |
| `snapshots` | Snapshots of your Koyeb persistent volumes. | Full refresh | — | id |
| `organization_members` | Members of the Koyeb organization the API token is scoped to. | Full refresh | — | id |
| `activities` | Audit trail of actions performed in your Koyeb organization: who did what to which object. | Full refresh | — | id |
| `app_events` | Append-only stream of lifecycle events for your Koyeb apps. | Full refresh | — | id |
| `service_events` | Append-only stream of lifecycle events for your Koyeb services. | Full refresh | — | id |
| `deployment_events` | Append-only stream of lifecycle events for your Koyeb deployments. | Full refresh | — | id |
| `instance_events` | Append-only stream of lifecycle events for your Koyeb instances. | Full refresh | — | id |
| `usage_details` | Per-instance usage records for your Koyeb organization: one row per instance run with its duration, used for billing. | Full refresh | — | instance\_id, started\_at |
| `catalog_instances` | Catalog of Koyeb instance types with their resources, pricing, and availability. Join on instance\_type to size and price services, deployments, and usage. | Full refresh | — | id |
| `catalog_regions` | Catalog of Koyeb regions with their location and the instance types available in each. Join on region to resolve the region codes on deployments, instances, and usage. | Full refresh | — | id |

## Troubleshooting

-   If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
-   If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.