Resources · Enterprise Library
This customer data platform (CDP) resource index helps buyer teams find the right public material for architecture, security, integration and procurement reviews. It also explains which release-specific documents must be requested.
Library · Catalog
Nine resources organized across the three evaluation tracks enterprise teams use during architecture review and procurement.
Single-page enterprise brief: positioning, why now, capabilities, deployment models, security design, and TCO at a glance — for architecture, procurement, and executive review.
Ongoing field notes from PrivyCDP engineering: deployment patterns, AI operational layer, identity, governance, and procurement design — written for architecture and security teams.
Three-layer reference architecture, deployment models, and update pipeline for the customer-owned environment.
Identity, decisioning, AI operational layer, and integration interface inside the Private AI Customer Data Infrastructure.
Single-tenant boundary, customer-owned residency, segmented architecture, and immutable audit ledger.
Line-by-line decomposition of license, infrastructure, DevOps, support, and update entitlement components.
Annual and Perpetual licensing models, Annual Version Extension & Update Entitlement, and support tiers.
Procurement-grade pricing design without profile-based billing, activation tax, or usage trap.
Identity unification, real-time decisioning, journey orchestration, and AI-assisted operations.
Deployment context, architecture, and operational outcomes from regulated enterprise references under NDA.
Vertical deployment topology references for finance, gaming, healthcare, government, legal, and commerce.
Planning your evaluation
Choose one bounded workflow and use the same requirements when comparing architecture, deployment and cost.
List the source events, identity rules, permitted fields and activation destination. Ask for a demonstration with synthetic records, including consent withdrawal, duplicate handling and recovery after a failed delivery.
Name the operators for infrastructure, access, backups and releases. Obtain current license and service terms, then model normal load, growth, recovery and exit costs for the same deployment.
Start with the decision your team needs to make. Architecture reviewers can use Product, Deployment and Security to prepare a data-flow and ownership discussion. Procurement reviewers can separate quote scope, license rights and operating costs using Pricing, Licensing and TCO. Integration engineers should identify the supported release and obtain the contracts listed in the API reference before treating a public description as implementation instructions.
Each resource has a different job. The industry pages describe workflow requirements, the compliance guides identify questions and primary sources, and deployment patterns illustrate the evidence to request. None of those pages establishes a customer result or a certification. Use the existing blog for background on privacy, assistive AI and email infrastructure, with publication context preserved for historical material.
The linked public pages and the one-page PDF are available here. Request installer verification, supported configuration examples, API descriptions, connector versions and operating runbooks for the proposed release during review. Confirm availability and confidentiality terms rather than assuming every named artifact is already supplied. Bring a synthetic payload, relevant access owners and the evidence needed for your next decision; the shared checklist below keeps that evaluation bounded.
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.