TCO · Procurement · Long-Term Ownership
Compare the cost of running a customer data platform (CDP) for three years. Add the licence, hosting, setup, staff and updates. Use your own quotes and assumptions. The model helps you compare options; it is not a price offer.
Three-year cost components
No percentage allocation is asserted. Compare the same workload, term and operating responsibilities.
Scope · License Boundary
The license covers the software platform itself. Infrastructure, hardware, DevOps, and managed services are engaged separately, so each line in the TCO has a clear owner and a clear cost basis.
Delivered under the PrivyCDP license itself.
PrivyCDP platform binaries, runtime, identity engine, AI decisioning layer, audit ledger, and orchestration core.
Version updates, security patches, and capability releases delivered during the active license or entitlement term.
Deployment runbooks, integration references, governance templates, and compliance control documentation.
Defect resolution, version compatibility guidance, and structured escalation channels during business hours.
Open APIs, MCP-ready endpoints, and webhook integrations for connection into customer-owned systems.
Engaged under separate scope · transparent line-by-line cost.
Compute, storage, networking, and managed cloud services billed directly by the customer's chosen provider.
On-premise servers, accelerators, network equipment, and air-gapped facility hardware.
Provisioning, observability, CI/CD integration, and ongoing platform operations — engaged per scope.
Optional managed support beyond the standard support tier, scoped under a separate engagement.
Bespoke connectors, downstream system integration, and customer-specific orchestration logic.
Comparison · 3-Year Composition
A line-by-line comparison of how typical SaaS CDPs accumulate cost versus a customer-owned PrivyCDP deployment under both Annual and Perpetual licensing.
Principles · Pricing Architecture
Five enforced principles that govern how PrivyCDP licensing and surrounding scope are structured for enterprise procurement.
Pricing does not scale with the number of customer profiles, identities, or behavioral records ingested into the platform.
Per-event, per-channel, or per-message fees are not used. Activation throughput is governed by deployed infrastructure, not metered billing.
The platform is not delivered through a shared multi-tenant cloud. Customer-owned deployment is the default operating model.
Compute, storage, networking, hardware, and managed services are scoped under separate engagements with transparent cost visibility.
Procurement can select term-bound annual licensing or perpetual licensing paired with the Annual Version Extension & Update Entitlement.
Economics · License Models
Two licensing paths, both procurement-friendly. Perpetual aligns with long-term ownership models; Annual aligns with operational expense cycles.
Time-bounded usage rights renewed on an annual cadence.
Predictable annual line item for procurement and finance.
Includes all updates and support during the active term.
Time-unlimited usage rights to the licensed software version.
Paired with an optional Annual Version Extension & Update Entitlement.
Aligned with long-term ownership and capital procurement models.
The Perpetual license remains valid indefinitely. The Annual Version Extension & Update Entitlement is a separate, optional mechanism covering continued releases, security patches, and version compatibility for an annual term — it is not a subscription.
Compliance is achieved through a combination of customer-owned infrastructure controls and PrivyCDP control documentation.
Planning your evaluation
Use current written quotes and internal cost estimates. No approved PrivyCDP rate card is asserted here; the worked model shows how to combine your inputs without inventing a license price.
Take annual software license L and one-time implementation I from the written proposal. Let C be monthly cloud spend, O monthly operations and S separately scoped monthly support. Year one = L + I + 12(C + O + S). Years two and three each = L + 12(C + O + S), assuming unchanged rates. Total = 3L + I + 36(C + O + S).
Use quoted upfront license P and annual update entitlement U for the selected version and term. With the same implementation and operating assumptions, year one = P + U + I + 12(C + O + S). Each following year = U + 12(C + O + S). Three-year total = P + 3U + I + 36(C + O + S). The license comparison is 3L versus P + 3U; actual quotes determine the result.
If cloud and operations costs double for the full period, add 36(C + O) to either example. If an extra region runs for only the final year, add 12 times its monthly cost. Model retention growth, disaster recovery and migration overlap separately, and state the currency, taxes, financing and internal staffing assumptions.
Separate software, implementation, infrastructure, operations, update entitlement and support. If support or updates are included in a quote, do not add them again. Include external activation providers, integration maintenance and exit/export costs before comparing alternatives.
Pricing covers quote scope; TCO models the operating period; Licensing covers agreement terms. Use the same deployment assumptions across all three.
Discuss your deployment with engineers.
Bring your data flow, operating owners and evaluation questions.
Published: · Updated:
Editorial dates describe content changes. Confirm current sources before making legal, security or purchasing decisions.