Tiers & Limits

Palveron has four tiers. Pick by request volume, team size, and the features you need — every tier ships the core governance engine; gates are on advanced capabilities.

Quick comparison

The tiers differ in monthly request volume, rate limits (RPM), agent and policy capacity, team size, compliance-framework coverage, and trace retention. The authoritative, always-current comparison lives on the pricing page — it renders directly from the live tier configuration, so numbers there can never drift from what is actually enforced.

Support scales with the tier — from community support to a dedicated contact on Enterprise. Business and Enterprise carry an uptime SLA (contractual on Enterprise).

Features by tier

Feature gates are part of the live tier configuration and can change until launch — a hardcoded matrix here would inevitably drift. The authoritative, always-current feature comparison (including every gate, SLA figure, and limit) lives on the pricing page, which renders directly from the live configuration.

In broad strokes: every tier ships the core governance engine (Verify API, SDKs, Gateway Proxy, MCP Gateway, policies, traces). Higher tiers add the browser-side enforcement surface (Browser Guard, Palveron Discover), compliance depth (Annex IV reports, FRIA workflow, additional screening frameworks), enterprise identity (IdP user sync), and deployment options up to dedicated infrastructure.

How limits are enforced

• Monthly request quota — counter resets at 00:00 UTC on the first of each calendar month. The dashboard surfaces usage banners as you approach the limit. What happens at 100% depends on your tier's configured limit behavior:
  • HARD_STOP — further requests return 429 RATE_LIMIT_EXCEEDED until the next reset or a top-up.
  • TOP_UP — automatically purchase the next pack size from the saved Stripe payment method.
  • OVERAGE — continue serving requests and invoice the overage at month-end (available on tiers configured for overage billing).
• RPM burst — per-key sliding window. Bursts above the RPM limit return 429 with Retry-After. SDKs honor it automatically.
• Agent and policy caps — enforced at registration. The wizard refuses to create the N+1th agent until you upgrade or delete an existing one.
• Trace retention — a retention worker runs hourly and removes traces whose age exceeds the effective retention window. Compliance exports must be made before the retention cutoff (or upgrade for longer retention).

Configure HARD_STOP / TOP_UP / OVERAGE under Settings → General → Rate limiting.

Tier changes mid-month

Upgrades take effect immediately and prorate the new monthly fee. Downgrades take effect at the next renewal — your higher quota continues until the period ends.

Cancellation and downgrades to Community preserve historical traces for the configured retention period but disable feature gates immediately (e.g. Browser Guard extensions stop receiving policy updates within ~5 minutes).