Strapi development
Scalable, API-first content platforms built withStrapi CMS and React.js frontends
Your editors need a proper admin panel and your site needs a clean API, or your Strapi 4 project has run out of support. Strapi gives editors an admin panel and gives developers a REST or GraphQL API, leaving you free to build any front end on it. We model the content, set up Strapi 5 and build the site or app on top. We also upgrade Strapi 4 projects, which no longer get updates.
What Strapi work covers
The content model is the part that lasts, so most of the thinking goes there.
Content modelling
Collection types, components and dynamic zones, planned with your editors so that a new page type doesn't need a developer each time.
Front ends on the API
React or Next.js sites and apps reading from Strapi, with previews for editors and caching so that the CMS isn't hit by every visitor.
Upgrades from Strapi 4
Running the upgrade tool on a copy, rewriting custom code and updating every API consumer for the new response format.
Custom plugins and integrations
Admin extensions and connections to search, email or commerce systems, written against the Document Service API.
Strapi, as of October 2026
From the Strapi 5 documentation. The first point matters to anyone still on v4.
Strapi 4 has ended
It reached end of life on 30 April 2026, and 4.26.2 is the final release. Strapi Cloud still runs v4 projects, but warns that this may change without notice.
Runtime: Active or Maintenance LTS Node.js
Strapi 5 currently supports Node.js 22, 24 and 26. Odd-numbered releases such as 25 aren't supported, so check your host before starting.
Databases: SQL only
MySQL 8.0+, MariaDB 10.3+, PostgreSQL 14+ and SQLite. Strapi says it does not support MongoDB, so an older project using it would have to migrate its data first.
Moving from Strapi 4 to 5
The upgrade tool is useful, but it won't touch the code that reads your API.
API responses changed shape
Strapi 5 uses a flattened response format, and no codemod covers it. Every website, app and integration that reads the API needs updating and testing.
documentId replaces id
API calls should use documentId rather than id. Codemods only partly handle this, and any stored references or links to entries need reviewing.
Entity Service is deprecated
Custom code moves to the Document Service API, where lifecycle hooks behave differently. Plugins are affected, and some may not have a Strapi 5 release at all.
There is no automatic way back
Data migrations run on first start and aren't reversed. Going back means restoring the backup and the v4 branch, so a tested backup is essential before you begin.
How a Strapi project runs
Editors are involved from the first step, because they are the daily users.
Model with your editors
We go through real pages and decide what is structured data and what is free content, and which rules each field needs.
Set roles and API access
We set who can edit and publish, and which tokens and public permissions the API exposes. These are easy to leave too open.
Build the front end
Your developers or ours build against the API with draft previews, so editors can see what they are about to publish.
Plan hosting and upgrades
Strapi is a Node.js application with a database and media, so it needs hosting, backups and updates. We document all of that.
How we price Strapi work
Separate the CMS and the front end when estimating. They are different amounts of work.
A v4 to v5 upgrade can be quoted after we have seen the custom code and listed the systems that read the API. A new content platform can be quoted once the model is agreed. Other work is charged by the hour from $20/h in USD, invoiced in USD, GBP, EUR or INR.
We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment. In the shared hours, editors can raise questions while we are working. If editors would be better served by a flat-file or PHP CMS, also consider Statamic or WordPress.
Why we name no Strapi projects
Most of our work is delivered under NDA, so many projects cannot be named.
This means the page has to rest on how we do the work, not on who it was for. Our WordPress page does list published headless CMS work, if you would like to see how we treat a separate content layer.
Questions about Strapi
From teams choosing a CMS or upgrading one.
We are on Strapi 4. What should we do?
Strapi or WordPress?
Does Strapi need a developer to run?
Must the front end be React?
Which content do your editors need to manage?
Send a few example pages, or your Strapi version and custom plugin list if you are upgrading. We will tell you what is involved.
We reply within one business day (IST).