Pricing
Priced for your connector scope,
not a generic tier.
Every Community Bridge deployment is provisioned to your environment — your connectors, your data boundaries, your governance rules. Pricing reflects that scope, not a one-size-fits-all plan.
Book a data flow mapping session. We'll scope your connectors, identify the opportunities your systems can already surface, and give you a real number.
What affects the price
These are the factors we look at when scoping a deployment. No surprises.
Connector scope
How many source systems feed the hub, and how many destination tools receive data from it. A Daxko to HubSpot deployment is different from a five-connector setup with writeback.
Sync frequency
How often source systems are polled or how many webhook events are processed per day. Higher activity centres generate more hub changes and downstream projection work.
Audience volume
How many active audiences are defined, how frequently they are re-evaluated, and how many people and households are in scope.
Writeback requirements
Whether approved writeback to source systems is required — updating contact fields, communication preferences, or other governed fields back to Daxko, Club Automation, or other source systems.
Tenant environment
Each customer gets their own provisioned runtime environment and data boundary. Deployment complexity varies by infrastructure needs and data volume.
What's always included
Every Community Bridge deployment includes the full platform — governance, audiences, profiles, and controls. There are no stripped-down tiers.
Why we don't publish a tier table
Most integration platforms publish three tier names and hope your centre fits one of them. Community Bridge doesn't work that way.
Each deployment is provisioned to its own runtime environment and data boundary. The connector scope, sync frequency, audience volume, and governance requirements vary meaningfully between customers. A single price would either undercharge complex deployments or make simpler ones feel overpriced.
A 30-minute mapping session gives us what we need to scope your deployment accurately and give you a number that reflects your actual situation — not a generic plan.
Start with your data flow map.
We'll identify which source fields should reach which tools, which rules should govern them, and what your deployment would look like.
No product pitch. We'll map your first opportunity and give you a real scope.
Book a mapping session