For teams validating one proof workflow, private room, or treasury approval process.
Start with a focused pilot, then move into a monthly plan or private deployment when the workflow is proven.
For organizations running recurring workflows, governance rooms, approvals, and audit-ready verification.
For dedicated deployments, custom integrations, compliance workflows, white-label, and higher capacity.
A clear first purchase path.
Credit, underwriting, compliance, grants, vendor approval, or audit workflow.
Groth16 policy proofs that prove a private policy was satisfied without exposing policy inputs.
Private rooms, committee voting, DAO decisions, or foundation governance.
Treasury requests, approval paths, spending controls, and audit trails.
ZK policy proofs as a focused paid product.
Cloud SaaS
PrivateDAO hosts the product, verification pages, pilot workflows, and operational proof records.
Private Deployment
Annual license, setup fee, maintenance, support, and organization-bound activation for private environments.
Scale by intelligence, proof volume, deployment, and connectors.
Workflow summaries, risk explanations, proposal summaries, treasury analysis, and audit-ready explanations.
Additional monthly verification capacity for workflows, rooms, treasury approvals, and reports.
Environment setup, activation, deployment documentation, and organization-bound license packaging.
Connect one customer data source, redacted JSON feed, workflow API, or treasury context provider.
Start a trial, then activate a paid PrivateDAO workspace.
Choose a plan and payment path. Crypto activation can produce a receipt and organization license record from this page. Bank transfer and enterprise procurement are invoice-led through official PrivateDAO contacts.
USDC, SOL, ETH, BTC, ZEC, USDT, DAI. Submit the transaction hash to create a receipt.
Request an invoice and bank instructions for monthly or fixed-scope pilot activation.
Use discovery for private deployment, SLA, support, and custom capacity.
Paid modules are license-gated and tamper-evident.
PrivateDAO paid workspaces use signed organization-bound licenses, activation records, feature gates, server-side verification, usage limits, and audit logs. If a license is modified or cannot be verified, paid capabilities fail closed and require reactivation through official support.