Skip to main content
Pylva Cloud plans meter three things: telemetry events per month, distinct end-users (unique customer_id values), and data retention. Self-hosted workspaces do not use a commercial Pylva plan; they use explicit operator-configurable limits described below.

​
Plans

Current pricing is always at pylva.com/pricing.

​
What happens at the cap

When a workspace crosses 80% of its monthly event cap, Pylva sends a warning notification. At the cap:
  • POST /api/v1/events rejects new telemetry with HTTP 403 and the error code TIER_LIMIT_REACHED (not a 402). The message names your tier, how many events you have used, and when ingestion resumes:
  • Responses include an X-Pylva-Tier-Usage: <current>/<limit> header so clients can see where they stand.
  • Your application keeps working. The SDK fails open by design: provider calls proceed, only the telemetry is rejected. You lose cost visibility for the rest of the window, not production traffic.
  • Ingest resumes automatically when the monthly window resets, or immediately after an upgrade.

​
Start or change a plan

Choose a plan from pylva.com/pricing: Payment happens in the browser through the checkout flow. If an AI agent is doing your integration, it should hand these links to a human rather than collect payment details.

​
Retention

Telemetry events age out per the plan’s telemetry retention window. Billing records (usage summaries used for invoicing your end-users) are kept for the longer billing-record window, so changing plans changes how far back dashboards can look.

​
Self-hosting

Self-hosted workspaces are active through the explicit self_hosted entitlement source; they are not assigned Pro, Scale, or Enterprise. The open-source build starts with these finite defaults:
  • 10,000,000 telemetry events per month (SELF_HOSTED_MONTHLY_EVENTS_LIMIT).
  • 500 distinct end-users (SELF_HOSTED_MAX_CUSTOMERS).
  • 365 days of telemetry retention (SELF_HOSTED_TELEMETRY_RETENTION_DAYS).
  • 365 days of billing-record retention (SELF_HOSTED_BILLING_RETENTION_DAYS).
Event-cap enforcement is enabled by default (ENABLE_EVENT_LIMITS=true) and produces the same 403 TIER_LIMIT_REACHED behavior described above. Operators can change the self-hosted limits to match their capacity; setting ENABLE_EVENT_LIMITS=false is an explicit opt-out from the monthly event cap, not a commercial plan assignment. See Open Source And Hosted for the full hosting model.