Linking Koyeb as a source
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.
This source is currently in alpha. The interface and available tables may change.
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
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- 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 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_attimestamp). 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 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 |
|---|---|---|---|---|
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 |
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. If that doesn't help, contact support – we're happy to help.