Why a security & compliance analyst should care
A vendor can be technically excellent and still deserve a hard continuity review. Confluent’s 2021 IPO filing-era numbers make that point unusually clearly: fast growth, substantial losses, and heavy cash use were all true at once. None of those figures proves a security incident or predicts a service failure. They do give a security & compliance analyst useful prompts for testing how a critical supplier funds, scales, and supports its service.
This is a financial snapshot from June 2021, not a description of Confluent today. TechCrunch reported that Confluent built a streaming data platform on Apache Kafka, and had raised more than $455 million since launching in 2014. It was most recently valued at just over $4.5 billion after a $250 million funding round the prior April. The company had filed its S-1 with the U.S. Securities and Exchange Commission that week. Those details set the context: an enterprise-relevant platform moving from private-company growth into public-market scrutiny.
For an analyst, the useful question isn’t “is this company risky because it lost money?” It’s whether the organization understands the dependency, has tested its continuity assumptions, and can respond if the supplier’s operating model changes. Financial data belongs beside technical and contractual evidence—not in place of it.
Growth was impressive; the trajectory mattered
Confluent’s reported revenue rose from $65.2 million in 2018 to $149.8 million in 2019, a 130% increase. Revenue reached $236.6 million in 2020, with growth slowing to 58%. TechCrunch described the 2020 expansion as solid despite the pandemic, while noting the sharp deceleration from the previous year. The first quarter of 2021 brought $77 million in revenue and 51% year-over-year growth.
That’s not a collapse. It is a changing growth profile, and that distinction matters. A security & compliance analyst assessing a supplier should avoid treating a single growth percentage as a verdict. Instead, ask whether the service is becoming more established while its growth rate moderates, and what that means for support, investment, and the customer’s own reliance on it. The article’s numbers are historical indicators; they do not establish current operating capacity.
The company’s net retention rate was 117% at March 31, 2021, down from 130% a year earlier. TechCrunch also reported remaining performance obligations of $280.9 million in Q1 2021, compared with $166.3 million in the year-ago quarter. These measures point in different directions: retention had eased, while reported obligations had increased. Neither, on its own, answers whether a supplier can meet a particular customer’s service, security, or recovery commitments. They are reasons to ask precise follow-up questions, not substitutes for evidence.
Losses and cash use deserve context
Net losses expanded from $41.4 million in 2018 to $95 million in 2019 and $229.8 million in 2020. TechCrunch noted that the 2020 figure included $111.9 million in one-time share-based compensation expense. Adjusted operating losses were reported at $79.4 million in 2019 and $89.3 million in 2020. That distinction is important: headline net loss and adjusted operating loss describe different views of performance, and neither should be silently substituted for the other.
Free cash flow was negative in each year cited: -$22.6 million in 2018, -$71.8 million in 2019, and -$86.7 million in 2020. For Q1 2021, the reported free-cash-flow margin improved to -28%, compared with -64% in the year-ago quarter. Gross margin rose from 65% in Q1 2020 to 69% in Q1 2021. The picture is mixed, not a one-word “healthy” or “unhealthy” rating.
That nuance should carry into vendor reviews. Ask what financial information is available, how often it is refreshed, and what contractual or operational protections exist if circumstances change. A public filing can inform the conversation, but it cannot establish the vendor’s current cash position, future plans, or security posture. Don’t infer those things from a 2021 article.
Sales investment can be a resilience question
TechCrunch characterized Confluent as a high-burn SaaS business and described an increasingly expensive sales model. Sales and marketing costs rose from $54.5 million in 2018 to $115.8 million in 2019 and $166.4 million in 2020; that final figure included elevated share-based compensation expense. The article’s framing was not that spending on growth was inherently improper. Investors had supplied capital for growth. The open question was how public investors would weigh that spending against decelerating growth.
For customers, the practical implication is narrower than a forecast: supplier strategy can change. A security & compliance analyst should map the organization’s dependency on the service, identify the business processes that rely on it, and confirm who owns contingency decisions. Check that service commitments, incident-notification obligations, data export paths, and exit provisions are understood in the contract and tested operationally. These are diligence actions—not claims about Confluent’s controls or likely behavior.
If the service supports a critical data pipeline, continuity planning should be concrete. Know which internal teams depend on it, what alternatives or manual procedures are feasible, and how recovery responsibilities are divided between customer and provider. The article provides no evidence about Confluent’s incident response, security certifications, or specific recovery capabilities; those require direct documentation and assessment.
A practical analyst checklist
Use the historical case to sharpen questions, not to score a vendor by proxy:
- Recheck the evidence date. The figures discussed here come from the 2021 IPO period. Obtain current financial and operational information before making a present-day assessment.
- Separate measures. Distinguish net loss from adjusted operating loss, and revenue growth from cash flow. Record what each number does and does not show.
- Map criticality. Document the workloads and business processes that depend on the service, including dependencies on identity, networking, and other providers where applicable.
- Validate continuity evidence. Review applicable service commitments, recovery documentation, incident communications, and customer responsibilities. Ask for evidence rather than relying on financial headlines.
- Test the exit. Confirm data portability, transition assistance, and a workable alternative or recovery plan for the organization’s use case.
- Set review triggers. Define what change in service, ownership, support, or disclosed financial condition prompts a reassessment. Use indicators relevant to your organization, not a universal threshold invented from one company’s history.
The takeaway: diligence, not diagnosis
Confluent’s IPO-era story combined rapid expansion with slower growth, widening net losses, negative free cash flow, and some improving operating measures. Its Q1 2021 retention rate of 117% was below the 130% year-earlier result, while remaining performance obligations increased and gross margin improved. That is a complicated operating picture. It deserves a complicated reading.
For a security & compliance analyst, the central lesson is straightforward: financial resilience is one input to third-party risk and continuity planning, not a proxy for cybersecurity. Use it to ask better questions and to revisit assumptions about a critical service. Then verify the answers through current, relevant evidence. That is less dramatic than declaring a vendor safe or unsafe—and much more useful.
Source: TechCrunch’s June 2, 2021 analysis of Confluent’s IPO-era growth and cash use.
a security & compliance analyst should care