Layered
A workspace gets the server's limits, then its plan's, then any overrides set for that workspace alone. A field left unset falls through; a limit of zero removes it.
Pricing
Plans are sets of limits.
A plan bounds ingest, retention, retained data and members for a workspace. The structure below is what the server enforces today. Prices have not been set.
Pricing not yet published
Contact your operator about plans. This server has no contact address configured.
What a plan limits
Each plan sets some or all of these. The defaults are the server's provisional limits, used when a plan leaves a field unset.
| Limit | What it bounds | Server default |
|---|---|---|
| Ingest volume | Compressed bytes of accepted uploads per UTC day. | 2 GiB per day |
| Ingest rate | Sustained upload requests per minute. | 1200 per minute |
| Raw telemetry retention | How long raw points, profiles, spans, logs and issues are kept. Evidence, investigations, comparisons, runs and captures are not removed by it. | 7 days |
| Retained data | Evidence and investigation text, original capture bytes and staged uploads. | 256 MiB |
| Members | People in the workspace. | 25 |
Defaults are provisional placeholders, not a plan offer. A server operator can change them.
How limits apply
Stated when reached
A request that would exceed a limit is refused with a message naming the limit, the current use and the amount requested.
Metered
The server keeps a daily usage ledger: peak seats, seat-days, peak retained bytes, retained byte-days and processed bytes. Its invoice preview has no prices.
Running it yourself
The server is a single Go binary with SQLite storage. The limits above apply to a self-hosted server in the same way; its operator assigns plans with the plan command.