Pricing that scales with your product integration requirements

Ampersand's core pricing metric is the amount of data processed and delivered, measured in gigabytes (GBs).

This model aligns costs with actual usage, offering flexibility and scalability. You only pay for the data you transfer. By using this pricing approach, Ampersand ensures that you have transparent and predictable costs directly tied to the value you receive from the platform.

Everything that happens in an integration is referred to as an Action, this includes:

• Read actions: read data from your customer's SaaS
• Write actions: write data to your customer's SaaS
• Subscribe actions (coming soon): subscribe to events (creates, deletes, and field changes) in your customer's SaaS
• Proxy actions: make passthrough API calls to the SaaS provider's API

“Data delivered” refers to the total volume of data that moves through Ampersand.

• For Read actions and Subscribe actions: this is the amount of data we send to your destination.
• For Write actions: this is the amount of data we send to the SaaS provider on your behalf.
• For Proxy actions that are a GET request, this is the response body size. For all other Proxy action calls, this is the request body size.

No, Ampersand’s pricing model is based on the amount of data delivered, regardless of the number of connections or customers. This directly ties costs to the value delivered, and allows you to freely experiment with building new integrations.

No, secure user token management is free to use. We also provide APIs to import and export tokens. We are anti vendor lock-in.

No. You pay the same to read from or write to any object or field, whether standard or custom.

No. You just pay for the data delivered across all your integrations. All customers, including those on the Launch plan, can build an unlimited number of integrations.

Backfills in Ampersand are a powerful feature that allows you to retroactively retrieve and process historical data from your customers’ applications. This is particularly useful when you need to sync past records or ensure your system has complete data coverage from a specific point in time.

The amount of data retrieved and delivered during a backfill will count towards your total data delivered.

Two gigabytes a month equals 2.0 GB of throughput. An early-stage tenant with about eight to ten thousand CRM records and a light stream of daily updates moves roughly 0.10 GB per month, so you can host around 15 to 20 such customers before you exhaust the pool. A mid-market tenant with roughly 80,000 records and more active ticket or email traffic averages about 0.30 GB monthly, which means five or six of these customers might fit inside the same 2 GB cap.

A backfill of roughly 150,000 records — Salesforce pegs a single record at about 2-4 KB each — landing near 1.0 GB a month, leaving room for two large pilots before overage applies. If usage exceeds 2 GB, nothing is throttled; each additional gigabyte is billed at the published overage rate, or you can move up to a tier with a larger allowance. The Ampersand architecture scales really well for complex use cases and serving our larger customers.

We are working with several pre-seed and seed stage startups that are happily using Ampersand’s Launch Tier, which provides 2 GB of data delivery for free. If your product requires a large amount of data from all your customers and you have concerns about pricing, please reach out to us. startups@withampersand.com

We love discussing the technical nitty-gritty of all things engineering. You can expect someone senior on the Slack channel to help your team during implementation and advise you on your integration roadmap items.

We work with engineers and PMs from your team to list your future requirements and review challenges with your current architecture, whether built in-house, with no-code or low-code tools, or unified API products. We then create a migration path towards a robust, scalable architecture and assist you with the Ampersand implementation.