staxlens documentation
Choose a version
Version 0.1.x
StaxLens pricing plans #
StaxLens is monetized as a per-node subscription with a self-hosted license option and retention-based tiers. This page summarizes the model; the binding terms are in the licensing and pricing policy.
Plans #
| Plan | Billing | Retention | Multi-host | Notes |
|---|---|---|---|---|
| Cloud | Per node / month | 1 week | Yes | Hosted collector, no infrastructure to run |
| Cloud Plus | Per node / month | 1 month | Yes | Higher retention for trend analysis |
| Cloud Annual | Per node / year | 1 year | Yes | Long retention; best value for steady fleets |
| Self-hosted | One-time / annual license | Your storage | Yes | Runs the same collector on your infrastructure; you own the data |
Per-node subscription #
Each monitored host is one node. Billing is per active node per billing period. Adding a host is just deploying the agent with a tenant token; the node count reconciles against the subscription.
Self-hosted license #
The self-hosted plan is the same collector binary with a license key instead of a cloud subscription. It exists for tenants that must keep metrics inside their own network (regulatory or air-gapped-adjacent needs). The agent collection code is shared with StaxMonitor, so on-prem teams can standardize on one agent.
Retention tiers #
Retention is the time window the collector keeps raw samples before downsampling or dropping. Higher tiers keep more history for longer-range trend views. The MVP store keeps raw samples within the window and downsamples wide queries; the billing tier controls the configured window.
Notes #
- Alerts and dashboards are included in every plan.
- Pricing is finalized at launch and listed on StaxStore.
- Not MIT-licensed; proprietary commercial software.