Usage & Billing

Honesty Ledger (Provenance Layer): Usage and billing metrics are tracked at the Server-known (Layer A) layer.

ZK Trust Boundary:

• What the server sees: Plan status, checkout sessions, and aggregate resource counts (bytes stored, sync volumes, sub-key counts).
• What stays on device: Decryption keys and cleartext memory content.

---

Usage and Billing

The Usage & Billing page enables teams to monitor resource quotas, review plan structures, and manage checkout details. Because the server is blind, billing calculations rely strictly on Layer-A metadata.

Resource Quota Meters

Resource usage is measured across four main quotas:

• Sync Operations: The number of background write/read synchronization runs executed.
• Encrypted Bytes: The total size of ciphertext envelopes stored on Supabase edge storage.
• API Sub-keys: The count of active cryptographic sub-keys generated for team agents.
• Sync Devices: The number of concurrent client sessions connected to the project.

Visual Warnings and Thresholds

Usage meters update dynamically based on replication events:

• Amber Warning: Quota bars turn amber when usage reaches 80% of plan limits, warning you of upcoming limits.
• Red Over-limit: Quota bars turn red at 100% capacity. Once exceeded, subsequent write-behind pushes are rejected with a 402 Payment Required or 429 Too Many Requests error. Envelopes remain cached in local LanceDB databases until you upgrade.

Polar Merchant of Record Integration

Subscriptions are processed securely through Polar.sh:

• Sandbox Testing: The Pro and Team tiers can be tested using the sandbox checkout system.
• Redirect Portal: Clicking Manage Subscription redirects the user to the Polar customer billing portal, where they can download invoices, update payment methods, or cancel plans.

Server-Blind Quota Audits

---

Offline Reference Analogs: This documentation was written with visual and rhythm reference to platform/features/platform-overview.html.