DPDP Rules 2025 notified — enforceable 13 May 2027.|Time left: –d –h –m –s
What it covers

The codebase, not a hosted rental

Source code, deployment, the consent engine itself, and everything your team needs to run it independently from day one.

Full source code delivery

The actual CMP codebase handed over, not access credentials to a hosted instance.

Deployment on your own infrastructure

Installed and running in your environment, under your own operational control from day one.

Consent capture & storage engine

The working mechanics of recording, timestamping and storing consent per purpose and per data element.

Integration with existing systems

Connecting the platform to your web, app and backend systems per the architecture already designed.

Ownership handover & documentation

The technical documentation and access your team needs to run and modify the platform independently going forward.

What you get

Owned outright, no recurring licence

Full source, a working deployment on your own infrastructure, and a handover built so your team can run it without us.

  • The complete CMP source code, owned outright — no recurring licence fee
  • A working deployment on your own infrastructure, configured for your systems
  • Technical documentation covering architecture, configuration and how to extend it
  • A handover session so your own engineering team can operate and modify it independently
Process

Four stages, click any to see more

From architecture handoff through build and deployment, to a handover your engineering team can actually run with.

01

Architecture handoff & scoping

Confirm the design — from Consent Architecture Design, or built fresh — and scope the build.

Whether the architecture already exists from a prior engagement or gets built fresh here, the scope is locked before development starts.

02

Build

Develop the platform against the agreed architecture and integration points.

The consent capture and storage engine takes shape here — recording, timestamping and storing consent per purpose and per data element.

03

Deployment

Install and configure the platform on your own infrastructure.

Running in your environment under your own operational control from day one, not on a vendor's hosted instance.

04

Testing & handover

Validate the deployment against real scenarios, then hand over source, documentation and operational control.

Source code, technical documentation and a handover session, so your own engineering team can run and modify it independently.

Ready to own your consent stack outright?

30 minutes to scope the build — no obligation.

Book a Consultation