Headless CMS

Definitions & benefits

Tools & Concepts

Open source

Features

Authentication

Custom plugins & Marketplace

Webhooks

Multilingual CMS

APIs

Dynamic Zones

User roles & permissions

Content Modeling

Security & Privacy

Use Cases

Ecommerce

Blog

Forum

About Strapi

Life at Strapi

Releases & Roadmap

Events

Community

News

The Tutorials section covers an introduction to Strapi, some advanced technical content, product updates and releases. From basic workaround to in-depth development guides. 

Tutorials

How tos

Get all the latest updates, news and events.

Subscribe to the newsletter 📣

As it approaches its first anniversary, [Strapi Cloud](https://strapi.io/cloud) has significantly evolved and proven its robustness with an excellent track record of stability. 

Strapi Cloud now offers great features to make infrastructure management easy. You can check your API use and how much data you're moving right from the main page. There's easy access to logs for quick fixes. You can use [custom domain](https://docs.strapi.io/cloud/projects/settings#connecting-a-custom-domain) names to keep things professional. With servers in both the US and Europe, your site runs fast no matter where your users are. Start off with a ready-made template to save time. Don't worry about losing data; we've got [automatic backups](https://docs.strapi.io/cloud/projects/settings#backups). Plus, next to GitHub you can now also send over your work from GitLab without a hitch. 

Support services have been exemplary, ensuring that users can leverage the full potential of the platform with minimal downtime. Also, Strapi Cloud is on the verge of achieving SOC2 compliance, a testament to its commitment to security and privacy standards.

Today, we're happy to share some updates to Strapi's plans to make choosing what you need easier and clearer for everyone, no matter where you are in your project. Here’s what this means for you:

- More people can use Strapi Cloud. If you're starting out or working on small projects, there’s more room to grow.
- Whether you’re just getting started, expanding your team, or managing a big project, you'll have access to the features you need at every step.
- It's going to be easier for you to see when it makes sense to move to a plan with more features, especially if you're working with others and need more advanced options.

We've also made it simpler to choose the right plan with predictable pricing and clear overages. This way, you can focus more on your project and less on figuring out which plan fits best.

## TL;DR
- Today, we’re excited to introduce a more accessible plan for individual developers building personal projects
- The number of seats included by default in the Strapi Cloud PRO and TEAM plans has been reduced to 5 and 10 respectively
- The price of additional storage has been decreased
- The price of additional bandwidth has been slightly increased
- Customers can choose to remain on their existing Pro or Team plans to be grandfathered in the old pricing and usage limits

## Designed with You in Mind
Many of our users are building or migrating their passion projects to Strapi. Developers need time to build their side projects, and they don't want to pay for unnecessary infrastructure while they do it. At the same time, hosting can be expensive and time-consuming.

As we designed the new plan, we recognized that predictable pricing that is simple and accessible was critical for many of our users who are still in the “build” phase of their project/business. The Strapi Developer Plan is our answer to this need, crafted with the insights and aspirations of the vibrant Strapi community at its core. 

## Who is the Developer Plan For?
The Developer Plan is tailor-made for individual developers, freelancers, and small teams who are in the early stages of their project lifecycle. Whether you're building a personal blog, a portfolio site, a small e-commerce platform, or experimenting with new web technologies, this plan is designed to scale with your project.

Ideal for those who prioritize ease of use, flexibility, and cost-effectiveness, the Developer Plan removes the complexity of managing your own server, database, CDN, and email provider while providing powerful features to bring your digital experiences to life. It's perfect for projects that require a customizable CMS backend without the need for security and collaboration features.

## Pricing Details and Overages
Understanding the importance of transparency and predictability, especially for individual developers and small teams, we've structured the Developer Plan to be straightforward and accessible. Here's what you need to know about the pricing and overages:

The plan comes with a competitive monthly subscription fee of $29, ensuring that you have access to all the essential features you need to get your project off the ground.

With 1 seat included by default and the flexibility to add up to two additional seats at just $15 per month per seat, this plan supports collaboration while maintaining affordability. It includes 1,000 CMS database entries and 25 MB of database storage, running on a PostgreSQL database, ensuring your projects run smoothly on reliable and efficient database software.

The plan shines in asset storage and bandwidth, offering 15 GB of storage right off the bat, with the option to expand up to 1,500 GB at a cost-effective rate of $0.5 per additional GB. 

It also boasts a generous 100,000 API requests limit, extendable to 1,000,000, to accommodate growing development needs. 

File upload is capped at a sizable 200 MB per file, ensuring that even large assets can be managed with ease. For bandwidth, you start with 50 GB, with the option to purchase more at $30 per additional 100 GB, maxing out at 500 GB. 

This plan is designed to scale with your development journey, offering a comprehensive suite of features that cater to the evolving needs of developers and small teams, making it an ideal choice for those looking to build and scale their projects efficiently and cost-effectively.


## Only Pay For What You Need
The best plan is one that can change as your team does, without paying for things you don't need. By making Strapi more accessible, we've designed all plans to grow with you. As your project scales, you might exceed the plan's limits. Our overage charges are clearly defined, so you'll always know what to expect. These fees are designed to be fair and proportional to your usage, ensuring that you only pay for what you need.

### Add Seats as Needed
The Developer Plan comes with a single seat and is tailor-made for individual developers and freelancers. With the option to add up to two additional seats at $15 per month each, it offers a degree of flexibility for developers who might occasionally need to grant access to a collaborator or temporary team member.

Designed for small teams or startup companies, the Pro Plan provides 5 seats by default with the capability to expand up to 20 seats. Each additional seat costs $15 per month, making it a cost-effective solution for growing teams that need to manage their budget carefully while still having the option to scale.

The Team Plan offers 10 seats with the capability to expand up to 50 seats. It's an excellent choice for mid-sized businesses or departments within larger corporations, offering significant flexibility. The additional seat price remains $15 per month, making it a scalable option for teams anticipating growth.

### More Generous Storage Overages
All Cloud plans come with generous assets storage. But we know managing CMS storage can sometimes be a bit tricky, especially when you're working on big projects or your site is growing fast. That’s why we made the storage overage fees a lot more friendly by decreasing them to just $0.5 per extra GB of storage for the Developer plan and $0.6 per extra GB for Pro and Team plans.

### Increased Bandwidth Overages
Just like any other business, Strapi needs to make sure it can keep running smoothly and provide all the great services you love. To do this, sometimes we have to adjust things a bit, especially when it comes to limits and extra charges. That’s why the rate for monthly bandwidth overages has increased from $25 to $30 per 100 GB.

This might mean that costs could go up a little for some of our users. We want you to know that we don't make these changes lightly. It's all about making sure Strapi can continue to support your projects and grow with you for a long time to come. 

## Overview of All Strapi Plans
Starting today, Strapi offers 5 plans:

|          | **Community**                                      | **Developer**                           | **Pro**                               | **Team**                                  | **Enterprise**                                  |
| -------- | ---------------------------------------------- | ----------------------------------- | --------------------------------- | ------------------------------------- | ------------------------------------------- |
| Delivery | Self-Hosted                                    | Cloud                               | Cloud                             | Cloud                                 | Self-Hosted                                 |
| For who  | Best for developers                            | Best for developers                 | Best for small teams              | Best for mid-sized teams              | Best for an organization                      |
| For what | Best for getting started on your local machine | Best for building personal projects | Best for building corporate sites | Best for building large sites or apps | Best for dealing with regulatory compliance |
| Price    | [Free Forever](https://docs.strapi.io/dev-docs/quick-start)                                   | [$29 per project / month](https://strapi.io/pricing-cloud)             | [$99 per project / month](https://strapi.io/pricing-cloud)           | [$499 per project / month](https://strapi.io/pricing-cloud)              | [Get a quote](https://www.strapi.io/contact-sales)                                 |



## Stay on Your Current Plan

> #### 💡 Your current projects will keep their current plans. 
> You can choose to switch to a new plan for your projects if you want, but it's not required. We will be grandfathering all existing projects. If you decide to change your plan, the new pricing and limits will apply.



We understand the value of consistency and loyalty, which is why we're excited to announce a special consideration for our existing Pro and Team Plan users. If you're already using one of these plans, you can keep it just the way it is. That's right, you don't have to switch to a new plan! This means you can continue to enjoy the benefits, features, and pricing you signed up for, without any disruptions. It's our way of showing our appreciation and making sure you're happy and comfortable continuing your great work with us.

## Discounts for Open Source and Non-Profit Initiatives
In case you missed it, we have also recently reiterated our financial support to open-source projects and non-profit organizations by offering significant Strapi Cloud discounts. 

At Strapi, we deeply appreciate the value that open-source projects bring to the community. By offering a substantial discount to Open Source initiatives, we wish to contribute to the sustainability and growth of these projects, ensuring that they continue to thrive and benefit the broader community.

Non-profit organizations play a crucial role in addressing societal challenges and making a positive impact on the world. Recognizing the financial constraints faced by many non-profits, Strapi is extending its offer to these organizations as well. By reducing the cost of our services, we hope to empower non-profits to channel more resources toward their mission and amplify their reach.

[Learn more ->](https://strapi.io/blog/empowering-open-source-and-non-profits-with-strapi-cloud)

## Host on Your Own Terms
If you aren’t confident in our business model though, we’re open source. You can host it yourself.  Even better, everything we create is out there for you to see and use on GitHub. 

So, if you're a bit unsure about jumping fully into a paid plan, no worries! Strapi is open-source, so you can set it up on your own server. The Community Plan from Strapi is something really cool, especially because it's free forever.

## Getting Started
Embarking on your journey with the Strapi Developer Plan is simple. Head over to our website to learn more about the plan's features, pricing, and how to sign up. Our goal is to help you turn your ideas into reality, and with the Strapi Developer Plan, we're one step closer to achieving that.

In conclusion, the Strapi Developer Plan is more than just a new subscription option—it's a commitment to supporting the developers and small teams at the heart of the digital ecosystem. By offering an accessible, flexible, and powerful solution, we're excited to see the innovative projects you'll bring to life. Welcome to the next chapter of your development journey with Strapi.


Announcing the new Strapi Developer Plan! A new plan to make our pricing more accessible, making it even easier to get started and grow with Strapi.

large_Introducing the New Strapi Developer Plan to Help You Build Personal Projects.jpg

medium_Introducing the New Strapi Developer Plan to Help You Build Personal Projects.jpg

small_Introducing the New Strapi Developer Plan to Help You Build Personal Projects.jpg

thumbnail_Introducing the New Strapi Developer Plan to Help You Build Personal Projects.jpg

Introducing the New Strapi Developer Plan to Help You Build Personal Projects.jpg

Introducing the new Strapi Developer plan to help you build personal projects

Paris

Pierre created Strapi with Aurélien and Jim back in 2015. He's a strong believer in open-source, remote and people-first organizations. You can also find him regularly windsurfing or mountain-biking!

Sales

Founders

With 58,000 stars on GitHub, 1,000 contributors, and more than 12 million downloads, Strapi’s impact is clear. Our client base includes tech giants like Amazon and Adidas, among others. But today, I want to shift focus from Strapi's achievements to a topic that's vital for many in the open-source world: the business model dilemma we face when building a Commercial Open-Source Software (COSS).


<iframe width="560" height="315" src="https://www.youtube.com/embed/AfVzyKl_-kw?si=3vrSzOI0_youCwNk" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

## The Roots of Strapi
Our story starts back in 2015 at university. My co-founders, Aurélien, Jim, and I were then students and freelance developers. We often worked with traditional CMSs and faced their limitations firsthand, especially when it came to managing content for modern applications. This led us to create Strapi, and on October 1st, 2015, we pushed Strapi’s first line of code into GitHub.

![Strapi's launch](https://api-prod.strapi.io/uploads/Strapi_s_launch_9f0606a1dd.png)

From the beginning, it was a no-brainer for us that Strapi had to be open source: we believed in the power of community, and our experience building websites as freelancers made us firm believers that a CMS had to be fully customizable.
We spent two years studying while working as freelancers and maintaining the project as much as we could on our nights, weekends, and holidays. Juggling our studies, freelance work, and Strapi was challenging, but the community's engagement made it rewarding.

## The Agency: Strapi’s very first Business Model

By 2017, it was time to commit to Strapi full-time. We started as freelancers, which allowed us to generate income quickly and use our product firsthand—that was our first business model. However, this model had its drawbacks. Most of our time went to client-specific needs, leaving little for Strapi’s development. We realized we needed to focus solely on Strapi to evolve the product at the pace we envisioned. To be able to free ourselves from distractions and focus solely on Strapi, we had to raise money.

## The Fundraising Path

Our fundraising journey began in 2018. We raised our first million in pre-seed, allowing us to dedicate ourselves to Strapi. This was a pivotal moment. It helped us grow our team (by recruiting for the first time) and expand our user base. We then raised a $4M Seed in 2019 and a $10M in 2020.
We raised all that money without any revenue coming in. This approach, while successful for us, is risky and less feasible in today's VC climate. That is not something we would recommend doing today. In the current context, you will need to show not only community traction but revenue traction.

![Strapi's timeline](https://api-prod.strapi.io/uploads/Strapi_s_timeline_8417477e48.png)

## Open Core vs SaaS: Picking the Right Business Model

To make money in open-source, you have two main options: going open core, or going SaaS.

![Open Core vs. SaaS](https://api-prod.strapi.io/uploads/Open_Core_vs_Saa_S_d92ba6fb75.png)

In 2020, Strapi embraced the Open Core model. At that time, being one of the few headless CMS companies, we saw a clear demand for additional features from our users. The decision to launch an Enterprise Edition was strategic. It wasn't just about adding features; it was about scaling our revenue and attracting further investment. That also helped us raise a great $31M Series B in 2022, two years after the launch of our paid offering.

So what’s the conclusion about Open Core for us? It was an interesting first model for us as we had no infrastructure to manage, we closed significant deals in terms of ACV because companies interested in open core were willing to pay for additional features.

We learned that a key element with Open Core is maintaining a single codebase. Forking the Community Edition can lead to maintenance challenges and user confusion. For us, the Enterprise Edition is an extension of our Community Edition. If you go open core, that's the first advice I’ll give you: **do not fork your Community Edition**. Instead, make it an extension.

It is important to mention one of the challenges we’ve been facing with this business: measuring usage. When your product does not run on your own servers, it can be difficult to understand usage and iterate based on it. Even drafting a pricing strategy that makes sense for everyone can be difficult, as the pricing usually depends on the usage, whether it's the number of API requests or the number of seats.

### Key Takeaways from the Open Core Business Model

| **Wins**                                                   | **Challenges**                                                                             |
|------------------------------------------------------------|--------------------------------------------------------------------------------------------|
| - It brought us to Series B                                | - Confusion between free and paid                                                          |
| - No infrastructure to manage                              | - Usage tracking is difficult, which makes renewals, expansion and Customer Success harder |
| - Focus on only one business model                         | - From individuals to enterprises                                                          |
| - Enterprise = big deals                                   | - Requires specific roles: Field Sales, Solution Architects, etc.                          |
| - Enterprise Edition in the open, with one single codebase | - Sales (and procurement processes) intensive                                              |

## The Strapi Cloud Journey

Despite the success with Open Core, we kept hearing the same recurring feedback from Strapi’s Community: **“I love Strapi, but I don’t want to manage servers”**. Handling uptime, scalability, security, networking, and so on became a recurring and growing pain point among our users. This insight led to the birth of [Strapi Cloud](https://cloud.strapi.io). Our goal was to simplify the Developer Experience: what if you could just click on a “sign up” button and get your Strapi project up and running? Strapi Cloud is more than just a product; it's a solution to a real problem, making it easier for users to get value from Strapi without the complexities of server management.

We learned that companies like to buy features, but are even more comfortable paying for hosted software. If companies use your self-hosted version, they will have to buy servers anyway. So they are more likely to pay you for a hosted service directly.

Proposing a hosted version of your open-source product also comes with some challenges. In our case, we needed new skills in our team, such as PLG marketers, a more proactive customer success team, and Solution Architects. Building and maintaining a platform is a second product, and it might require deeper changes such as architecture changes in your product to go multi-tenant. It asks for a new paradigm to anticipate.

### Key Takeaways from Strapi Cloud's Business Model 
| **Wins**                                                         | **Challenges**                                                         |
|------------------------------------------------------------------|------------------------------------------------------------------------|
| - Shorter time to value                                          | - Requires a new set of skills: SREs, PLG marketers, reactive CS, etc. |
| - Not only sell features but compute                             | - It's a second product to build and maintain                          |
| - Companies are more used to pay for hosted software             | - Might require some architecture changes                              |
| - Flywheel: increases usage and revenue                          |                                                                        |
| - Better suited for self-serve, which results in more efficiency |                                                                        |
| - Enlarges total addressabke market                              |                                                                        |

## Sales-Driven vs. Self-Serve Models

I’ve shared some learnings from our journey to open core and our journey to offer a managed version of our product. Another key thing to think about when building an open-source startup is the choice between being sales-driven and self-serve.

You’ll need to be focused on only one of these two at the beginning because your team will be too small. And even when your team gets bigger, you will want everyone to be aligned.

![Open Core vs. SaaS](https://api-prod.strapi.io/uploads/Open_Core_vs_Saa_S_d3c2ef0501.png)

At Strapi, we had to navigate through multiple motions. We went from individuals with our Community plan to large companies with the release of the Enterprise Edition. Now, with the arrival of Strapi Cloud, we can offer a product to SMBs and mid-market companies.

![Strapi Motions](https://api-prod.strapi.io/uploads/Strapi_Motions_7fe76eb9b3.png)

It can be easy to be all over the place. My advice here would be to focus, and pick one. Iterate on it, try it, and analyze where you get the most traction from. But you won’t be able to optimize multiple machines at the same time.

Our journey also involved balancing sales-driven and self-serve models. In the beginning, it's crucial to focus on one due to limited resources. As we grew, these models became complementary. The sales-driven approach targets larger clients, while self-serve caters to smaller businesses and individual users.

|              | **Self-Serve**                                        | **Sales-Driven**                                      |
|--------------|-------------------------------------------------------|-------------------------------------------------------|
| **Pros**     | - More efficient, higher velocity, easily scalable | - Higher ACV, helps collecting feedbacks             |
| **Cons**     | - Lower retention, lower ACV                         | - Capital intensive, requires strong differentiators |
| **Comments** | Great fit for SaaS                                    | Great fit for Open-Core                               |

## Conclusion: Adapt & Overcome

What have we learned from our journey at Strapi building an open-source startup?
It’s vital to start selling early: Don’t do like us, the market is different today. Except if you’re in a very hot market like AI, start selling early. You will learn a lot about who your users are, and what they want.
Do something users want. If they want open core, go Open Core. If they want SaaS, do SaaS.
Default to SaaS and Self-Serve. Except if your Ideal Customer Profile is the enterprise and that your SaaS market is very crowded, SaaS with Self-Serve is the way to go.
Focus on one model only. That’s the most important thing: focus. And say no to the rest.
As your business grows, be prepared to adapt and evolve. The open-source landscape is dynamic, and success lies in being responsive to market needs and user feedback.

large_open source business model dilemma.jpg

medium_open source business model dilemma.jpg

small_open source business model dilemma.jpg

thumbnail_open source business model dilemma.jpg

open source business model dilemma.jpg

The Business Model Dilemma of Building a Commercial Open Source Software

Before we get into celebrations and upcoming innovations, I wish you, on behalf of the Strapi team, a Happy New Year! May 2024 bring you health and success in every personal or professional project you want to build and grow!

2023 has been such a productive year! The project has reached new milestones:
-   🌟 58k stars on GitHub (134th most starred repository,[  add yours](https://github.com/strapi/strapi)!) 🌟
-   ⏬ From 2M to 4M annual downloads on npm
-   🏗️ 936 contributors
-   ⚡️ 1307 issues closed
-   ⬆️ 6,448 commits pushed
-   ✅ 298 pull requests merged
-   📣 21,381 community members on[  Discord](https://discord.com/invite/strapi)

What a ride! Let's go over all the great things that happened in 2023 together. 🚀

## Community

[StrapiConf](https://conf.strapi.io/) is our annual global user conference. For the 2023 edition, we were proud to bring the spotlight on amazing Strapi Community members, partners, users or customers. In case you missed it, check out how:
-   [Tesco built a 500k audience multi-channel solution on top of Strapi](https://www.youtube.com/watch?v=aP-8GLzv6JQ) 
-   [Sonos deployed Strapi to reach new markets](https://strapi.io/user-stories/sonos-pixel-alliance)
-   [Bash powers multi-channel e-commerce with Strapi to go live in 7 months](https://strapi.io/user-stories/bash)

You can also find all the [talk recordings](https://www.youtube.com/watch?v=4n9x9x8WP3k&list=PL7Q0DQYATmvh133Z8b2I6T87e0ReXJ6hs) directly on the Strapi YouTube channel.

60 new plugins were published on Strapi Market, which now totalizes 166 extensions. The most downloaded community plugins include:
-   [Import/Export Entries](https://market.strapi.io/plugins/strapi-plugin-import-export-entries), by [Baboo](https://github.com/Baboo7)
-   [Translate](https://market.strapi.io/plugins/strapi-plugin-translate), by [Felix Haase](https://github.com/Fekide)
-   [Responsive image](https://market.strapi.io/plugins/strapi-plugin-responsive-image), by [Nicolas Hamelin](https://github.com/nicolashmln)

## Product

Strapi is greater than ever, thanks to many improvements:
-   [Data Transfer](https://docs.strapi.io/dev-docs/data-management): Easily import, export, and transfer content from one environment (ex. local/development) to another (ex., staging or production).
-   [Review Workflows](https://docs.strapi.io/user-docs/settings/review-workflows): Review content before it is published.
-   [Custom Roles became free](https://strapi.io/blog/custom-roles-and-permissions-available-for-free-in-strapi-v4-8): Role-based Access Control, including Custom Roles, became 100% free.
-   [TypeScript](https://docs.strapi.io/dev-docs/typescripthttps://docs.strapi.io/dev-docs/typescript): From now on, you can customize your Strapi project (both the API and the admin panel) using TypeScript.
-   [Bulk Publish](https://strapi.io/blog/may-product-updates): Publish multiple entries at the same time.
-   [Rich Text Editor](https://strapi.io/blog/say-hello-to-strapi-v4-14-with-rbac-for-review-workflows-and-new-rich-text-editor-with-content-blocks-alpha): Easy to use rich text editor.
-   v5: We also made significant progress on Strapi v5 (more details below).
-   And more!

As much as your favorite open-source Headless CMS became better and better, 2023 definitely was the year of [Strapi Cloud](https://strapi.io/cloud)!

Since the creation of Strapi, it has been possible to deploy Strapi on any server or Cloud. With all of the benefits that come with this, it includes some challenges to handle: setting up servers (application, database, assets, etc.), managing security, scalability, etc. This might result in a lot of hidden financial and human costs. Strapi Cloud removes all of this complexity, by being **the easiest platform to host, and scale, Strapi projects**.

Strapi Cloud has been a fantastic success. We received a ton of positive feedback, and the numbers speak for themselves:
![Strapi Cloud Active Projects](https://api-prod.strapi.io/uploads/Strapi_Cloud_Active_Projects_6081b89933.png)
[Give Strapi Cloud a try!](https://strapi.io/cloud)

As a business, we are glad we raised our Series B last year. This, combined with the massive growth of Strapi Cloud and the Enterprise Edition, guarantees the **sustainability of the project**, which is essential for all of the Strapi users. I am very comfortable to say Strapi is a solution you can very confidently rely on for all of your future projects.

The self-hosted Enterprise Edition (which includes SSO, Audit Logs, Review Workflows, Releases - soon, Content History - soon, and support) of Strapi has been a fantastic success since we started selling it in 2020. We see so much demand for Strapi Cloud that we are now shifting our efforts to the Cloud. We believe this is great not only for Strapi's sustainability but, even more importantly, for the community: it allows us to grow our revenue while limiting the number of paid features (hosting the CMS being necessary for anyone using a CMS).

## Company

We are now 78 Strapiers in the team, working 100% remotely, located in 13 different countries, for a total of 23 nationalities! 

In June, we spent a fantastic week together, in person. For an all-remote organization like Strapi, it is essential to better know each other. The event was a perfect mix of inspiring workshops (cross-team collaboration, etc.) and, even more importantly, a ton of delightful moments! Strapiers organized amazing activities, such as karaoke, tea making, meditation (so relaxing that I fell asleep!), solidarity world tour, movie watching, soccer, darts, guinguette, and dance party. It was so much fun!

![Company Onsite Picture](https://api-prod.strapi.io/uploads/Company_Onsite_Picture_9b89cc516f.png)

## What's planned for 2024?

We have one objective for 2024: To **make the Editing and Deployment Experience seamless**.

### Editing Experience

Get ready for massive updates!

On top of their ability to manage content on multiple platforms, **Headless CMSs were primarily created because developers want to use modern frontend frameworks**. React, Next.js, Vue, Nuxt.js, Svelte, Angular, you name it. Say bye to old, slow, unmaintainable, monolith CMS templating systems. Instead, these modern frameworks allow developers to build more performant websites through a fantastic Developer Experience. Developers and businesses benefit from this new architecture, as **higher performance** results in **better SEO, better User Experience, and stronger conversion rates**.

By splitting the frontend and the CMS, **the Editing Experience is not as great as it could be**. Editors (and certainly developers) miss live previews, inline editing, etc. We will fix that. **2024 will be dedicated to unifying the frontend and the CMS**, to offer a **fantastic Editing Experience**.

We will do this through a brand new **JavaScript/TypeScript SDK**, which will leverage the power of frontend frameworks, such as Next.js, to allow you to edit the content directly from within your frontend application.

![Strapi Editing Experience Preview](https://api-prod.strapi.io/uploads/Strapi_Editing_Experience_Preview_a70a0b6320.png)

On top of this massive update, we will introduce significant improvements to Strapi. v5 will be live by the end of Q2, with solid updates: full **TypeScript** support, the ability to have a **draft version of an already published entry**, [Vite](https://vitejs.dev/) instead of Webpack, **simpler API format** (bye "data.attributes"), and more!

We will release top-notch features, such as **Releases** (publish multiple entries, at a defined date and time, simultaneously) and **Content History** (see the previous versions of an entry and rollback within one click).

We will also allow **nested components** and release **conditional fields**.

### Deployment seamless

We received fantastic feedback about [Strapi Cloud](https://strapi.io/cloud), and look forward to making it even better! First, we will release a **cheaper tier**, which will start as low as **$29/month**. As much as we want to unify the frontend and the CMS, we will make Strapi and Strapi Cloud one single experience. We want to make using Strapi extremely easy. To do so, we will introduce a **CLI** that will deploy every Strapi project in seconds with an extremely fast **build time**. We will add a **multiple environments** feature.

This is quite a list of improvements, right?

## Ready for 2024? 🚀

We are more excited than ever about the future of Strapi, so we hope you are 🤓

2024 will be a fantastic year for Strapi. Looking forward to building this together with you!

Looking forward to celebrating 2023 achievements together and knowing more about what's next in 2024? Register [here](https://app.livestorm.co/strapi/community-call-jan-2024-strapi-mission-road-map-and-updates) for the Community Call we will have today (Jan 9, 2024)!