Skip to main content
BundleUp pricing is simple and usage-based. You pay for requests, not integrations, not connections, and not users. We believe infrastructure pricing should scale with actual usage, not arbitrary limits.

​
How Pricing Works

BundleUp charges based on the number of proxy requests executed per month. A request is counted each time your application sends an API call through the BundleUp proxy to an upstream provider. Examples:
  • Sending a Slack message → 1 request
  • Fetching 50 GitHub issues (single API call) → 1 request
  • Updating a Linear ticket → 1 request
BundleUp does not charge based on:
  • Number of integrations
  • Number of connected accounts
  • Number of workspaces
  • Number of users

​
How Requests Are Counted

A request is counted when:
  • A proxy call is executed against an upstream API
  • A unified API request is translated and executed
  • A successful or failed upstream attempt occurs
Retries initiated by BundleUp due to provider rate limiting or transient failures count as requests because they consume upstream API calls. Authorization redirects and dashboard activity do not count toward request usage.

​
Why Per-Request Pricing?

We charge per request because:
  • It aligns cost with real usage
  • It removes artificial limits on integrations
  • It encourages architectural flexibility
  • It avoids penalizing multi-tenant SaaS products
You can connect 1 account or 10,000 accounts — pricing scales only with activity.

​
Example Cost Scenarios

​
Early Startup

  • 120,000 requests/month
  • Cost: Free

​
Growing SaaS Tool

  • 2.4 million requests/month
  • Cost: Base plan + 1.4M overage
  • Additional cost: $5 × 1.4 ≈ $7

​
Large Platform

  • 25 million requests/month
  • 1M included
  • 24M additional
  • Additional cost: $5 × 24 = $120
Simple and predictable.

​
Overage Policy

If you exceed your included request volume:
  • Usage continues uninterrupted
  • Additional requests are billed at $5 per million
  • No automatic shutdowns
You can monitor usage from the dashboard.

​
Our Philosophy

We built BundleUp because integration infrastructure should:
  • Be simple
  • Scale naturally
  • Avoid confusing tier structures
  • Avoid penalizing growth
If your usage grows, your pricing grows proportionally. Nothing more.