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

Plan	Included	Overage
Community	1,000 requests / month	Hard-stop at 1,000
Pro	10,000 requests / month	Top-up packs or auto-overage
Business	100,000 requests / month	Top-up packs or auto-overage
Enterprise	Negotiated request volume + dedicated SLA	Contracted overage rate

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 = two months free).
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/stripe/checkout.

Stripe Customer Portal

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

GET /api/v1/stripe/portal

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

Top-up payments for overages

Pro and Business plans can purchase top-up packs when monthly quota runs low — no plan change required.

Pack	Additional requests
Small	+5,000
Medium	+25,000
Large	+100,000

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

Auto-overage (Business / Enterprise)

When auto-overage is on, 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?from=2026-05-01&to=2026-05-31 returns daily totals plus per-agent breakdown.
Webhooks — usage.threshold_reached fires at 80% 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 — included on Business and Enterprise; Pro pays a minimal per-anchor fee

For current pricing, visit palveron.com/pricing.

On this page