Next.js development agency: business applications, stores and websites in production Next.js, from the first route to the running server
ANTASY IT (a.it) builds business applications, online stores and websites with Next.js, and runs most of them on servers we operate. An ERP, a CRM, two online stores, a multi-tenant product, a catalogue site and this website are Next.js systems in production today. Hire us for a project, under your agency’s brand, or inside your team.
- Router
- App Router
- In production
- Next.js 16 on our recent systems
- Data
- PostgreSQL, via Strapi, Prisma or SQL
- Hosting
- next start, nginx, Cloudflare
In production
What do we build with Next.js?
Business applications with many roles, online stores, multi-tenant products and fast company websites. Next.js systems built by ANTASY IT are in production at TSS Company (ERP), Thyna Solar (the SOLARP CRM), Key Brothers (store), ESPAMED (catalogue site) and the Damak group (cspddammak.com), as are our own Made in Tunisia product and this website.
| System | Type | What Next.js does there |
|---|---|---|
| TSS Company ERP | Business application | App Router screens for sales, purchasing, stock and the workshop, on a Strapi 5 API |
| SOLARP, at Thyna Solar | CRM | Screens and API in one process; every write checks the user’s rights, validates the input and runs in a database transaction |
| Key Brothers | Online store | Catalogue, cash-on-delivery checkout and an admin back office, with Prisma and PostgreSQL |
| Made in Tunisia (our product) | Multi-tenant SaaS | One application serves every venue’s QR menu; the venue is identified by the domain name of the request |
| espamedical.com (ESPAMED) | Catalogue website | Pages built from typed content modules, without a database; quote and contact forms |
| cspddammak.com (Damak group) | Store and group site | Storefront fed by a Strapi CMS |
| ait-tun.com (this site) | Bilingual company site | French and English with translated URLs; metadata, sitemap and structured data generated from the content |
Set-up
How do we set up a Next.js project?
Server components by default, with small client islands only where a page must react; TypeScript everywhere; data access and rights checked on the server; translated URLs when there are two languages; metadata and structured data generated from the same content as the page; and cache headers that let a new deployment show up at once.
- Rendering
- Server components first. Interactive parts, such as a menu, a form or a filter, are small client islands that receive only the strings they need, so pages ship less JavaScript.
- Data and rights
- Reads and writes run on the server, and the user’s rights are checked there, never only in the browser.
- Languages
- On this site, French and English each have translated URLs (/fr/methode, /en/process), linked by hreflang tags, and no message catalogue is sent to the browser.
- Search
- Titles, descriptions, canonical URLs, sitemaps, share images and JSON-LD come from the same content modules as the visible page, so they cannot drift apart.
- Images
- next/image with explicit sizes. On small servers we serve WebP only, because on-the-fly AVIF conversion costs too much memory.
- Deployment
- A production build served by next start under a process manager, behind nginx and Cloudflare, with revalidating cache headers and one deployment identifier per build.
Production
What production taught us about Next.js
Five problems met on Next.js systems we run, and the fix each one received.
- Pages cached for a year
- Next.js sends s-maxage=31536000 on pre-rendered pages, and Cloudflare honours it. Old HTML kept pointing to JavaScript files that the new build no longer had, while the cache status still read DYNAMIC. Pages now send max-age=0, must-revalidate, and builds are versioned.
- Public variables frozen at build time
- Variables prefixed NEXT_PUBLIC_ are written into the JavaScript during the build. Changing them on the server has no effect until the next build, so any change to them is treated as a new release.
- French URLs that redirected to themselves
- With Next.js 16.4 started on 127.0.0.1, rewritten URLs were compared with one host name and built with another, so every French page of this site answered with a redirect to itself. A configuration flag and a small fix in the proxy solved it before launch.
- Image optimisation and memory
- AVIF conversion of about a hundred product photos took a small server past its memory, and the process manager restarted the site. WebP only, a long cache for resized images and a memory cap on the process brought the peak back down.
- Builds on a shared server
- Development servers never run on production machines, and builds run with a memory cap, so building one application cannot starve the others that are serving clients.
Working with us
How can you hire Next.js developers from ANTASY IT?
In three ways: a fixed-price project built from a written scope; a white-label project delivered under your agency’s name; or Next.js developers who join your team for a monthly fee and work in your repository. In all three, the people writing your code also deploy and run Next.js in production.
- A fixed-price project
A written scope, an estimate by module, payment by milestone.
- White-label development
Your agency’s brand and client relationship; our delivery.
- A dedicated team
Next.js developers inside your team, for a monthly fee.
FAQ
Next.js questions
Is Next.js good for SEO?
Yes, when pages are rendered on the server: search engines and AI crawlers receive complete HTML with titles, descriptions and structured data. Rankings still depend on content, URLs, speed and internal links. This site, built with Next.js, generates its sitemap, hreflang tags and JSON-LD from the same content as its pages.
App Router or Pages Router?
The App Router for every new project: server components, nested layouts and streaming are built around it, and it is where Next.js puts its new features. For an existing Pages Router application, we keep what works and move route by route when there is a reason to, such as a new section, never as a big-bang rewrite.
Can you take over our existing Next.js application?
Yes, starting with a review of the version, rendering choices, data access, dependencies, hosting and cache headers. The review lists what to fix first and what can stay. Upgrades to a newer major version are planned as separate steps, tested on a staging address, because major versions of Next.js bring breaking changes.
Where do you host Next.js applications?
On Linux servers we operate: a production build served by next start under a process manager, behind nginx and Cloudflare. The code does not depend on our servers. A standard Next.js build runs on any Node.js host, including Vercel or your own infrastructure, and the hosting choice is written into the quote.
Which back end do you pair with Next.js?
It depends on the rules. Strapi 5 when administrators need a ready back office, as in the TSS Company ERP; Prisma or plain SQL inside the Next.js application for focused products, as at Key Brothers or in SOLARP; NestJS when one API serves several front ends. Every one of these systems stores its data in PostgreSQL.
Do you build multilingual Next.js sites?
Yes. This site runs in French and English with translated URLs, hreflang tags and one language switch that lands on the matching page. Right-to-left Arabic is part of our production work too: the kindergarten SaaS used by Jardin d’Enfants Anous prints its registers in Arabic, although it is built with Angular rather than Next.js.
A Next.js project, or Next.js developers?
Tell us what you are building and how far along it is. We reply with questions, then a written scope or a team proposal.