Islamabad — an established Pakistani operation, engineering-deep.
A Pakistani legal entity, alongside Spain, Peru and Colombia — engineered to serve regional enterprises directly and to anchor a senior engineering practice on the same codebase and the same accountability as Spain. The European working day extends six hours through ours, by deliberate construction.
Established operation
A Pakistani legal entity, with the engineering and delivery accountability that comes with running an operation locally — not a partner arrangement at arm's length, not a back-office extension of another centre.
Senior engineering anchor in Asia
Principal engineers, platform architects, AI and database specialists in Islamabad — staffed for depth, not headcount. The engineering centre that anchors the platform's regional capability.
Time-zoned for European delivery
GMT+5. The Spanish working day overlaps Islamabad's from morning through late afternoon. The handoff between Spain and Pakistan is a working session, not a relay.
One engineering team across regions
Islamabad is not a separate company. It is the same engineering team that delivers in Spain, Peru and Colombia, with the same shared codebase and joint architecture decisions.
Why Pakistan, why Islamabad
Islamabad is the right Asian anchor because the engineering talent pool is deep, the time-zone math works for European delivery, and the legal-entity structure puts the company on the ground commercially — not only as an engineering extension of Spain.
The Pakistani operation does two things at once : it engineers the platform, the application tooling and the AI surface that our customers run on, and it carries the legal-entity standing to engage regional enterprise customers directly, on Axional or on Airtool, when the conversation arrives.
What the Islamabad operation delivers
Engineering capability and regional commercial standing — engineering-deep, locally established.
Platform engineering
The Airtool runtime — Jetty, Jersey, GraalVM, virtual threads, JDBC pool, replica clustering, microservice mesh. Senior engineers writing the platform that runs the company's customers.
Microservices
Eighteen specialised gRPC microservices for document rendering, OCR, diagram generation, cloud connectors, image processing and more. Each is a separate JVM process; each has its own ownership.
AI and MCP
Multi-provider AI abstraction, RAG over multiple vector stores (Qdrant, Milvus, pgvector, Redis), governed SQL agents, MCP server. The AI surface of the platform is engineered here.
Frontend engineering
Vue 3.5, Vuetify 4, TypeScript 5.8, Vite 6. The browser-side application surface for the platform's built-in applications and partner-deployed apps.
Application tooling
Schema importers, dictionary materialisers, metadata-driven UI generators and integration tooling — the engineering that makes large enterprise programmes deliverable without a full-stack team.
Observability and operations
The MemDB schemas (jvm, jdbc, cache, statistics, machine), the dashboards on top of them, the SRE tooling that runs the platform in customer environments.
The framing matters
The Pakistani operation is part of the company's core engineering function, not a back-office extension of it. The engineers here are paid as engineers, treated as engineers and trusted with the codebase. The legal entity in Islamabad makes that commitment structural, not optional.
What the customer sees is what we sell — senior engineering capability, time-zoned for European delivery, on the same codebase and the same accountability as Spain, with a local legal entity ready to engage regional enterprise customers when the conversation arrives.