Mesosphere Set to Achieve Sustainable Revenue in $50 Million Range

Utilizing open-source Apache Mesos technologies, Florian (“Flo”) Leibert directs Mesosphere, Inc., and introduces efficiencies and cost savings for “webscale" enterprises seeking to optimize their cloud infrastructure. A recent Business Insider article brought attention to the success of Florian Leibert’s company, which famously declined a Microsoft acquisition offer valued at $150 million.

Mr. Leibert described his company as one that is on track to achieve $50 million in annual revenue, contrary to the expectations of Silicon Valley insiders who wrote off Mesosphere as defunct.

Launched in 2013, the company relies on the same open-source Mesos software that Apple used to create Siri. Developed at the University of California, Berkeley, the software was brought to Twitter by Ben Hindman at a time when he and the other Mesosphere cofounders were working at the social media app company.

To date, Mesosphere has raised $122 million in venture capital funding from investors that include Microsoft, Khosla Ventures, and Hewlett Packard Enterprise. With revenue tripling year by year, the company is on a trajectory to become self-sustaining, although an IPO or additional funding round may be necessary.

The Key Features of Mesosphere’s Marathon

From his base in San Francisco, Florian “Flo” Leibert oversees the operations of Mesosphere, Inc. – a technology firm – as the company’s chief executive officer. In this role, Florian Leibert maintains relationships with the firm’s funding partners, which include Andreessen Horowitz and Vinod Khosla, in addition to writing software. An example of the software he has crafted is Marathon, which is a container orchestration platform for use with DC/OS and the Apache Mesos open-source platform.

Marathon’s key features include the following:

1. Capable of multiple container runtimes offering support to Docker and Linux containers.

2. The ability to bind storage volumes to an application, allowing for databases including PostgreSQL and MySQL to run while Mesos handles storage.

3. Numerous health check features utilizing TCP and HTTP to evaluate the health of an application.

4. The ability to use an HTTP endpoint to create notifications.

5. The running of an active/passive cluster featuring leader election, which contributes to Marathon’s 100 percent runtime. 

6. Constraints, such as only running a single application instance per node, rack, etc.