Stuck on Strapi v3 or an early v4
A project built on v3 before the entity service existed, or an early v4 install with plugins that no one has touched in years. Security patches have long since moved on.
Upgraded onto a supported version
Running Strapi?
Strapi gives you a self-hosted headless CMS that you own, which is a feature until an upgrade breaks half the plugins and nobody has time to fix them. Most of the Strapi work we handle is older v3 and v4 projects that need to move forward without losing the content models the editors have built around.
What it is
Strapi is an open-source, Node.js headless CMS first released in 2015 by the team that would become Strapi Inc. Unlike Contentful or Sanity, Strapi runs on your infrastructure, backed by your own Postgres, MySQL, SQLite or MariaDB, and the admin panel is served from the same application.
The project has shipped three major versions: v3 (2020), v4 (2021) with the entity service API and rewritten admin, and v5 (2024) with the Document Service API and TypeScript throughout. Each version bumped how plugins are built, which is the single biggest source of upgrade pain. Strapi offers a hosted Cloud product, though the majority of production installs are self-hosted on AWS, DigitalOcean, Render or Heroku.
The honest version
No technology is all upside. This is where Strapi earns its place and where it tends to cause trouble.
Sound familiar?
The Strapi problems that bring people to us, and what you have once each one is fixed.
A project built on v3 before the entity service existed, or an early v4 install with plugins that no one has touched in years. Security patches have long since moved on.
Upgraded onto a supported version
A plugin that assumed the v3 or early v4 API, a service renamed between minor versions, or a yarn upgrade that caught a peer dependency mid-stream. The admin refuses to start.
Plugins compatible, admin healthy
A busy custom controller leaking connections, a Postgres instance sized smaller than the traffic needs, or a connection pool left at the default while the app has eight workers.
Pool sized to real load
A production container with 512 MB trying to run webpack through the Strapi admin build. We pre-build the admin in CI and ship the output, which fixes it for good.
Admin built in CI, container slim
The default local uploads provider on an ephemeral container filesystem. Every deploy wipes the directory, and editors slowly lose faith in the system.
Uploads on S3 or compatible storage
The .env was never fully populated when the app was deployed from a developer's laptop, so required secrets are missing and the admin exits on startup.
Secrets managed, startup deterministic
A content type added or edited in one environment and the schema file not committed, leaving staging and production disagreeing about what the model looks like.
Schema in Git, environments aligned
A Postgres dump that is scheduled but never restored, and uploads that live on a disk nobody has ever imaged. A restore drill reveals both problems at the worst possible time.
Backups tested on a fresh machine
What we do
Call us for one broken plugin, or hand over the whole installation.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
There is no in-place path from v3 to v5. We stand up a v4 or v5 instance alongside the existing one, define the content types that match the old schema, write a migration that moves data through the APIs rather than through the database, and move the front end over once the parity is proven. v3 keeps serving until the cutover and then it retires.
The common causes are a missing JWT_SECRET or APP_KEYS in the environment, a plugin that failed to load and took the app down with it, or a schema file on disk that disagrees with the database. The server logs usually name the culprit, and most of the fixes are one line in the .env or one plugin pinned to a known-good version.
Self-host when you want to control the database, run inside a specific network, or save on the Cloud subscription at a scale where ops time is cheaper than hosting fees. Move to Cloud when nobody on the team wants to look after Node, Postgres and the admin build any longer. The right answer depends on what your team already does for a living.
Not if they are on the default local provider on an ephemeral container filesystem. Every redeploy or reboot wipes them. We switch the upload provider to S3 or Cloudinary, migrate the existing files once, and confirm new uploads land in the bucket before anything is deleted locally.
Strapi when owning the data layer and the SQL database matters. Contentful when the editor group is large and roles and environments are part of the ask. Sanity when the Studio should feel like part of the application codebase. We will say which one matches your team in plain language before any migration starts.
The initial quote is free. Share the Strapi version and what you need done, and we come back with a scope and a number before the first commit lands.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: