Henrique Schmaiske and the human work behind Meteor 3.0

Meteor.js is one of those open-source projects developers have lived with for years. It has over 44,800 GitHub stars, more than 500,000 active installations worldwide, and still sits inside products across many countries.

Behind its largest release in over ten years, Meteor 3.0, is Henrique Schmaiske, CTO of Meteor Software, who started the work in April 2022 and led it to release in July 2024.

A framework people still depend on

Meteor launched in 2011, when full-stack JavaScript felt new. Its appeal was straightforward: developers could build across client and server with one language, while working with real-time data patterns that made applications feel immediate.

That is what made Meteor 3.0 more than a routine upgrade. When a framework has over 5,300 GitHub forks and hundreds of thousands of active installations, every major change lands somewhere: on startups, enterprises, and developers relying on maintainers’ decisions.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol' founder Boris, and some questionable AI art. It's free, every week, in your inbox. Sign up now!

For Schmaiske, the work was not about making Meteor look new but about moving it forward without treating its community as collateral damage.

The old engine had to come out

The hardest technical issue was Fibers, a library Meteor had used to make asynchronous JavaScript feel synchronous. For developers, it had been part of Meteor’s smoothness, but the JavaScript and Node.js ecosystem had moved on.

The need to remove Fibers had already been written down in GitHub Discussion #11505 in June 2021. That was the original planning document, but execution had not started. Schmaiske began work after joining Meteor as Tech Lead in April 2022.

He led the Meteor.js open-source team, setting direction, designing migration paths, sequencing releases, reviewing code as a CODEOWNER, and communicating publicly with users. The team implemented the changes, while Schmaiske led the effort.

The change touched methods, publications, and database access. Meteor had to move to native async and await while giving applications a realistic way to adapt. When Node.js 14 reached end of life in April 2023, the path became urgent.

Open source does not move by command

Inside a company, a difficult migration can be managed through meetings and deadlines, but open source is different. People are spread across countries, time zones, companies, and priorities. Some teams upgrade quickly, while others have compliance reviews, customer obligations, or production systems where downtime is serious.

That is why communication became part of the engineering work. In March 2023, Schmaiske opened the public Meteor forum thread for the Fibers roadmap and Meteor 3.0, then posted weekly progress updates for nearly 18 months.

Those posts were practical. They showed what had shipped, what was blocked, what needed attention, and where users should be careful. They reduced guesswork and made the migration feel less like a surprise and more like a road users could follow.

The bridge came before release

Meteor 3.0 did not arrive as one break from the past. Before the July 2024 release, Schmaiske directed work that allowed Meteor applications to begin adopting async and await alongside older patterns. That groundwork shipped in Meteor 2.8 and 2.9 during 2022.

That sequencing mattered. Instead of pushing every user toward one upgrade window, Meteor gave teams time to prepare before the architectural shift landed.

Schmaiske’s contribution to that foundation was recognized. In the official Meteor changelog, he is listed first in the “Special thanks to” sections for v2.8.2 and v2.9.

When Meteor 3.0 shipped in July 2024, it covered 2,300 commits, 800 changed files, and more than 200 pull requests. It removed Fibers, moved the framework to async and await, and updated Node.js to version 20.

Recognition beyond the core community

The official Meteor 3.0 release announcement named Schmaiske one of three core contributors. On the Meteor forum, it received more than 22,600 views and 626 likes.

The release also reached the wider JavaScript ecosystem. JavaScript Weekly issue 697, published on July 18, 2024, covered Meteor 3.0, putting it before a long-running newsletter’s readers.

Schmaiske is also a designated CODEOWNER on the main Meteor.js GitHub repository, which means his review is required for changes affecting key parts of the framework. In a mature open-source project, it is the responsibility of people building on top of it.

Meteor’s reach helps explain why that responsibility matters. Wappalyzer, TheirStack, and Enlyft list Meteor.js as being in active use across thousands of companies as of 2025. Built In names Apify, ANY.RUN, and Chatra are among the companies using the framework.

A practical route into leadership

Schmaiske’s path to Meteor was built through hands-on software work. Before joining the company, he worked at Brazilian startups Tipay and Hola! Cartão, later with Familio in Copenhagen and AE Studio in Los Angeles, where he led blockchain-related work for Protocol Labs using Filecoin.

His professional path began outside the traditional framework of engineering. He had been hands-on with computers from a young age, built websites on the side, and ran an online education business called Burn Up Studio, growing it to more than 400 students while building the platform himself. That led to startups, international software teams, and open-source framework leadership.

He joined Meteor Software in April 2022 as the company’s first technical hire under a new leadership team. Soon after, he began the Meteor 3.0 work, helped shepherd the framework through its largest release in more than ten years, and became CTO in April 2025.

His background is practitioner-first. He learned by building and shipping production software, then moved into leadership through projects where reliability had consequences. That shows in Meteor 3.0’s staged releases, migration planning, code review, public updates, and focus on people, depending on the framework.

What comes next

Meteor’s modernization did not stop with 3.0, but the lesson is less about any single feature than about stewardship. Galaxy Cloud gives the team production feedback, but Meteor 3.0 remains the clearest example of his leadership.

The release showed that a decade-old open-source framework can rebuild core parts of itself without walking away from the community that depends on it. For Schmaiske, the achievement was helping thousands of downstream teams move forward with confidence.