Pricing · Procurement · Long-Term Ownership
Customer data platform (CDP) pricing: annual and perpetual licensing
Plan what goes into your customer data platform (CDP) quote. Separate the software licence from hosting, setup, staff and support. Use the cost model to compare three years of running costs.
Procurement-grade · Scoped components
POS-01
Annual / Perpetual
Software License
POS-02
Annual
Update Entitlement
POS-03
Customer-owned
Infrastructure
POS-04
Standard / Enterprise / Sovereign
Support
Each component is scoped independently. Procurement, finance, and architecture teams model them as separate line items.
Section 01 · Procurement Paths
Two Procurement Paths
Both paths grant rights to the same product — Private AI Customer Data Infrastructure — deployed inside the customer's own environment. The choice aligns with procurement framework, not with platform capability.
Annual License
Time-bounded right to deploy and operate PrivyCDP. Renewed annually with all updates and standard support included during the active term.
- Time-bounded right to deploy and operate
- All product updates during the active term
- Standard support coverage during the term
- Anonymized reference access during evaluation
Enterprises that prefer operating-expense procurement, predictable annual budgeting cycles, and bundled support coverage tied to the active license term.
Perpetual License
Time-unlimited right to deploy and operate the licensed version. Paired with the optional Annual Version Extension & Update Entitlement.
- Time-unlimited right to deploy and operate
- Indefinite use of the licensed version
- Optional Annual Version Extension & Update Entitlement
- Optional Enterprise or Sovereign support tier
Enterprises and sovereign organizations requiring capital-expense procurement, long-horizon ownership, and operation independent of vendor renewal cycles.
Section 02 · License Boundary
What's NOT in the License
The license covers the software platform itself. Every other operational interface is scoped under a separate engagement — so each cost line in the TCO has a clear owner and a clear cost basis.
Infrastructure
Scoped under separate engagement
DevOps
Scoped under separate engagement
Cloud
Scoped under separate engagement
Hardware
Scoped under separate engagement
Managed Support
Scoped under separate engagement
This separation is intentional. It keeps total cost of ownership transparent, prevents lock-in to a specific cloud or hardware vendor, and ensures the customer retains operational control of the environment in which PrivyCDP runs.
Section 03 · Pricing Architecture
Why No Profile-Based Billing
Enterprise customer data platforms cannot be priced as if profiles were a vendor revenue lever. Profiles are a customer obligation, not a vendor metering interface.
Profile counts are driven by the customer's regulatory retention requirements, audience scale, and operational reality — not by the platform's commercial design. PrivyCDP keeps cost decoupled from those dimensions and scopes throughput against deployed infrastructure instead.
Cost does not compound with profile growth, identity counts, or behavioral record retention.
Regulated retention windows do not inflate platform cost. Customer obligations remain decoupled from vendor billing.
Throughput is governed by deployed infrastructure. Per-event, per-channel, and per-message metering are not used.
Section 04 · TCO Preview
Compare 3-Year TCO
A representative 3-year composition for a customer-owned PrivyCDP deployment. Build a line-by-line model against your existing SaaS CDP stack in the full TCO interface.
Three-year cost components
- License: obtain a scoped quote or measured operating estimate.
- Infrastructure: obtain a scoped quote or measured operating estimate.
- DevOps: obtain a scoped quote or measured operating estimate.
- Support: obtain a scoped quote or measured operating estimate.
- Update entitlement: obtain a scoped quote or measured operating estimate.
No percentage allocation is asserted. Compare the same workload, term and operating responsibilities.
Procurement Note
Full procurement documentation — license terms, entitlement scope, and support definitions — is provided for legal and finance review during enterprise evaluation. References are protected under strict NDA.
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.
Further reading
- CDP Pricing Explained
- CDP TCO: Scenario Workbook
- CDP TCO Calculator: 3-Year Comparison
- Three-year total cost model
- Licensing and support
Published: · Updated:
Editorial dates describe content changes. Confirm current sources before making legal, security or purchasing decisions.