Linking Baseten as a source
This source is currently in alpha. The interface and available tables may change.
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.
Contents
The Baseten connector syncs models, deployments, model environments, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Your Baseten account needs to be able to create API credentials, and those credentials need access to 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 your Baseten API key to sync your Baseten workspace data.
Create an API key in your Baseten workspace settings. The key is workspace-scoped and read access to your models, deployments, chains, and training resources is sufficient.
You'll be asked for:
- API key
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 Baseten tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
models | Models deployed in your Baseten workspace. | Full refresh | — | — |
deployments | Deployments of each model, including autoscaling state and active replica counts. | Full refresh | — | — |
model_environments | Environments (e.g. production, staging) configured for each model. | Full refresh | — | — |
chains | Chains (multi-model inference pipelines) in your workspace. | Full refresh | — | — |
chain_deployments | Deployments of each chain, including their chainlets and status. | Full refresh | — | — |
training_projects | Training projects in your workspace. | Full refresh | — | — |
training_jobs | Training jobs across all training projects. | Full refresh | — | — |
users | Users with access to your Baseten workspace. | Full refresh | — | — |
model_apis | Baseten Model APIs catalog, enriched with any workspace-specific state. | Full refresh | — | — |
instance_types | Catalog of compute instance types available on Baseten. | Full refresh | — | — |
instance_type_prices | Instance types with their usage price, in USD per minute. | Full refresh | — | — |
secrets | Secrets configured in your workspace. Values are never returned by the API. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one in Baseten and reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions in Baseten, 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.