Linking CAST AI 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 CAST AI connector syncs your Kubernetes cost and savings data from CAST AI into the PostHog data warehouse. This lets you analyze cluster costs, spot vs on-demand spend, and optimization savings alongside your product analytics.
Prerequisites
You need a CAST AI account with API access enabled. A read-only API key is sufficient.
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.
When linking CAST AI, you'll need:
- API key – create one in your CAST AI console under API Access settings.
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.
The clusters table always syncs as full refresh since the CAST AI API has no server-side timestamp filter for it.
The cluster_cost_reports and cluster_savings_history tables support incremental syncs on their timestamp fields, which we recommend to avoid re-fetching historical data on every sync.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
clusters | A Kubernetes cluster connected to CAST AI for cost monitoring and optimization. | Full refresh | — | — |
cluster_cost_reports | Historical compute cost for a cluster, bucketed by time interval and broken down by on-demand, spot, and spot-fallback instance cost. | Incremental, Full refresh | timestamp | — |
cluster_savings_history | Historical comparison of a cluster's real cost against CAST AI's estimated optimal cost under different optimization strategies, used to track realized and available savings. | Incremental, Full refresh | createdAt | — |
Troubleshooting
- Authentication error (401): your API key is invalid or has been revoked. Create a new key in your CAST AI console under API Access settings, then reconnect.
- Permissions error (403): your API key does not have the required permissions. Check the key's scopes in your CAST AI console, then reconnect.
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.