Choose Free when you are still small on purpose
Free is the right fit when you are validating Liteguard with a compact team and a clearly bounded workspace.
- Up to 3 active seats
- Up to 100 configured guards
- Up to 10 routed alerts
Liteguard plans are based on the shape of your workspace, not on hidden event-metered surprises. Free covers up to 3 seats, 100 configured guards, 10 routed alerts, 10 million monthly guard checks, and 1 GB of signal telemetry. Team becomes a flat $30 per workspace per month after beta, and during beta platform charges are waived while we still show plan fit before billing ever turns on.
Start with the plan that matches your workspace shape. Use the detailed comparison below only when you want to verify the exact line items.
Free is the right fit when you are validating Liteguard with a compact team and a clearly bounded workspace.
Team is the default growth path for production teams that have outgrown Free but do not need enterprise buying or governance requirements.
Enterprise is not the high-traffic tax. It exists for identity, governance, contracts, retention, and support expectations.
All plans are currently free during beta. The point of the pricing page now is clarity: what each plan is for, what will count later, and why Team should become a flat workspace decision instead of a pricing math problem.
For solo builders, small founding teams, and early products validating Liteguard.
For production teams that outgrow Free but do not need enterprise operating requirements.
For SSO, governance, contracts, retention controls, and higher-touch support expectations.
On smaller screens, use the summaries above first. The full line-item comparison stays below if you need to verify an exact boundary.
|
Detailed comparison
Review the exact limits, usage, and feature boundaries for each plan.
|
For founders
Free
$0
Beta and long-term free tier
For solo builders, small founding teams, and early products validating Liteguard. |
Most natural upgrade
Team
$30/mo after beta
Free during beta, $30 per workspace with optional Capacity Packs after launch
For real production teams that outgrow Free but do not need enterprise operating requirements. |
For enterprise needs
Enterprise
Talk to us
Custom terms based on enterprise needs
For SSO, governance, contracts, retention controls, and higher-touch support expectations. |
|---|---|---|---|
| Active seats Active workspace members count toward plan fit. | Up to 3 | Unlimited | Unlimited |
| Configured guards Stored adopted guards across the workspace. | Up to 100 | Unlimited | Unlimited |
| Routed alerts Alerts with routing enabled, not every possible alert object. | Up to 10 | Unlimited within normal platform-safety bounds | Unlimited |
| Included guard checks / month Visible runtime allowance before any extra usage purchase is needed. | 10 million | 100 million | Custom committed usage |
| Included signal telemetry / month Signal payload volume included before additional usage is required. | 1 GB | 25 GB | Custom committed usage or BYO storage |
| When usage exceeds the included amount How heavier runtime usage is handled once the included envelope is exhausted. | Not available on Free | Capacity Packs: $15 each for another 100 million checks and 25 GB of telemetry | Custom committed pricing |
| Usage visibility How clearly Liteguard shows why a workspace fits a plan. | OKProject-level and workspace-level usage views | OKProject-level and workspace-level usage views | OKProject-level and workspace-level usage views |
| Warnings before limits What should happen before a plan boundary blocks an action. | Warnings before the next seat, guard, or routed alert is blocked. | Warnings and plan-fit messaging should still be visible, even though Team removes the core Free caps. | Handled through commercial and support process rather than Free-limit gating. |
| Heavy-usage path How operationally heavy workloads are treated. | Tracked separately for fair-use and platform protection. Not the main packaging meter. | Can still remain Team. Capacity Packs cover ordinary overages, and only very heavy sustained throughput may trigger fair-use controls or a capacity review without auto-forcing Enterprise. | Enterprise is not required just because traffic is high; it is for enterprise operating needs. |
| Custom CNAME branding Use your own subdomain for customer-facing Liteguard surfaces. | Not included | OKIncluded | OKIncluded |
| Security remediation alerts Operational guidance when Liteguard identifies a remediation path. | Not included | OKIncluded | OKIncluded |
| Security auto-remediation Automated response flows when a supported mitigation is available. | Not included | OKIncluded with standard controls | OKIncluded with advanced policy controls |
| Bring your own telemetry storage Store high-volume telemetry in customer-managed infrastructure. | Not included | Not included | OKIncluded |
| Enterprise features When SSO, governance, and similar requirements enter the picture. | Not included | Not included by default | SSO, governance, retention controls, contracts, and custom support expectations. |
| Open source path How open source teams can ask for more. | Email [email protected] for review. | Email [email protected] for review. | Open source Enterprise access can be granted through manual review. |
| Beta grandfathering What early adopters may keep after beta. | Active beta workspaces may qualify for grandfathered Enterprise feature support later. | Active beta teams may qualify for grandfathered Enterprise feature support later. | Grandfathered feature access may apply, but final commercial terms still follow the paid plan model. |
The first packaging model intentionally uses a small number of visible product objects. That keeps pricing legible and avoids a hidden-meter feeling.
These are the numbers that determine whether a workspace is still a Free fit or has naturally become Team.
Free and Team include explicit runtime usage, and ordinary growth is handled through simple Capacity Packs instead of surprise reclassification or hidden event billing.
Important: Liteguard still protects shared infrastructure with per-workspace fair-use controls. If one workspace becomes unusually heavy, we may throttle or review that workload to protect everyone else. That is an operational safeguard, not a hidden pricing trick. A small team with a heavy workload can still be a Team customer.
No hidden raw-event meter. Team is a flat workspace price with explicit monthly checks and telemetry included, and Capacity Packs are simple fixed add-ons rather than surprise event billing.
You can still stay on Team. Capacity Packs cover ordinary extra demand, and if the workload becomes unusually heavy, Liteguard may still apply fair-use protections or a capacity review without quietly converting you into Enterprise.
Platform charges are waived. The product should still show which plan fits your workspace and where you are against limits so pricing is not introduced as a surprise later.
Liteguard should warn first, then block the next seat, configured guard, or routed alert that exceeds the Free limit until the workspace upgrades or reduces usage.
Yes. Email [email protected] and request an open source review. Early on, that approval path can stay manual.
Active beta teams may qualify for grandfathered Enterprise feature support, but final commercial terms still apply once paid plans begin.
Feature flags, rate limits, observability, and CVE response. One dependency.