Predictable prices
Start now with a 30-day free trial, upgrade for more deployment and security, and save with yearly contracts.
Save more with annual contracts and yearly billing!
Annual contracts reward your commitment with lower rates and the peace of mind of a fixed yearly budget.
- Startups
- Non-profits
Simple, fair, and built for scale
Our services
Professional services
Partner Integrators
FAQ
Popsink charges based on the number of transactions replicated. A transaction represents a single data change (insert, update, or delete) captured from a source system and delivered to a destination.
No. Backfills and initial loads are free of charge. Only incremental changes replicated in real time are counted as billable transactions.
All replicated transactions across your connectors and streams are pooled together at the deployment level. This means every new stream adds volume to the same pool, moving you into lower, degressive rates as you scale.
Yes. Annual plans unlock additional discounts on top of the standard volume-based pricing. This helps you save while securing predictable costs.
For customers who prefer full predictability, Popsink offers:
- Annual contracts that guarantee fixed pricing for the contract term.
- Enterprise License Agreements (ELAs) that cover the needs of an entire organization with a locked cost structure, regardless of the number of connectors or streams.
Unlike some solutions that bill on Monthly Active Rows (MAR) or on compute usage, Popsink pricing is tied only to the data transactions you actually replicate. This ensures your costs grow slower than usage, giving you more value as volumes increase.
While the base model is transaction-based, final pricing may vary depending on:
- The chosen deployment model (cloud-managed, BYOC, or on-premise).
- Specific security and compliance features (e.g. VPN tunnels, air-gapped deployments).
- The level of support and SLA response times required (standard or premium).
A transaction is any single change event (insert, update, or delete) captured on a source system and delivered to a target destination. For example:
- Updating 1,000 rows generates 1,000 transactions.
- Inserting 10,000 new rows generates 10,000 transactions.
- Deleting 500 rows generates 500 transactions.
Yes. Because pricing is both usage-based and degressive, you only pay for the volume of replicated transactions, and the per-transaction cost decreases as your total usage grows. You can also adjust deployment and SLA options as your needs change.
Contact us for a tailored quote. We’ll factor in your expected transaction volume, deployment model, and support requirements to give you an exact pricing proposal.