ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Contact

Pick the door that fits the conversation.

Five doors, five teams, five response cadences. An architect, a product specialist, a content team, the partner programme or the communications team — depending on what you need.

Five categories, five forms

Each form carries the fields the receiving team needs to respond well. Skip the generic-contact-form experience.

Talk to an architect

Architecture conversation with a senior engineer — platform, data, AI / MCP, operations, security, application surface. The default door for technical and platform discovery. Two-business-day response. → /contact/architect.html

Book a product demo

Hands-on demo of one of the Apps — ERP, CRM, HR or Project Management — at the workflow you care about. 30 minutes, real screens, real data. → /contact/demo.html

Request a datasheet

The product or capability datasheet in PDF — modules covered, deployment models, fiscal coverage, integration surfaces. Delivered by email. → /contact/datasheet.html

Apply to be a partner

The Airtool partner programme. Implementation partners, technology partners and resellers reach out via the partner form on the Partners page. → /partners/index.html

Press & analyst

Press inquiries, analyst briefings and speaking requests. Senior engineers available for technical briefings on the platform, AI / MCP, and the modernisation practice. → /contact/press.html

Why a router, not one form for everything.

A generic contact form forces the receiving team to triage intent from a free-text message — slow, lossy, and not the experience an enterprise architect expects from a serious platform company. Each of the five doors above maps to a different team with a different response cadence and a different operational context.

For ongoing customers, the support channels and account contacts are documented in your engagement. Please use those for in-flight work rather than this page.

Architect / demo / datasheet : two business days

The architect responds for discovery and platform questions ; the product team responds for demos ; the content team responds for datasheet downloads.

Partners : two business days

The partner programme team responds with the next-step packet — onboarding, certification path, commercial framework.

Press : one business day

Time-sensitive press and analyst requests handled on shorter cadence. Senior engineers reachable for credible briefings on short notice.

Engineering team across three continents

Spain (Barcelona), Peru (Lima) and Pakistan (Islamabad). The architect on your call is the engineer who would deliver the engagement.