<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>TypeORM Blog</title>
        <link>https://typeorm.io/blog</link>
        <description>News, release updates, and insights from the TypeORM team.</description>
        <lastBuildDate>Tue, 01 Oct 2024 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>Copyright © 2026 TypeORM</copyright>
        <item>
            <title><![CDATA[The Future of TypeORM]]></title>
            <link>https://typeorm.io/blog/future-of-typeorm</link>
            <guid>https://typeorm.io/blog/future-of-typeorm</guid>
            <pubDate>Tue, 01 Oct 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[TypeORM is one of the most high-performance, feature-rich, and battle-tested ORMs in the Node.js ecosystem, relied upon by hundreds of thousands of projects and companies worldwide. With nearly 2 million downloads each week, it powers countless applications as a critical dependency. However, over the past few years, maintenance has slowed significantly, leading to growing uncertainty about the project's future among its dedicated community.]]></description>
            <content:encoded><![CDATA[<p>TypeORM is one of the most high-performance, feature-rich, and battle-tested ORMs in the Node.js ecosystem, relied upon by hundreds of thousands of projects and companies worldwide. With nearly 2 million downloads each week, it powers countless applications as a critical dependency. However, over the past few years, maintenance has slowed significantly, leading to growing uncertainty about the project's future among its dedicated community.</p>
<p>We're thrilled to announce that Michael Bromley and David Hoeck, under the umbrella of our parent company <a href="https://elevantiq.com/" target="_blank" rel="noopener noreferrer" class="">Elevantiq</a>, are
stepping up to lead TypeORM into its next chapter. At Elevantiq, where we
specialize in enterprise digital commerce solutions, TypeORM is a critical dependency—not
only for <a href="https://vendure.io/" target="_blank" rel="noopener noreferrer" class="">Vendure</a>, our flagship open-source project, but also for many of our other solutions.
With our reliance on TypeORM and the growing needs of its vibrant community, we saw an
opportunity to contribute back and ensure the project remains active, maintained, and secure.</p>
<p>After discussions with TypeORM's original maintainers, Umed and Dmitry, we've reached an agreement to take on the project's maintenance, inspired by successful, community-centric open-source projects. One standout model is <a href="https://github.com/tauri-apps/tauri" target="_blank" rel="noopener noreferrer" class="">the Tauri project</a>, a self-governing open-source initiative co-founded by <a href="https://github.com/denjell-crabnebula" target="_blank" rel="noopener noreferrer" class="">Daniel</a>, who we already collaborate with through Michael and Vendure. Our discussions with Tauri have set the foundation for the organizational structure we envision.</p>
<h2 class="anchor anchorTargetStickyNavbar_uNQm" id="our-vision-for-typeorms-future">Our Vision for TypeORM's Future<a href="https://typeorm.io/blog/future-of-typeorm#our-vision-for-typeorms-future" class="hash-link" aria-label="Direct link to Our Vision for TypeORM's Future" title="Direct link to Our Vision for TypeORM's Future" translate="no">​</a></h2>
<p>To ensure long-term stability and governance, we plan to establish a non-profit
foundation for TypeORM, likely under the <a href="https://commonsconservancy.org/" target="_blank" rel="noopener noreferrer" class="">Commons Conservancy</a> in the Netherlands.
This foundation will be led by a board of seven members: Michael and David,
along with five additional board members dedicated to the project's success.
The board will work closely with a <strong>Working Group</strong> comprising companies, contributors,
and other community members who heavily rely on TypeORM. This collaborative setup will help guide
strategic decisions that align with the needs and goals of TypeORM's ecosystem.</p>
<h2 class="anchor anchorTargetStickyNavbar_uNQm" id="organizational-structure">Organizational Structure<a href="https://typeorm.io/blog/future-of-typeorm#organizational-structure" class="hash-link" aria-label="Direct link to Organizational Structure" title="Direct link to Organizational Structure" translate="no">​</a></h2>
<p>To drive TypeORM forward, we'll introduce three core domains:</p>
<ul>
<li class=""><strong>Development</strong>: Led by core developers with expertise across various database engines and adapters, this team will focus on TypeORM's architecture and ongoing technical maintenance and advancements.</li>
<li class=""><strong>Operations</strong>: Handling day-to-day needs, from documentation to sponsorship accounting, this team will keep the project running smoothly.</li>
<li class=""><strong>Community</strong>: Dedicated to engaging, moderating, and supporting our growing community, this team will foster collaboration through platforms like Discord.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_uNQm" id="scaling-sponsorships-and-full-time-development">Scaling Sponsorships and Full-Time Development<a href="https://typeorm.io/blog/future-of-typeorm#scaling-sponsorships-and-full-time-development" class="hash-link" aria-label="Direct link to Scaling Sponsorships and Full-Time Development" title="Direct link to Scaling Sponsorships and Full-Time Development" translate="no">​</a></h2>
<p>A significant part of our strategy is to increase sponsorships, reaching out to
companies and collaborating with organizations like <a href="https://opensourcepledge.com/" target="_blank" rel="noopener noreferrer" class="">OSS Pledge</a>. Our goal is to fund and
employ two full-time developers who will lead the Development team, ensuring ongoing progress
and project maintenance.</p>
<p>We're confident that, with this structure, we can build a sustainable future for TypeORM. But the
<em>success of this vision depends on the support of the community</em>.
We'll also remain in close contact with <a href="https://github.com/pleerock" target="_blank" rel="noopener noreferrer" class="">Umed</a> to keep his insights and vision connected to the project's evolution.</p>
<h2 class="anchor anchorTargetStickyNavbar_uNQm" id="join-us-in-supporting-typeorm">Join Us in Supporting TypeORM<a href="https://typeorm.io/blog/future-of-typeorm#join-us-in-supporting-typeorm" class="hash-link" aria-label="Direct link to Join Us in Supporting TypeORM" title="Direct link to Join Us in Supporting TypeORM" translate="no">​</a></h2>
<p>If your company is interested in starting or expanding its sponsorship with TypeORM, we encourage you to reach out to us directly <a href="mailto:maintainers@typeorm.io" target="_blank" rel="noopener noreferrer" class="">via e-mail</a>.</p>
<p>Thank you for your support, and we're excited to embark on this journey with the TypeORM community!</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_uNQm" id="join-the-conversation">Join the Conversation<a href="https://typeorm.io/blog/future-of-typeorm#join-the-conversation" class="hash-link" aria-label="Direct link to Join the Conversation" title="Direct link to Join the Conversation" translate="no">​</a></h2>
<p>Have questions or want to get involved? Join our <a href="https://discord.gg/cC9hkmUgNa" target="_blank" rel="noopener noreferrer" class="">Discord community</a> or check out our <a href="https://github.com/typeorm/typeorm" target="_blank" rel="noopener noreferrer" class="">GitHub repository</a>.</p>]]></content:encoded>
            <category>announcement</category>
        </item>
    </channel>
</rss>