Strapi
Strapi is an open-source headless CMS used for building fast and easily manageable APIs written in JavaScript.
What detecting Strapi tells you about a site
Strapi is the leading open-source, self-hosted headless CMS built on Node. Being self-hosted, its prints are path- and API-shaped rather than vendor-CDN: an /admin Strapi panel, uploaded media under /uploads/, REST endpoints shaped like /api/<collection>, and Strapi's default JSON envelope ({ data, meta }). Spotting it signals a team that wanted a headless CMS but kept its content database and hosting in-house — a control-, cost- or data-residency-driven choice over a SaaS like Contentful or Sanity.
Strapi in a real-world stack
When you find Strapi, it rarely travels alone. Node on the server with PostgreSQL or MySQL, and a decoupled Next.js/Nuxt/Astro front end consuming its API.
About
Strapi is an open-source headless CMS used for building fast and easily manageable APIs written in JavaScript.
Categories: CMS
Quick facts
Detection methodology for CMS
For content management systems we lean on the most stable signals each platform leaves behind: the `<meta name="generator">` tag, asset URL prefixes (`/wp-content/`, `/sites/default/files/`, `/cdn.shopify.com/`), distinctive cookie namespaces (`wordpress_*`, `_shopify_*`, `Drupal.*`) and admin-route signatures (`/wp-admin/`, `/user/login`). When the visible site is a JavaScript framework with a headless CMS underneath, we surface the CMS SDK from the bundle (`@sanity/client`, `contentful`, `@storyblok/react`) — the fingerprint that survives even when the HTML carries no traditional CMS markers.
How we detect Strapi
Sourcemap Explorer carries 2 fingerprint signals for Strapi, spread across 2 channels — response header and script src url. The exact patterns are listed below, and you can replay each one in Chrome DevTools to confirm a match by hand.
Each signal alone is rarely conclusive — Sourcemap Explorer cross-references all of them and weights by confidence. You can reproduce any of these checks yourself in Chrome DevTools.
Server-side fingerprint: the response header reveals the technology behind the page. Visible in DevTools → Network → response headers.
X-Powered-By: ^Strapi
Script URL pattern. Typically a CDN host or chunk path that ships with the technology.
(?://|-)strapi-|strapi_jwt
FAQ
How do I check if a website is using Strapi?
Open the page in Chrome, click the Sourcemap Explorer toolbar icon, and read the Stack tab. Strapi's specific fingerprints here are response header and script src url, and the popup flags Strapi whenever any combination of them is found. The same checks can be reproduced manually in DevTools — see the "How we detect" section above.
What Strapi version can Sourcemap Explorer detect?
Strapi ships as a hosted cms rather than a bundled npm package, so version-specific detection isn't always possible. Where the platform leaks a version in response headers (`X-Powered-By`, `Server`, generator meta tags) we surface it; otherwise we report presence only.
Is Strapi open source?
Yes, Strapi is open source. The license details are listed on the official site (https://strapi.io), and the codebase typically lives on a public source-control host.
Where can I read more about Strapi?
Official site: https://strapi.io. For Sourcemap Explorer's detection guide, see the deep-dive link below or the related guides in the cross-link section.
Keep reading on Sourcemap Explorer
Practical guides
Detection deep dives
Alternative tools
Detected by Sourcemap Explorer
Open the popup on any page running Strapiand you'll see the exact version pulled from the bundled package.json when sourcemaps are exposed.