Next.js agency: App Router, strict TypeScript and React

We do not just consume the React ecosystem: we contribute to it. Our plugins are published on npm and run in production on the sites we operate.

Next.js App Router, strict TypeScript, Server Components: these are not sales arguments. They are the constraints we impose on every project, because they produce faster, safer and more maintainable sites.

What we build with Next.js

App Router development

Server Components, Server Actions, API routes, native cache management. Our packages declare their supported versions in their package.json, readable on npm.

Strict TypeScript

No compromise on type rigour. A bug caught at compile time costs less than a bug caught in production.

Strapi v5 integration

Content modelling, Dynamic Zones, custom fields via our @isomorph-agency/strapi-plugin-link plugin. Front-end and back-end share the same types.

See our Strapi agency page for projects built on a Strapi v5 back-end.

Performance and Core Web Vitals

LCP, INP, CLS measured in real data (CrUX). Optimisations target the metrics that matter for Google Search.

RGAA 4.1.2 accessibility

Semantic HTML, verified contrasts, keyboard navigation, visible focus. This is not a billable option.

Deployment and hosting

Front-end on Vercel, Strapi back-end on Scaleway (France). Reproducible stack, documented, transferable to another team.

Why we host on French infrastructure (in French): our article on sovereign hosting.

Our code, installed by other teams

npm packages published by ISOMORPH, downloads over 30 days
PackageVersionDownloads (30 days)
@isomorph-agency/cookie-consent1.0.7751
strapi-plugin-cookie-consent1.0.4675
strapi-plugin-cookie-consent-v41.0.5586
@isomorph-agency/link-resolver0.1.2425
@isomorph-agency/strapi-plugin-link0.1.1275

npm registry snapshot, July 30, 2026, covering June 30 to July 29, 2026. Each figure is verifiable package by package on npmjs.com.

Two MIT-licensed repositories on github.com/agenceisomorph: cookie-consent, strapi-plugin-link-v2.

Four standards, on every project

RGAA 4.1.2

Accessibility

RGESN

Eco-design

Core Web Vitals

Performance

OWASP Top 10

Security

How a project runs

01

Scoping

Stack validated, dependencies decided, route structure defined.

02

Development

Components, routes, Server Actions, CMS integration.

03

Testing and acceptance

Performance, accessibility, security on staging.

04

Go-live

Deployment, DNS configuration, documentation.

We quote after a written scoping exercise, never from a rate card.

Let's talk about your Next.js project

Redesign, migration from another stack or new build: describe your need. We come back with a written scoping document.

By email