The full power of TDengine, now free forever for up to 5,000 tags.

Explore More

190× Faster Dashboards: How Autonoma Powers Industrial Digital Services with TDengine

Jim Fan

November 12, 2026 /

Serving 10 machinery manufacturers, 800+ companies and subaccounts, and 30,000 sensors worldwide—with a 30-query dashboard loading in 0.16 seconds versus 30 seconds for InfluxDB in Autonoma’s benchmark.

Lindner Merak 2800 shredder at a wood recycling facility, with a banner highlighting approximately 190× faster dashboard loading.

Lindner Merak 2800 at a wood recycling facility. Image: Lindner.

Based in Austria, Autonoma helps machinery manufacturers stay connected to equipment operating around the world. Some of those machines are large enough to crush an entire car. Others recycle plastics, compress scrap metal, shred paper or filter air—often thousands of kilometers from the companies that built them.

When those machines develop a problem, traditional service can mean sending a specialist across a country—or an ocean. Autonoma gives manufacturers a different way to work: see how a machine is running, examine historical measurements and diagnose issues remotely, often before a site visit becomes necessary.

Underneath that customer experience is TDengine, the time-series engine that has grown with Autonoma from an early product idea into a global industrial software platform.

Built for machines that never behave exactly alike

Florian Bauernfeind, co-founder of Autonoma, faced a problem familiar to machinery OEMs: two assets may be the same model but collect completely different measurements. One sensor reports every second, another only when a value changes, and customers can add new signals as their equipment evolves.

Autonoma needed that flexibility without paying for it in slow queries or an ever-expanding infrastructure footprint. TDengine’s supertables and child tables made it possible to represent one highly dynamic data stream per table, yet still query related machines together.

Florian Bauernfeind

Co-Founder

Portrait of Florian Bauernfeind, co-founder of Autonoma.

“The possibilities we have with supertables were a real eye-opener. If done correctly, they enable analytics across a big set of assets without complex business logic to prepare queries.”

Lindner NEXUS asset details for a Merak 2800 shredder, with operating data, machine status, sensor streams and service options.

Lindner NEXUS: an asset-level view of a Merak 2800 machine, showing operating context and independently configured data streams.

Growing a global industrial customer platform

Autonoma began as a project developed alongside its founders’ regular jobs. TDengine gave the team a flexible time-series foundation for building its product and onboarding customers. As the business grew, that foundation became central to delivering responsive digital services for machinery manufacturers.

Today Autonoma supports around 10 principal machinery-manufacturer customers and more than 800 companies and subaccounts. Its platform monitors approximately 30,000 sensors around the world, with roughly 600 additional industrial assets being added each year.

Autonoma global asset map with industrial equipment location markers across Europe, the Americas, Asia and Australia.

Autonoma’s global asset map shows machinery and customer sites across multiple continents.

Publicly named Autonoma customers include Lindner Recyclingtech, Scheuch, Komptech, Next Generation Recycling Machines (NGR), RUBBLE MASTER, EUROpress Umwelttechnik, Piller Group and GIG Karasek. These machinery manufacturers span recycling, heavy equipment and industrial processing.

30,000
sensors monitored
600
new assets each year
5 years
raw-data access

TDengine at the center—not in place—of Autonoma’s platform

Autonoma creates the machine-specific processing, permissions, white-label interface, operational alerts and customer-facing digital services. TDengine Enterprise is the fast, reliable time-series data foundation beneath those experiences.

Industrial measurements flow into Autonoma’s platform and are written to TDengine in efficient batches. The historical readings power dashboards, state-duration calculations, asset KPIs, remote diagnostics and long-range trend analysis. The database layer can focus on ingestion and retrieval, while Autonoma stays focused on the application each machinery manufacturer wants to deliver to its customers.

Lindner NEXUS Merak 2800 dashboard showing the main-drive current trend, production hours, rotor speed and other machine KPIs.

Lindner NEXUS: real operational measurements, operating-hour KPIs and trend data in a customer-facing machine dashboard.

The responsiveness is important in everyday service work. Engineers looking into an equipment fault need fast answers while a customer is still on the phone, not another lengthy wait between charts.

Five years of raw data, fast queries, lower infrastructure cost

Autonoma wanted to preserve detailed history instead of relying exclusively on pre-aggregation. With TDengine’s storage efficiency and query capabilities, it reports access to up to five years of raw machine data while keeping dashboards responsive, typically around one to two seconds in its customer application.

Based on Autonoma’s longer-term evaluation, the company estimates a 70% reduction in five-year time-series storage total cost of ownership versus InfluxDB, alongside roughly 50% lower infrastructure cost than a dedicated InfluxDB installation. These are Autonoma’s economic estimates, separate from the controlled performance benchmark below.

Lindner NEXUS Komet 2800 dashboard showing machine-state timelines, operating hours and an equipment performance indicator.

Lindner NEXUS: machine-state timelines, operating-hour trends and an equipment performance indicator shown together.

Measured performance: TDengine 3 vs. InfluxDB 3

To verify its experience, Florian’s team repeated a controlled comparison on November 10, 2026, using an identical dataset and a workload designed to reflect Autonoma’s actual data model. They compared TDengine 3.3.8 with InfluxDB 3.12, each tested on the same host and in the configuration described below.

≈190x
faster dashboard opening
14×
faster history backfill
2.9×
less disk space used

Benchmark configuration

One host with 2 vCPU and 8 GB RAM; the engines ran one at a time, with the load generator on the same host. The dataset comprised four customer accounts with 100 data streams each, 60 days of data and 31.3 million rows. Both engines received byte-identical data (70% numeric, 15% machine state, and 5% each text, events and geo), sampled once per minute. Results were checked for equivalent bucket counts, sums and state-window outputs. TDengine used default settings, while InfluxDB used a file-backed object store with an increased query-file limit. Queries were run 20 times; dashboard bursts were repeated 15 times.

Ingestion, latency and storage

TestTDengine 3.3.8InfluxDB 3.12Result
30-query dashboard opening0.16 sec30 secTDengine is ~190× faster
History backfill, 10k-row batches / 16 writers1,661,672 rows/s118,595 rows/sTDengine is 14× faster
10k rows/s sustained: p95 write latency25 ms144 msTDengine has ~5.8× lower latency
40k rows/s sustained: p95 write latency62 ms; target met~31,900 rows/s; target not metTDengine met target
Disk for 31.3M rows, excluding WAL189 MB544 MBTDengine uses 2.9× less disk
Download Autonoma’s full TDengine 3 vs. InfluxDB 3 benchmark report

At the 40,000-rows-per-second target, the InfluxDB test reached the target only with an alternative acknowledgement setting that reported success before its write-ahead log was persisted; the benchmark did not treat that mode as equivalent durability.

Query performance across Autonoma workflows

The dashboard result is not an isolated synthetic point. Longer-range aggregations, cumulative sums and machine-state windows produced the largest differences, while simple recent-history queries were much closer. The chart summarizes selected latency ratios from the same 20-run query tests.

Bar chart comparing InfluxDB 3 and TDengine 3 query latency in Autonoma's benchmark, with workload-specific ratios ranging from 1× to 549×.

Source: Autonoma’s November 2026 evaluation. A ratio of 1× means similar speed; larger ratios indicate lower query latency with TDengine. Results are specific to this workload.

Why the data model matters

Autonoma’s model has five common supertable types—numeric, text, state, events and geographic data—with a child table for each independently configured stream. That architecture maps directly to TDengine. In the tested InfluxDB configuration, the same streams had to be represented differently, affecting the fit for assets with hundreds of dynamically defined signals.

The results reflect Autonoma’s dataset, versions, hardware and settings; they do not predict performance for every workload or configuration. Test source: “TDengine 3 vs InfluxDB 3,” Florian Bauernfeind, November 10, 2026.

A partnership proven when it mattered most

When Autonoma needed urgent help recovering valuable customer data, the stakes were immediate. Machinery manufacturers depended on that history to support equipment already operating around the world. Preserving those records meant protecting not just technical information, but the customer relationships and service commitments built around it.

TDengine responded quickly. Senior engineers worked directly with Florian to assess the situation, establish a recovery plan and restore the affected history. With engineering teams in North America and Asia providing around-the-clock support, Autonoma received hands-on assistance across time zones, including nights and weekends. Florian says the recovery estimates proved accurate, giving his team a clear plan and dependable progress when it mattered most.

Florian Bauernfeind

Co-Founder

Portrait of Florian Bauernfeind, co-founder of Autonoma.

“The incident showed us that TDengine really cares about its customers. For me, this is beyond a classical customer relationship—more of a partnership.”

Autonoma now operates TDengine Enterprise with three data nodes and three replicas. Combined with deployment guidance, encryption and direct access to engineers, this setup provides a supported foundation for customer-facing operations. The value is not just a resilient database—it is a partnership that can grow with the business.

A strategic foundation for long-term growth

For David Gumpinger, Managing Director and Co-Founder of Autonoma, the relationship with TDengine is as much about customer commitments as technology. Predictable costs, strong data security, EU self-hosting and responsive engineering support give Autonoma a framework for growing its platform while retaining control of its infrastructure.

David Gumpinger

Managing Director & Co-Founder

Portrait of David Gumpinger, managing director and co-founder of Autonoma.

“A strong data backbone that scales across industrial use cases is an essential building block of our Digital Customer Platform. TDengine’s security capabilities and expanding AI functionality help us position Autonoma at the forefront of digital innovation in the machinery industry.”

The self-hosted model is important to Autonoma, which wants to keep its services and customer data hosted in the EU while reducing the operational risk of supporting a business-critical database alone.

Engineering support across two continents—even nights and weekends

A critical incident cannot wait for the next business day. Autonoma’s direct Microsoft Teams support channel connects Florian with TDengine’s teams in North America and Asia, providing around-the-clock coverage across time zones. During the recovery effort, engineering specialists helped investigate the problem, worked through the technical details with Autonoma and provided the rapid, credible answers its customers needed.

Florian Bauernfeind

Co-Founder

Portrait of Florian Bauernfeind, co-founder of Autonoma.

“With TDengine, we can host the system ourselves, lower the operational risk and still sleep well on weekends.”

That level of responsiveness matters as much as the software itself. Florian reports fast, technically competent responses even on weekends and late at night. The team did not merely acknowledge an urgent ticket—it helped restore valuable customer history and validate the Enterprise production setup. For David, that means confidence in an accountable partner while Autonoma retains control of its EU-hosted environment.

What the machinery customer actually sees

Autonoma’s customer-facing platform adapts information to the role: machine operators need live states and alarms; service teams investigate detailed sensor history and error codes; managers want utilization and productivity KPIs. The system gives manufacturers one branded digital service around each machine, even when equipment is operating far from the factory.

Autonoma digital-twin demonstration showing a 3D batch-mixing plant model with a popup for tank level, temperature and agitator speed.

Autonoma digital-twin demonstration: interactive equipment context alongside the operational views powered by its industrial data platform.

For machine builders with equipment scattered across continents, remote diagnosis can prevent unnecessary site visits, shorten service interactions and strengthen the relationship after a machine is sold.

Industrial filtration equipment from Scheuch.

Industrial filtration equipment from Scheuch, one of the machinery manufacturers using Autonoma.

Next: fleet-wide analytics with TDengine IDMP

Autonoma is now evaluating TDengine IDMP — the industrial analytics and AI layer that complements TDengine TSDB — to extend the value of its existing customer platform. The distinction matters: Autonoma continues to provide the operational experience, while IDMP could help OEM engineers, after-sales teams and R&D staff compare performance across whole fleets.

The next generation of questions goes beyond whether one machine is overheating. Which of hundreds of similar assets is behaving differently? How does operating environment influence performance? Which customers should the service team contact first? Many of these manufacturers do not have dedicated data scientists; easier analytics could let existing service staff cover more assets and make better decisions.

Autonoma has also experimented with zero-shot forecasting, including equipment operating hours, temperature and vibration, and is exploring how weather and other covariates could help deliver more reliable anomaly detection across climate zones. These applications remain under evaluation, rather than production results claimed in this case study.

One product decision, a long-term partnership

Autonoma started with a clear technical need: store flexible, high-volume machine data quickly and economically. TDengine has grown with the business, providing a supported Enterprise foundation for security, availability and growth. Measured performance on Autonoma’s own data model — and support from teams across North America and Asia—helps the company deliver better customer experiences while keeping control of its infrastructure. For machinery manufacturers, the result is faster answers and more value from equipment long after it leaves the factory.

Build Your Industrial Customer Platform

Looking to help machinery customers monitor equipment and investigate issues remotely? Talk to our team about using TDengine to manage machine data and deliver responsive dashboards.

About Autonoma

Autonoma is an Austria-based provider of a white-label Digital Customer Platform for industrial machinery and plant manufacturers, helping OEMs deliver remote monitoring, service experiences and data-enabled customer relationships. Learn more at autonoma.cloud.

  • Jim Fan
    Jim Fan

    Jim Fan is the VP of Product at TDengine. With a Master's Degree in Engineering from the University of Michigan and over 15 years of experience in manufacturing and Industrial IoT spaces, he brings expertise in digital transformation, smart manufacturing, autonomous driving, and renewable energy to drive TDengine's solution strategy. Prior to joining TDengine, he worked as the Director of Product Marketing for PTC's IoT Division and Hexagon's Smart Manufacturing Division. He is currently based in California, USA.