MongoDB announced on November 17, 2026, that it had acquired Firebolt Analytics, adding an analytical database business with a Tel Aviv presence to the New York company. MongoDB disclosed the announcement in a Form 8-K that identifies its principal executive offices at 1633 Broadway in Manhattan. The acquisition gives the two cities another direct connection in the infrastructure behind business software. MongoDB’s November 17 SEC disclosure

The central product change is still ahead. MongoDB intends to bring Firebolt’s engine into its Intelligent Data Platform so applications can analyze current operational information alongside the database they already use. It describes customer availability in the coming months, rather than a feature customers can switch on today. MongoDB’s acquisition announcement

The Tel Aviv connection and the deal’s history

Firebolt’s own company page lists Tel Aviv among its locations, alongside San Francisco, Munich and Bangalore. It identifies Benjamin Wagner as CEO and Mosha Pasumansky as CTO, and gives 2019 as its founding year. The company presents itself as an analytical database built for engineers, with standard SQL and deployment options that range from a laptop to a large cluster. Firebolt’s company profile

CTech reported the acquisition on November 17 and said the purchase price was not disclosed. Its account traces Firebolt’s founding to Eldad Farkash, Saar Bitner and Ariel Yaroshevich, and puts the company’s historical funding at approximately $270 million. A $100 million Series C in February 2022 valued it at $1.4 billion. That figure describes an earlier financing round; the announcement supplies no comparable sale price. CTech’s acquisition reporting

The same report describes management changes and workforce reductions before the deal, including Wagner’s appointment as CEO in September 2025 and layoffs in February 2026. For Tel Aviv’s technology community, that history makes this more than a product announcement: an Israeli-founded database business is moving into a larger software platform after a period of restructuring.

Why an analytical engine matters inside an application

Recording a single purchase and calculating a pattern across millions of purchases ask different things of a database. The first operation needs to capture a particular event correctly. The second may need to examine a few fields across a very large collection of events. When both feed a live application, the analysis also needs to finish while its answer is still useful.

Firebolt’s technical explanation of columnar storage helps make the distinction concrete. Grouping values by column allows an analytical query to read the fields it needs without retrieving every field of every record. Compression and processing batches of values can further reduce the work involved. Firebolt describes its own implementation as combining columnar storage, indexes and a separation of storage from computing resources. Those are architectural descriptions, not performance results for the forthcoming MongoDB integration. Firebolt’s columnar-storage explanation

Imagine a software service that shows a customer how a current measurement compares with months of prior activity. An old overnight extract may miss what happened during the current session. A separate analytical system can answer the historical question, but the team then has to decide how new information reaches it and how much delay the feature can tolerate.

What customers can expect next

MongoDB says it plans to run Firebolt’s engine alongside its database and synchronize information automatically, reducing the pipelines customers must maintain themselves. Its announcement also says existing Firebolt customers can continue with the same product, support and service. These statements describe the buyer’s integration plans and continuity commitment. The announcement and customer FAQ furnished to the SEC

In November 18 coverage, The Register raised a useful unresolved question: automatic synchronization does not establish whether the underlying architecture avoids separate data copies. The publication said it had asked MongoDB to clarify that architecture. That distinction will matter to engineers assessing the eventual service’s operation and cost. The Register’s analysis

For teams in New York and Tel Aviv, the next decision point comes when MongoDB publishes the integrated service’s availability, technical documentation and commercial terms. A meaningful evaluation would use changing production-like data and many simultaneous queries, then measure response time, freshness and resource use together. The acquisition establishes who will build the combined offering; those later details will show where it fits into a working application.