The technologies we use, and why we chose them

No technology is good or bad in the abstract: it solves one problem and creates others. Here are those trade-offs, technology by technology.

Websites and web interfaces

What your users see. The choice comes down to display speed, server-side rendering and how long the project needs to last.

AngularApplication framework
Native server-side rendering, strict typing and an enforced structure. An Angular project picked up three years later is still readable.
ReactInterface library
The largest ecosystem of components, and a natural choice when your team already knows it.
Next.jsReact framework
React with server rendering and routing built in, for websites that need to be found on Google.
Nuxt.jsVue framework
The same strengths on the Vue side: server rendering, routing and a quick start for content sites.
TypeScriptLanguage
Type errors show up at compile time rather than in production. Our default choice on a project meant to last.
JavaScriptLanguage
The language of the browser. We take over existing projects written without TypeScript with no difficulty.

Servers and APIs

Where the business rules and data live. The criterion is long-term solidity, not fashion.

ASP.NET.NET server framework
High performance, a mature ecosystem and long-term support. Our default choice for business software.
Spring BootJava server framework
The standard for Java information systems. The right choice when what you already have runs on Java.
Express.jsNode.js server framework
Light and quick to set up: a simple API, in the same language as the interface.
Node.jsServer runtime
Server rendering for websites and automations, in the same language from browser to server.

Mobile and desktop

One codebase for iOS and Android, and for the desktop when the project justifies it. Two separate apps cost twice as much.

FlutterCross-platform framework
One codebase for mobile and desktop, with identical rendering everywhere.
React NativeMobile framework
Real iOS and Android apps in React, when your web interface is already written in it.
Ionic AngularMobile framework
A mobile app built on Angular skills, for internal tools and form-based applications.

Data

The database is chosen according to the shape and volume of your data. It is the hardest decision to change later.

MySQLRelational database
Proven, available from every host, and more than enough for most SMEs.
MongoDBDocument database
For data whose shape varies a lot, or changes quickly early in a project.
SQLiteEmbedded database
No server to manage: the right choice for a desktop app, offline mobile use or a small website.

Artificial intelligence

Building blocks chosen for what they let you control, not for show.

API AnthropicLanguage models
Quality of reasoning on long documents and clear contractual terms on how data is used.
RAGRetrieval-augmented generation
The model answers from your documents and cites its sources, instead of drawing on its memory.
MCPModel Context Protocol
Gives the model explicit, limited access to your internal tools, which makes every action auditable.
Pipelines multi-agentsOrchestration
Splitting a task into specialised stages makes each link testable and replaceable.

The right technology depends on your context

The choice is justified during scoping, with the alternatives ruled out and the reasons why. Describe your project.

Reply within one working day. You can also write to contact@chenit.eu or call 0456 71 39 98.