WillItSurvive

InfluxData

InfluxData builds InfluxDB, a database purpose-built for time-series sensor and metrics data.

Losing its protection
Assessed 21 July 2026 · Evidence as of 21 July 2026
The structural protection is eroding.
On the recordSince 21 July 2026 · Checkable from H2 2026 · Every call on the record Checkpoint: Next priced funding round, acquisition announcement, or 12-month silence mark since Series E
The call

InfluxData still has real customers and a shipped product, but three and a half years without new funding and rivals copying its protocol leave its position unsettled.

InfluxData makes specialized databases that store and analyze data collected over time, like sensor readings or stock prices. Rivals like QuestDB and TimescaleDB are making it easier to switch away by copying InfluxData's technical approach, and Amazon Web Services is both a partner and a potential threat, since it could absorb InfluxData's technology into its own cloud service. The company has a large base of free users and deep roots in industrial settings, but the next major financing announcement or evidence that customers are actually switching to competitors will show whether those roots are strong enough to protect the business.

Why
01
AI pressure: QuestDB and TigerData using AI-assisted migration tooling. AI coding agents can now auto-translate queries and schemas, making it easier for customers to swap to QuestDB or TimescaleDB than before. Could AI do the core job? Unlikely.
02
Bigger players: Amazon Web Services. AWS runs a managed Timestream for InfluxDB service while it shut down its own competing Timestream for LiveAnalytics in June 2025. Could a giant copy it? Yes, easily.
03
What protects it. 750,000+ open-source InfluxDB installs and the Telegraf agent ecosystem create real switching friction in industrial and IoT deployments.
What would change this call
InfluxData announces a Series F or acquisition within 6 to 12 months. Would show financial health; continued silence suggests fundraising difficulty or distress.
QuestDB or TigerData publish named customer case studies of former InfluxData logos switching. Would confirm real customer defection, not just benchmark marketing.
AWS expands or promotes Timestream for InfluxDB while adding native competing time-series features. Would show AWS channel dependence turning into competitive absorption risk.
Key numbers
  • ~$75M estimated 2024 revenue (2025-04-09)
  • 1,900+ commercial customers (2023-02-08)
  • $81M Series E was last priced round (2023-02-08)
Named risks
  • No new priced funding round since February 2023, roughly 3.5 years, raising capital-access uncertainty. Severity: high
  • Benchmark rivals QuestDB and TigerData support InfluxDB's Line Protocol, easing customer migration away. Severity: high
  • Dependency on AWS as a distribution channel while AWS runs its own competing time-series services. Severity: medium
  • Headcount estimates inconsistent and low (129-197), with unverified layoff chatter on Blind. Severity: low
Rivals, as read in July 2026
RivalDirectionEvidence
QuestDBcontestingClaims 12x-36x faster ingestion than InfluxDB and supports Line Protocol for migration, July 2026
TigerData (TimescaleDB)contestingRebranded from TimescaleDB in June 2025, publishes comparative benchmarks against InfluxDB
Amazon Web Servicesgaining onRuns Timestream for InfluxDB as managed channel while closing own Timestream for LiveAnalytics, June 2025
ClickHouse and Snowflakegaining onGeneral-purpose OLAP platforms encroaching on time-series analytics workloads as of 2026
Questions people ask
Is InfluxData profitable in 2026?
InfluxData has not disclosed profitability. It last raised a priced round, an $81M Series E ($51M equity plus $30M SVB debt), in February 2023 and has gone roughly 3.5 years without a new round, which could signal either quiet profitability or fundraising difficulty. No company financials are public as of mid-2026.
Who owns InfluxData?
InfluxData is privately held and venture-backed, with no parent company. Its Series E (February 2023, $81M) was led by Princeville Capital and Citi Ventures, with Battery Ventures, Mayfield, Sapphire Ventures, Trinity Ventures, Norwest Venture Partners, Sorenson Capital, and Harmony Partners also participating.
Who is InfluxData's biggest competitor?
QuestDB and TigerData (formerly TimescaleDB) are InfluxData's most direct rivals as of 2026, both publishing benchmark claims against InfluxDB and supporting its Line Protocol format for easier migration. QuestDB claims 12x-36x faster ingestion than InfluxDB in a July 2026 comparison post.
Can AI replace InfluxDB or InfluxData's product?
The core time-series database layer is not AI-replaceable, but AI copilots are commoditizing the query/dashboard convenience layer InfluxDB relied on for differentiation. InfluxData responded by shipping an MCP Server (v1.3.0, May 2026) letting AI agents like Claude and Codex query InfluxDB data directly.
Has InfluxData had layoffs?
No verified mass layoff at InfluxData has been confirmed as of mid-2026; an unverified Blind forum thread references an 'InfluxData Layoff' but without dates or figures. Headcount tracker Unify GTM reported 129 employees with 7.2% year-over-year growth.
What is InfluxDB 3 and when did it launch?
InfluxDB 3 Core and 3 Enterprise, a Rust-based redesign built on the Apache Flight/DataFusion/Arrow/Parquet (FDAP) stack, reached general availability on April 14, 2025, followed by an MCP Server for AI agents in May 2026 and Telegraf Enterprise GA in mid-2026.
Timeline
  • 2026-07-01Telegraf Enterprise reaches GA with fleet management; InfluxDB 3.9/3.10 released
  • 2026-05-28InfluxDB 3 MCP Server v1.3.0 released for Claude, Codex, Cursor AI agent access
  • 2025-06Amazon Timestream for LiveAnalytics closes to new customers
  • 2025-04-14InfluxDB 3 Core and 3 Enterprise reach general availability
  • 2025-02-19Amazon Timestream for InfluxDB adds Read Replicas via AWS partnership
  • 2025-01-07Pat Walsh appointed CMO of InfluxData
  • 2023-02-08InfluxData closes $81M Series E ($51M equity plus $30M SVB debt)
Revision history
21 July 2026
First assessed. Losing its protection. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources