What We Deliver with Strapi
- a content model: types, fields, relations and reusable blocks, shown to your editors before frontend work begins;
- roles, drafts, publishing and language versions set up around your approval process;
- a frontend on Next.js, Nuxt or Astro that pulls data from Strapi, with preview so editors can check a page before publishing;
- REST or GraphQL APIs for mobile apps, so banners, screen text and promotions change without a new App Store or Google Play release;
- integrations: products or schedules from your accounting system, form submissions to your CRM, Slack or email notifications, automatic page rebuilds after publishing, site search;
- deployment on your server or in the cloud, backups and upgrades to new Strapi versions.
When Strapi Is Right, and When We'd Suggest Something Else
Strapi suits teams that publish to several channels, want freedom to redesign the frontend without migrating content, or need custom logic written in JavaScript and TypeScript. We recommend a different route if:
- you have a single corporate website or blog and no other channels: WordPress is simpler and cheaper;
- the site rarely changes and a developer updates it: a static Astro site without a separate CMS is enough;
- the project runs on Python and Django and content should sit next to the rest of the logic: Wagtail is a better fit.
Be ready for the trade-off: Strapi and the website are two applications to build, deploy and maintain, which costs more than one site on a traditional CMS.
New Project or Migration
A new project is designed with every channel in mind from the start, so a mobile app added later does not force a restructure. A migration from another CMS happens in phases: content model and data migration first, then the website, and the domain switches only after testing. Old URLs are redirected so you do not lose search traffic. For apps, we set up the same APIs for native and cross-platform apps.
What We Need from You
- A list of the places your content appears: site pages, app screens, newsletters, partner feeds.
- Examples of your current content and who edits it today.
- Access to the old site or spreadsheets if content must be migrated.
- Your hosting preferences and any data location requirements.
What Affects Cost and Timeline
- Size of the content model: number of types, fields, relations and blocks.
- Channels: only the website, or also an app and external services.
- Frontend: design, number of page templates and performance requirements.
- Languages and roles: language versions and how complex content approval is.
- Migration: volume and condition of content in the old system.
- Upgrades: moving between major Strapi versions has required noticeable rework, so we plan it into support.
Frequently asked questions
Is Strapi hard for editors to use? No. The admin panel is built around your content, so there are no unnecessary menus. Much depends on how well the structure is designed, which is why we test it with your editors first.
Where is the data stored? On a server you choose: your own, a cloud provider or hosting from Strapi's developer. The database is usually PostgreSQL or MySQL.
Does a headless setup hurt SEO? Not by itself. We build the frontend so search engines receive fully rendered pages with all text and meta tags.
Can we redesign the site later without touching the content? Yes. The new frontend connects to the same API, and editors do not migrate anything.
Can Strapi work alongside an online store? Yes. Products and orders stay in the ecommerce platform, while Strapi handles articles, lookbooks and brand pages.
Are there paid parts of Strapi? The free version can be deployed on your own server. Strapi's developer sells paid plans with extra features and cloud hosting, and we discuss whether you need them before work begins.
Why Promodex
Promodex has built websites, apps and web services since 2015, with 750+ projects delivered. We look at Strapi as one part of the whole product, from the frontend and the app to analytics and SEO, and one in-house team covers all of it. If a headless approach is overkill for your needs, we will say so, and after launch we keep Strapi updated and add new content types.