Stack SpendDocs

Connecting Providers

Connect your cloud, AI, and data providers to StackSpend and start tracking spend in minutes.

StackSpend supports 15 providers across cloud infrastructure, AI APIs, data platforms, and communications services. Once connected, each provider syncs automatically every 6 hours so your cost data stays current. The guides below walk you through every provider — most take under 5 minutes to set up.

If you are new to StackSpend, start with whichever provider represents your largest spend. AI API providers (OpenAI, Anthropic, Cursor, Grok) are the fastest to connect — just paste an API key. Cloud providers (AWS, GCP, Azure) take a few extra minutes because they require read-only billing permissions to be configured on your account.

Provider overview

ProviderTypeData latencyHistorical dataSetup timeGuide
OpenAI logoOpenAIAIReal-timeFull history2 minSetup guide →
Anthropic logoAnthropicAIReal-timeFull history2 minSetup guide →
Claude (OTel) logoClaude (OTel)AI~1 hourFrom setup date5 minSetup guide →
Cursor logoCursorAIReal-timeFull history2 minSetup guide →
Grok (xAI) logoGrok (xAI)AIReal-timeFull history2 minSetup guide →
Hugging Face logoHugging FaceAIMonthlyFrom setup date3 minSetup guide →
AWS logoAWSCloud24–48 hours90 days5 minSetup guide →
GCP logoGCPCloud24–48 hoursFrom setup date10 minSetup guide →
Azure logoAzureCloudDaily90 days5 minSetup guide →
GitHub logoGitHubCloudDailyFrom setup date3 minSetup guide →
Snowflake logoSnowflakeDataDaily90 days5 minSetup guide →
Vercel logoVercelCloudDaily90 days5 minSetup guide →
ClickHouse Cloud logoClickHouse CloudDataDaily90 days5 minSetup guide →
Twilio logoTwilioCommsDaily90 days3 minSetup guide →

GCP is the most complex setup (10 min) because it requires BigQuery billing export to be configured in your Google Cloud project before StackSpend can read your data. All credentials are encrypted at rest.

GCP billing export must be enabled before you connect.GCP does not provide historical cost data — StackSpend can only ingest data from the date you enable BigQuery billing export in your Google Cloud project. Enable billing export first, then return here to connect your account, so you do not miss any data.

How sync works

After you connect a provider, StackSpend runs an automatic sync every 6 hours to pull in the latest cost and usage data. The sync schedule is fixed and runs in the background — you do not need to keep a browser tab open.

If you need fresher data immediately — for example, after a large deployment — you can trigger a manual sync at any time from the provider's detail page. Navigate to Settings → Providers, open the provider, and click Sync now. Manual syncs are subject to the same latency windows listed in the table above; triggering a sync for a provider with 24–48 hour latency will not return data that the provider has not yet published.

StackSpend's IP addresses (for allowlists & network policies)

If your provider restricts inbound access with an IP allowlist or network policy — most commonly a Snowflake network policy, but also locked-down databases or warehouses — add StackSpend's fixed outbound IP addresses to the allowed list. All connections and scheduled syncs originate from these addresses:

  • 152.55.176.240
  • 162.220.232.252
  • 152.55.177.181
Add all of the addresses above.Traffic can leave from any one of these IPs (they are high-availability addresses), so allow all of them — allowlisting only one will cause syncs to fail intermittently when the connection egresses from a different address.
Private networks (Azure Private Link, VPC-only).If your provider is reachable only over a private network — for example a Snowflake account behind Azure Private Link with public access disabled — there is no public endpoint for StackSpend to reach, so an IP allowlist alone will not work. Contact us at support@stackspend.com and we'll set up a push-based ingest instead.
StackSpend Docs