We maintain and extend content platforms built on Strapi.

We built a crypto newsroom and a hiring platform's MVP on Strapi.

Editorial platforms for newsrooms

Coinpaper's editors write in a Strapi CMS we extended for crypto coverage. Our Slate editor runs as a Strapi plugin, so a live price chart, a tweet or a related article goes straight into the text. Every save is a snapshot they can restore. A job that runs every minute publishes scheduled articles, and the Next.js front end regenerates pages in the background, so publishing never waits for a site rebuild.

We built Coinpaper's content platform on Strapi and Next.js, with a custom CMS for its crypto newsroom and a site that reached 100k+ monthly users.

100k+

Monthly users on the platform

3

Developers on the first release

Read the case study

Back ends for product MVPs

For hiretesters, a Canadian platform that connects QA and DevOps professionals with employers, we designed and built the MVP. Strapi, Redis and PostgreSQL sat underneath a Next.js front end written in TypeScript and React. The brief asked for strong SEO, solid embedding support and fast page generation. The platform launched in 2021.

We ran hiretesters' engagement end to end, from consultancy and brand to a freshly-branded MVP for a QA and DevOps hiring platform.

2021

Platform launched

MVP

Freshly-branded product shipped

Read the case study

Strapi served these projects well. For new builds we now recommend Payload or EmDash CMS.

• Official Payload Partner Payload Collections and permissions are TypeScript files in your repository, so a change to the content model goes through a pull request like any other code. See our Payload work
• Astro-native, 1.0 EmDash CMS EmDash runs inside the Astro application, and editors can build collections in its admin that generate TypeScript types for the site. We build and deploy EmDash sites for Astro projects with one editorial team. Explore EmDash services

Our Strapi vs Payload comparison covers databases, schema changes, permissions and paid governance, and names the cases where Strapi is still the stronger pick.

We extend Strapi platforms already in production, and move them to Payload when a rebuild makes more sense.

Four decisions make a Strapi platform easy or hard to change later.

• The content model comes first

  Before we build anything, we map the content types, how they relate and how editors will use them. A model shaped around the first use case alone usually needs reworking a few months in.

• Extensions you can upgrade

  Strapi extends through plugins, custom controllers and lifecycle hooks. We add a plugin only for a specific problem, because each one has to survive every Strapi upgrade. Coinpaper's editor and version snapshots both run as Strapi plugins.

• Built for the editors

  Field names, validation and permissions follow how the editorial team works. Coinpaper's admin warns an editor when a description runs past its limit and shows the last publication date on the edit page.

• Hosting with a plan

  Production Strapi needs monitoring, backups and updates. We deployed Coinpaper's CMS to Fly.io with separate staging and production environments, and every change shipped through GitHub Actions.

Questions we get asked about Strapi.

1. Do you still take on Strapi projects?

   Yes, for platforms that already run on Strapi. We maintain and extend existing builds: the content model, editorial workflow, custom plugins, performance and hosting. We still ship maintenance and new features for Coinpaper's Strapi platform.

2. Should we start a new project on Strapi?

   We recommend Payload or EmDash CMS for new builds. Our Strapi vs Payload comparison lists the cases where Strapi is still the stronger pick, such as a project that has to run on MySQL or MariaDB.

3. Can you migrate us from Strapi to Payload?

   Yes. Each Strapi content type becomes a Payload collection, and most fields map across directly. The work concentrates in components, dynamic zones, media and relations. Our Strapi to Payload migration guide covers the field mapping in detail.

4. How does an engagement start?

   With a consultation that costs nothing. After it we write the scope down and agree a fixed price against it, and the work starts once both are signed off.