Documentation

Chameleon developer docs

Technical documentation for engineers evaluating, integrating with, or self-hosting Chameleon: how the system is put together, how PII gets declared and protected, and how deletion produces verifiable proof.


Start here

Core concepts

Begin with architecture if you're deciding whether Chameleon fits your stack — everything else builds on the control-plane/data-plane split and the two encryption schemes described there.

Architecture

Control plane vs. data plane, the two AES-256-GCM encryption schemes, and the single-key-per-user model that makes deletion instant. Available now.

PII registry

How resources get declared — manually, via the dbt package, or by the discovery crawler — and what a declaration actually contains. Available now.

Crypto-shredding & deletion

The six-state deletion lifecycle, what a completed key-destruction actually guarantees, and the source-redaction options for a resource's original table. Available now.

Certificates

The hash-chained Certificate of Destruction: how it's signed, how to verify it independently, and exactly what its coverage claims do and don't promise. Available now.


Reference

API reference & deployment

API reference

The full REST surface grouped by concern: keys & crypto, the PII registry, deletion & lineage, certificates, decrypted views, and analyst access. Available now.

Self-hosting (BYOC)

The bring-your-own-cloud deployment model: run Chameleon entirely inside your own GCP project, using the public Terraform installer. Available now.

Hosted deployment

A fully isolated instance Chameleon provisions and runs for you — same architecture, no infrastructure knowledge required. Available now.


Keep reading

Control plane vs. data plane, the two encryption schemes, and the single-key-per-user model.

How manual, dbt-managed, and discovered declarations compose into one registry.

How the signed, hash-chained Certificate of Destruction is generated and verified.