Linking Vultr 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 Vultr connector syncs your cloud infrastructure inventory and billing data into PostHog – instances, bare metal servers, Kubernetes clusters, block storage, snapshots, load balancers, managed databases, users, billing history, and invoices. Use it to join spend and resource usage with your product and revenue data, or to build cost dashboards across your compute, storage, and managed services.
Prerequisites
You need a Vultr account with API access enabled and a personal access token.
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 Vultr, you'll need an API key:
- Sign in to the Vultr customer portal.
- Go to Account > API (my.vultr.com/settings/#settingsapi).
- Copy your Personal Access Token. If you don't have one, click Enable API and generate a token.
- If Access Control is enabled for the API, add PostHog's egress IP addresses to the allowlist (or allow all IPs) so PostHog can reach the Vultr API.
Paste the token into the API key field when adding the source in PostHog.
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 Vultr API doesn't expose an updated-since filter or webhooks on any list endpoint, so every table syncs with a full refresh on each run. Vultr accounts typically hold a small number of resources per table, so a full refresh is inexpensive.
| Table | Sync method |
|---|---|
instances | Full refresh |
bare_metals | Full refresh |
kubernetes_clusters | Full refresh |
block_storage | Full refresh |
snapshots | Full refresh |
load_balancers | Full refresh |
managed_databases | Full refresh |
users | Full refresh |
billing_history | Full refresh |
invoices | Full refresh |
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
instances | Cloud compute and GPU instances (virtual machines) in your Vultr account. | Full refresh | — | — |
bare_metals | Bare metal (dedicated) servers in your Vultr account. | Full refresh | — | — |
kubernetes_clusters | Vultr Kubernetes Engine (VKE) managed clusters. | Full refresh | — | — |
block_storage | Block storage volumes in your Vultr account. | Full refresh | — | — |
snapshots | Instance snapshots stored in your Vultr account. | Full refresh | — | — |
load_balancers | Load balancers in your Vultr account. | Full refresh | — | — |
managed_databases | Vultr Managed Databases (MySQL, PostgreSQL, Valkey, Kafka). | Full refresh | — | — |
users | Sub-users configured on your Vultr account. | Full refresh | — | — |
billing_history | Append-only account billing history line items (charges and payments). | Full refresh | — | — |
invoices | Account invoices. | Full refresh | — | — |
Troubleshooting
- Invalid API key – regenerate the token under Account > API in the Vultr portal and reconnect the source.
- Requests blocked / 403 – your token is valid but Vultr's API access control list is blocking PostHog. Add PostHog's egress IPs to the API key's allowlist, or temporarily allow all IPs.
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.