Technology stack: Next.js, React, Strapi, NestJS, Angular and PostgreSQL Tools chosen for software that keeps running
ANTASY IT (a.it) builds most web front ends with Next.js and React in TypeScript, business back ends with Strapi 5 or NestJS, and keeps data in PostgreSQL. Angular serves some dense back offices. The systems run on Linux servers behind Cloudflare. Every tool on this page is tied to a system in production today.
- Language
- TypeScript, front and back
- Default pair
- Next.js and Strapi
- Database
- PostgreSQL
- Hosting
- Linux, nginx, Cloudflare
Stack
What technology stack does ANTASY IT use?
TypeScript end to end. Next.js and React for websites, stores and most application front ends; Angular with PrimeNG for some dense back offices; Strapi 5 or NestJS for APIs and business rules; PostgreSQL for data, through Prisma or plain SQL; Linux, nginx and Cloudflare for hosting. The table shows where each tool runs today.
| Layer | Tools | In production at | Why |
|---|---|---|---|
| Websites and stores | Next.js, React | cspddammak.com, espamedical.com, Key Brothers, Made in Tunisia, this site | Pages rendered on the server: fast first display, fully readable by search engines |
| Business applications | Next.js (App Router), React | TSS Company ERP, SOLARP for Thyna Solar | One TypeScript code base for screens and server logic; rights checked on the server |
| Dense back offices | Angular, PrimeNG | Jardin d’Enfants Anous SaaS, Facturty | A strict structure and rich data tables for forms used all day long |
| Back ends and content | Strapi 5 | TSS Company ERP, Facturty, the cspddammak.com content | Content types, roles and an admin panel ready on day one; business rules in custom controllers |
| Application APIs | NestJS, Node.js | Jardin d’Enfants Anous SaaS | Modules and guards that keep business rules and access rights in one structured API |
| Live updates | Redis (publish/subscribe), server-sent events | Made in Tunisia | An order or a reservation made on one application process reaches every open dashboard at once |
| Data | PostgreSQL; Prisma or plain SQL | TSS Company, SOLARP, Jardin d’Enfants Anous; Prisma at Key Brothers and Made in Tunisia | Transactions and constraints that keep stock, balances and documents consistent |
| AI | Mistral’s Pixtral vision model | Facturty: reading supplier invoices | Fields read from a photo of an invoice and returned as structured data |
| Hosting and operations | Linux, nginx, pm2, Cloudflare | Most client systems shown on this site | Open, standard layers that we know end to end, with no proprietary platform to leave |
Defaults
Why Next.js and Strapi by default?
Because together they cover most of what our clients ask for. Next.js serves fast pages that search engines read in full, and Strapi gives administrators a ready back office with roles, while custom controllers hold the business rules. Both are open source, written in TypeScript and self-hosted, so a client is never tied to a platform.
- Next.js at ANTASY IT
The Next.js systems we run, how we set them up, what production taught us.
- Strapi at ANTASY IT
Strapi 5 back ends for an ERP, a billing product and a store.
Choosing
Next.js or WordPress: which should you choose?
WordPress if the site is mostly pages and posts that your team edits, with standard features covered by well-known plugins. Next.js, with a headless CMS such as Strapi, when the site carries business logic, several languages, links to your software or a strict speed budget. ANTASY IT builds with Next.js, and says so when WordPress would serve you better.
| Criterion | WordPress | Next.js + Strapi |
|---|---|---|
| What it is | A CMS with themes and plugins, rendered in PHP | A React framework for the site, with a separate CMS for the content |
| Editing | Built in, familiar to many editors | Strapi’s admin panel, with content types shaped to your data |
| Business logic | Through plugins or custom PHP | In TypeScript, inside the application |
| Speed | Depends on the theme, the plugins and the cache | Pages rendered on the server, and only the JavaScript each page needs |
| Several languages | Through a plugin | In the routing itself, with translated URLs (as on this site) |
| Upkeep | Frequent updates of core, theme and plugins | Framework and library updates, done by the developer |
| Best when | A content site edited daily, standard features, a tight budget | A site linked to your software, a catalogue or store, specific rules |
Your stack
Can you work with our existing stack?
Yes, when it is a stack we know: React, TypeScript, Node.js, NestJS, Angular, PostgreSQL, Prisma, Redis and REST APIs. With agencies and product teams, we work in your repository, with your conventions, your reviews and your deployment pipeline. When a request falls outside what we run in production, we say so before quoting rather than learning on your project.
- React
- Next.js
- TypeScript
- Node.js
- NestJS
- Angular
- Strapi
- PostgreSQL
- Prisma
- Redis
- REST
Production
What running these tools taught us
Six problems we met on systems in production, and what we changed. This is the knowledge you pay for when you hire a team that also runs what it builds.
- Pages that never updated
- Next.js marks pre-rendered pages as cacheable for a year. Behind Cloudflare, a deployment could stay invisible for weeks while old pages called scripts that no longer existed. Our pages now send revalidating cache headers, and each build carries its own deployment identifier.
- Security headers lost by one line
- In nginx, a single add_header inside a location block silently drops every header set at server level. Security headers went missing that way on two production apps. They now live in one shared file, included in every location.
- Arabic printed in the wrong order
- An Arabic date inside a French line comes out scrambled by the bidirectional text algorithm, and common PDF libraries do not join Arabic letters. Our documents isolate Arabic text in the data itself and are printed through a real browser engine.
- Millimes rounded away
- The Tunisian dinar has three decimals. Strapi’s default decimal columns kept two, so 14.875 became 14.88 in the database. Money columns were migrated to three decimals, and our money fields accept the decimal comma that French-speaking users type.
- Invoice lines invisible to hooks
- Strapi 5 saves components, such as document lines, before its lifecycle hooks run, so a hook cannot total them. Document totals are computed in the controller, and stock and balance updates happen after saving.
- Image resizing that ran out of memory
- On-the-fly AVIF conversion of a product catalogue pushed a small server beyond its memory and restarted the site. Serving WebP only, caching the results and capping the process memory fixed it.
Talk to the people who run the stack
Describe your project or your current stack. We tell you what we would keep, what we would use and why.