Trust basics

Security
at a glance.

Wakehold is a multi-tenant control plane. This page states the trust posture we design for - tenant isolation, an inspectable proof trail, and payments handled by Paddle as Merchant of Record. It is not a compliance certification.

01

Tenant isolation

Customer, team, and environment boundaries stay scoped. Routing and context are tenant-aware so one fleet’s wake, packet, or capsule does not bleed into another’s plane. Operators work inside the scope they own.

02

Proof trail

Meaningful actions can carry sealed receipts - message, tracker, or system ids - so “done” is evidence, not a vibe. Work packets carry ownership; policy capsules pin versions. Together they give operators a trail they can inspect after the fact.

How receipts work →

03

Payments via Paddle

Token purchases will be processed by Paddle as Merchant of Record. Card data and tax handling sit with Paddle’s checkout - not on Wakehold’s public site. Until checkout is live, purchase CTAs use mailto placeholders; we do not invent live Paddle URLs.

Token packs →