LogFlux uses per-event pricing across three categories based on the type of data you ingest. All plans include zero-knowledge encryption, all integrations, and full API access.
For current pricing, visit logflux.io/pricing.
Plans
| Free | Starter | Team | Business | Professional | |
|---|---|---|---|---|---|
| Monthly | $0 | $19 | $49 | $99 | $199 |
| Yearly | – | $15/mo | $39/mo | $79/mo | $159/mo |
| Events | 100K | 2M | 10M | 50M | 200M |
| Traces | 10K | 200K | 1M | 5M | 20M |
| Audit | – | 20K | 100K | 500K | 2M |
| Retention | 7 days | 14 days | 30 days | 90 days | 365 days |
| Users | 1 | 3 | 10 | Unlimited | Unlimited |
EUR and USD use the same numbers. EUR prices include VAT; USD prices are net.
Annual billing saves approximately 20%.
Event Categories
Every log entry you send to LogFlux has an entry type (1-7). These map to three pricing categories:
Events (standard)
Covers most log data. Includes:
- Log (type 1) – Application logs, system logs, structured messages
- Metric (type 2) – Numeric measurements, counters, gauges
- Event (type 4) – Application events, user actions, business events
Traces
For distributed tracing and telemetry. Includes:
- Trace (type 3) – Distributed trace spans (E2E encrypted)
- Telemetry (type 6) – E2E encrypted telemetry data
- TelemetryManaged (type 7) – Server-side encrypted telemetry (S3 SSE-KMS)
Audit
For compliance and immutable record-keeping:
- Audit (type 5) – Compliance logs with Object Lock (GOVERNANCE mode, 365-day undeletable retention)
The ratio across tiers is approximately 100:10:1 (Events : Traces : Audit), reflecting the different storage and compliance costs.
Note: The Free tier does not include audit events.
Overage
When you exceed your plan’s included quota, behavior depends on your settings:
| Category | Per 100K events | Per 1M events |
|---|---|---|
| Events | $0.30 | $3.00 |
| Traces | $1.50 | $15.00 |
| Audit | $5.00 | $50.00 |
How overage works
- Free plans: Ingestion is blocked (HTTP 402) when any category quota is exceeded.
- Paid plans (overage disabled): Ingestion is blocked when any category quota is exceeded.
- Paid plans (overage enabled): Ingestion continues. Overage usage is tracked and billed at the end of the billing cycle.
- Warning: An email notification is sent at 80% usage (once per month per category).
- Reset: All counters reset on the 1st of each month.
Data Retention
Each plan includes automatic data retention with TTL management:
| Plan | Retention |
|---|---|
| Free | 7 days |
| Starter | 14 days |
| Team | 30 days |
| Business | 90 days |
| Professional / Usage-Based | 365 days |
- Retention policies update automatically when you change plans
- Expired data is cleaned up daily at 2 AM UTC
- Audit entries (type 5) always have 365-day Object Lock retention regardless of plan
Entry Type Reference
When sending logs via multipart/mixed, the X-LF-Entry-Type header determines which pricing category each entry counts toward:
| Type | Name | Category | Encryption |
|---|---|---|---|
| 1 | Log | Events | E2E (AES-256-GCM) |
| 2 | Metric | Events | E2E (AES-256-GCM) |
| 3 | Trace | Traces | E2E (AES-256-GCM) |
| 4 | Event | Events | E2E (AES-256-GCM) |
| 5 | Audit | Audit | E2E (AES-256-GCM) + Object Lock |
| 6 | Telemetry | Traces | E2E (AES-256-GCM) |
| 7 | TelemetryManaged | Traces | Server-side (S3 SSE-KMS) |
If no entry type is specified, type 1 (Log) is used by default.
Monitoring Usage
Track your usage in the LogFlux dashboard:
- Go to dashboard.logflux.io
- Navigate to Settings → Usage
- View per-category breakdowns for the current and previous months
Frequently Asked Questions
Can I switch plans? Yes, you can upgrade or downgrade at any time from the dashboard. Changes take effect immediately. When upgrading, retention policies are updated and new data benefits from the longer retention period.
What happens when I downgrade? Your retention period adjusts to the new plan’s limit. Data older than the new retention window will be cleaned up during the next daily cleanup run.
Do unused events roll over? No. Event quotas reset on the 1st of each month.
How are events counted?
Each entry in a multipart/mixed request counts as one event. A request with 50 MIME parts counts as 50 events. The category is determined by the X-LF-Entry-Type header on each part.
Related Documentation
- Authentication Setup – API keys and PATs
- Security & Encryption – Zero-knowledge architecture
- Getting Started – Quick start guide