Billing

Palveron bills per governance request — every verify call, MCP tool call, and extension event counts as one. Tokens and agents are not billed line items.

Plans

Four tiers — Community, Pro, Business, Enterprise. Every tier ships the core governance engine; they differ in monthly request volume, rate limits, agent/policy/team capacity, trace retention, and advanced feature gates. The authoritative, always-current limits live on the pricing page — it renders directly from the live tier configuration, so it can never lag behind a plan change.

What happens when the monthly quota is reached depends on your tier's configured limit behavior: hard-stop, top-up packs, or auto-overage — see the sections below.

Self-service plans (Community / Pro / Business) run on Stripe. Enterprise plans run on individual contracts (see Manage contracts).

Stripe checkout

Pro and Business upgrades flow through Stripe Checkout. From the dashboard:

Billing → Plan, click Upgrade.
Pick monthly or annual billing — annual billing is discounted; the current rates are on the pricing page.
Stripe Checkout opens — enter card or SEPA details.
Once payment confirms, the project tier is updated within seconds via Stripe webhook.

A receipt is emailed automatically. The same flow is available programmatically via POST /api/v1/billing/checkout.

Stripe Customer Portal

Every billable project has a Stripe-hosted self-service portal: change payment method, download invoices, update billing address, cancel.

POST /api/v1/billing/portal

Returns a short-lived URL that admins can hand to finance teams without giving them dashboard access.

Top-up payments for overages

Plans with top-up behavior can purchase top-up packs when monthly quota runs low — no plan change required. Three pack sizes are offered; the current sizes and prices are shown in the dashboard under Billing → Top-up and on the pricing page.

Top-ups roll over indefinitely and consume after the included quota. Bought via Stripe Checkout.

Auto-overage

On tiers configured for overage billing, requests above the included quota continue to be served and the overage rate (per 1,000 requests) is invoiced at the end of the period. Toggle under Billing → Plan.

Usage metering

Every request is metered server-side and surfaces in three places:

Dashboard — Command Center KPIs (near real-time) and Usage Reports (per-day breakdown, page).
API — GET /api/v1/usage/report?month=2026-05 (month in YYYY-MM, defaults to the current month) returns the monthly summary with daily totals plus per-agent breakdown.
Webhooks — usage.threshold_reached fires at 80%, 90%, and 100% of monthly quota.

Counters reset at 00:00 UTC on the first of each calendar month. RPM (requests per minute) limits apply independently — see Tiers & Limits.

On-premise & air-gapped (planned)

On-premise and air-gapped deployments are on the post-launch roadmap and not yet generally available. The metering design below documents the intended billing model. Contact sales if you want to participate in the early-access pilot.

The planned model: self-hosted deployments report aggregate usage via an HMAC-signed telemetry agent. The agent batches counters and tolerates up to 72 hours offline before billing falls back to the contracted minimum.

TELEMETRY_ENDPOINT=https://billing.palveron.com/ingest
TELEMETRY_HMAC_KEY=...
TELEMETRY_INTERVAL_SECONDS=3600

No prompts, payloads, or PII will ever leave the customer environment — only aggregated counts.

What's not billed

LLM tokens — captured for observability and cost estimation only
Agents — register as many as your plan permits, no per-agent fee
Team members — limited by tier (see Tiers & Limits)
Blockchain anchoring — the included allowance and billing model depend on the tier's anchoring configuration (managed wallet vs. bring-your-own-wallet); see the pricing page

For current pricing, visit palveron.com/pricing.

On this page