Technology stack
Technologies for sustainable digital platforms
We choose tools based on the problem they solve, their support, and their ability to integrate. Drupal organizes content; the rest of the stack extends search, infrastructure, interfaces, and automation when the project needs it.
The stack we integrate
Drupal
Open source CMS for portals with editorial workflows, permissions, structured content, and integrations.
Apache Solr
Search, facets, and relevance for document catalogs and portals with large volumes of content.
NGINX
Web server and reverse proxy for delivery, TLS, caching, and traffic distribution.
Angular
Decoupled web interfaces when complex interaction justifies a standalone application.
Java
Integration with enterprise services and systems already part of the institutional architecture.
Node.js
APIs, automations, webhooks, and network services that complement the editorial platform.
Vercel
Deployment of modern frontends, previews, and global delivery in decoupled architectures.
NestJS
We design enterprise APIs and integrations with NestJS, TypeScript, and a modular architecture ready for security, testing, and continuous operation.
Next.js
We build decoupled frontends with Next.js to integrate Drupal and other CMS platforms, improving performance, technical SEO, and verifiable deployment flows.
Payload CMS
We implement Payload CMS to model headless content, permissions, versions, and APIs in projects with technical control and a flexible editorial experience.
WordPress
We build and modernize WordPress sites with blocks, integrations, security, and sustainable operation for content teams and digital channels.
Contentful
We integrate Contentful as a headless content platform to distribute reusable models to sites, applications, and omnichannel experiences.
Dify
Building AI agents, prompt versioning, and knowledge bases with RAG, with the option to self-host.
n8n
Workflow orchestration and integration between CRM, ERP, databases, and our own APIs, deployable on your own infrastructure.
How we choose a technology
We start from the users, the content, the integrations, the service level, and the capabilities of the team that will operate the solution. We then compare security, accessibility, maintainability, total cost, and ease of observability. A technology doesn't get into the project just because it's trending.
We always look for the simplest architecture that meets the requirements. An editorial portal can be solved entirely in Drupal; an advanced search may need Solr; a highly interactive experience may justify Angular; and an asynchronous integration may fit better in Node.js. Every piece needs a clear boundary and a clear owner.
Need to define or modernize your architecture?
We review the current state, the risks, and a verifiable technical path.