The enterprise application platform for mission-critical operations.
Many applications on one supervised runtime — scale, security, observability and audit handled by the platform, not by each application.
What Airtool is
Airtool is a complete enterprise application platform — not a framework, not a low-level runtime, not an integration layer. A supervised JVM-class runtime owns HTTP, threads, sessions, security, observability and audit. A dictionary-driven model lets applications be metadata rather than compiled artefacts. Seven OLTP engines and three OLAP engines are addressed natively. Eighteen specialised microservices handle document rendering, AI inference, cloud connectors and image processing. Multi-provider AI and a native MCP server operate inside the user's permission perimeter by construction. One product, with the breadth a critical-operations customer needs.
Cloud multi-tenancy is structural. One installation hosts many applications from many companies. Tenant identity is bound per request at the runtime layer; tenant data is routed to the right database engine through a per-tenant pool; row and column security expressions are injected by the platform's query compiler. Multiple companies share infrastructure; they never share data — and the application cannot bypass the boundary because the boundary is the runtime's, not the application's.
Horizontal scale is a property of the runtime, not an operational project. Nodes are stateless. The two-tier dictionary cache invalidates cluster-wide through Redis pub/sub in milliseconds. Adding capacity is adding a node; the cluster coordinates itself. There is no Kubernetes orchestration layer to operate, no service-mesh sidecar to configure, no separate scaling control plane to learn. The supervised runtime handles what an external orchestrator would otherwise have to.
The engineering team behind Airtool
The Airtool platform is engineered by a team with deep experience in enterprise systems. The same engineers who have shipped mission-critical software for healthcare, industrial, distribution and public-sector customers across European enterprises engineer the platform you read about on this site. Many of the architectural ideas in Airtool — the metadata-driven application model, the supervised runtime, the multi-database portability — come from a long history of shipping enterprise systems and learning what works at scale. The platform itself is a recent build on a modern JDK 25 / Jetty 12 / virtual-thread foundation; the experience behind it is older.
The team operates from offices in Barcelona, Madrid and Lima, with a senior engineering centre in Pakistan time-zoned for European delivery. One codebase, one engineering team, one accountability — across the platform and across every customer engagement that runs on it.
What we stand for
Engineering for longevity
We build mission-critical systems engineered to outlive their architects. Three platform generations. Same engineering DNA. Long-horizon by construction, not by accident.
Supervised execution
The platform owns the infrastructure, not the application. Security, multi-tenancy, observability and audit are guarantees, not options. Misbehaviour degrades; it never collapses the host.
Honest competence
We declare in writing what we are good at and what we are not. The database tier table is an example — Tier-1 DBA depth on a small set, development on the rest. Honesty is itself a positioning lever.
One team, one accountability
The engineers who build the platform are the engineers who deliver the customer programmes. The same team responds to the support ticket, runs the modernisation pilot and ships the next platform release. No hand-offs.
Where we work from
Iberia is the headquarters and the operational heart of the team. Latin America — through our Lima office — is the gateway to the Andean countries and the Spanish-speaking partner ecosystem. Pakistan is our senior engineering centre, time-zoned for European delivery, on the same codebase and under the same accountability as Iberia. Airtool delivery happens from all three regions, with the same engineering team across them.