Complete Observability. Straight From Logs.

save 80% in days – get better answers for years

80% cheaper
200 GB/s
Start Now
All metrics
EU hosted

Problems we solve

As products scale, logs and metrics explode in volume — and costs quickly become unsustainable. Teams spend precious engineering time cutting cardinality and trimming data just to stay afloat.

All too often, this leads to blind spots in production. When an incident happens, the data you removed before is exactly what you needed. See below how logging24 solves this conundrum:

Your monitoring costs too much?

Reduce costs up to 80% and more within days.

Logging24 costs about a fifth of other observability solutions:
€0.25/GB·month for storage, €50/PB scanned for compute.

We can offer these prices thanks to novel algorithms and an implementation hand-crafted with attention to detail — and performance.

Metric cardinality is a constant trouble?

Never worry about cardinalities again.

Query metrics from logs after arbitrary filtering. No predefined dimensions. No indices. No trade-offs.

By filtering on plain logs first and then aggregating millions of data points per second, logging24 sidesteps the cardinality problem entirely. Every text-filter is a dimension.

Need to get your data out of US control?

Your logs are staying 100% in the EU.

We run dedicated servers geo-redundantly in Germany and Finland, leased from EU-registered and EU-controlled hosting providers.

All logs are encrypted in transit and at rest with keys unknown to the hosting providers. All administrative commands are logged and audited.

logging24 in Numbers

200 GB/s
scan speed

4 years
without incident

25482817092151
bytes stored

Logs expire before tickets are complete?

Keep logs as long as needed.

At 20% the price, you can keep logs around much longer and still pay less.

Our oldest logs are from 2021. And we query them with the same performance as those from yesterday.

Every new observability signal requires engineering effort?

Answer all questions from existing logs.

With the flexibility of regular expressions, logging24 can extract errors, metrics and correlations from the logs you already have, no matter their format.

Metric generation doesn't need to be planned, either. Instead you query whatever metric the situation requires — even from logs written long ago.

Your self-hosted observability is too slow?

Never care about observability resources again.

By sharing a large CPU pool across all our clients, logging24 delivers a maximum of compute exactly when you need it.

Of course, we also take care of upscaling, capacity planning, backups, and all the other little details necessary to keep your observability up and running.

Our Onboarding Process

1

Contract is signed.

NDA, GDPR roles, primary contact points clarified.

We help you configure log forwarding.

Webservers, applications, system logs, embedded devices.

2
3

You get the answers you need.

All logs available with maximum flexibility and speed.

Built by Experts

Jens-W. Schicke-Uffmann

  • 22 years of observability experience
  • 17 international publications
  • PhD in computer science

Felix Klose

  • 24 years of observability experience
  • 20 international publications
  • Diploma in computer science

Unsure?

Start today.

Trial is free. Do it before the next incident. Start logging today. Be ready for tomorrow.

Frequently Asked Questions

General

logging24 is a modern observability platform based on log management that lets you collect, store, and query logs at any scale and for any purpose. Traditional solutions require you to collect and pre-index logs, metrics and traces separately. Instead, logging24 uses massively parallelized regex search, giving you full flexibility without sacrificing speed.
logging24 is designed for DevOps teams, SREs, developers, and IT departments who need reliable observability without the operational overhead. Whether you're running a single server or managing terabytes of logs across distributed systems, logging24 scales with you.
Traditional log management requires you to define schemas, create indexes, and plan your queries in advance. logging24 takes a different approach: we store your logs as-is and use parallelized regex search at query time. This means:
  • No preprocessing or filtering required
  • Query any field without pre-planning
  • Handle format changes without losing data
  • Extract metrics from any numeric field on-the-fly
All data is hosted on dedicated servers in the European Union — specifically in Germany and Finland.

Getting Started

Getting started is simple: Sign up for a free evaluation account, create a write token in the web interface, install our forwarder on your servers, and start querying your logs. Most users are up and running within minutes.
You need to install our log forwarder on the machines generating logs. We offer multiple options:
  • native Linux binary — recommended for production, high performance
  • multi-arch Python tool — convenient cli, multi-architecture support
  • Fluentd plugin — if you're already using Fluentd
  • nothing - just point your existing promtail or rsyslogd at our ingest nodes
No! logging24 works with your existing log output. There's no need to add SDKs, change log formats, or instrument your code. Simply forward your existing logs to logging24 and start querying.
Most users complete initial setup in under 10 minutes. After receiving an account, installing the forwarder is straightforward. Logs appear in the web interface within seconds of being forwarded.

Technical

logging24 supports any text-based log format — structured (e.g. JSON) or unstructured plain text. Since we don't require pre-indexing or a schema definition, you can mix formats freely even within the same log stream.
logging24 uses high performance regular expression search across your stored logs. When you run a query, we pre-filter by time range and log stream, then scan the relevant log segments in parallel across our server fleet. Results are cached transparently for faster repeat queries.
We support a comprehensive set of the usual regex constructs including character classes, quantifiers, groups, alternation, anchors, and special escapes. Additionally our syntax allows logical-and and negation. We also support capture groups to extract numerical data for statistic analysis at full speed.
You control retention on a per-log-stream basis. The minimum retention period is 30 days, but you can configure longer periods as needed.
Security is built into every layer:
  • All data is encrypted in transit (TLS) and at rest (dm-crypt)
  • Access tokens use secure hashing — we never store the actual token
  • Role-based access controls (Writer, Reader, Admin)
  • Prefix-based permissions for fine-grained access
  • EU-based infrastructure
  • We host only at ISO 27001 certified datacenters
  • Our systems are fully audit-logged

Pricing & Billing

Our pricing has two components: Storage (€0.25 per gigabyte per 30 days of retention) and compute (€50 per petabyte scanned). Your evaluation period is completely free.
Yes! The evaluation period is completely free with no credit card required. You get full access to all features so you can properly evaluate logging24 on your actual logs.
Use our cost estimator on the pricing page. Enter your daily log volume, retention period, and expected query patterns to get an accurate monthly cost estimate.

You only pay for what you use — there are no overage penalties or surprise charges. Your bill scales linearly with your actual usage.

If needed, we can help you estimate your usage during onboarding and agree on a monthly price cap. Even then, we will never interrupt your log delivery without talking to you first.

You are never locked in. You can adjust retention periods, modify log streams, or stop forwarding logs anytime. Your data belongs to you. You can cancel your account without notice, effective end-of-month to keep a regular billing cycle.

Performance & Scale

logging24 is designed to scale from gigabytes to petabytes. Our architecture distributes storage and query processing across many nodes, allowing us to handle massive log volumes without performance degradation.

The apparent query speed increases as more data is scanned. This is due to fixed latencies at query startup. Queries over large amounts of data usually proceed at 100s of GB/s. Naturally, overall duration will increase once the scanned data set becomes large enough.

By choosing the ratio between compute and storage, we can control the maximum query duration. Our current deployment strategy aims at 30s for a hypothetical full scan of all stored log data. As the resources are shared between customers, an analysis over all your logs, ever, will complete significantly faster.

No. Our forwarder is designed to be lightweight, non-intrusive and asynchronous. It uses minimal CPU and memory and includes resource limits to prevent impact on your production systems. You can also configure CPU quotas and memory limits in the systemd service file.
The forwarder includes buffering and retry logic. If the network connection is lost, logs are buffered locally and forwarded once connectivity is restored. For critical systems, we recommend configuring appropriate buffer sizes.

Support

We support organizations of every size — from early-stage startups to global enterprises. All customers receive full access to our comprehensive documentation and benefit from our expertise. For direct assistance, our expert team is available via email and phone during business hours. Enterprise clients benefit from priority response times and dedicated account management. Contact us to build a support plan that matches your scale.
Start with our Getting Started guide and documentation. If you need personalized help, contact us via email or phone — we're happy to assist.
Yes, we offer professional services for complex deployments, including architecture review, performance optimization, and custom integrations. Contact us to discuss your needs.

Contact | Terms of Service | Privacy | Security
© quuxLogic Solutions GmbH. Tel: +49 531 18059926 Mail: info@logging24.com