From legacy enterprise stacks to a metadata-driven runtime — without losing the business logic that runs the company.

What your modernised application will look like.

Airtool Apps — our own enterprise application suite — runs on the same platform the modernised version of your legacy stack will run on. Same metadata-generated UI, same supervised runtime, same OLTP and OLAP portability, same AI and MCP perimeter, same observability surface. Apps is the picture of what a finished modernisation looks like in production.

The implication for budgeting and planning is concrete : every platform-core capability — multi-tenancy, audit trail, row and column security, AI inside the perimeter, real-time observability — is inherited automatically by every form, every report, every module. Modernisation isn't translating your legacy stack into custom application code with these features rebuilt; it is lifting your schema and database business logic onto a runtime that already provides them.

Why this order matters

Most modernisations get this exactly backwards. They start with the UI because the UI is what the customer can see. They build the screens first, then realise the business rules behind the screens have to come from somewhere. They translate the rules into application code, and translation is where institutional knowledge is lost.

Our order is the order in which value compounds. The schema is the least negotiable layer — we import it. The database logic is the most expensive to lose — we preserve it. Metadata is the highest-leverage layer — we author it once and the platform reuses it. The middle tier is the smallest deliberate surface area we can get away with. The UI is generated, so it costs nothing per screen.

Why the platform makes it possible

The methodology is not separable from the platform. Every layer depends on a specific Airtool capability that does not exist in generic application servers or visual-builder frameworks.

The schema importer depends on the dictionary's multi-engine portability and its declarative table-object model. Database business-logic preservation depends on the schema compiler's SPL/trigger sequencing and per-object timestamp tracking. Metadata depends on the runtime's Redis-coordinated cluster cache and the supervised execution model. The middle tier depends on GraalVM Polyglot's controlled execution policies and the platform's standard library. The generated UI depends on the metadata model itself.

We do not sell modernisation as a service that happens to use a platform. We sell modernisation as the natural consequence of the platform's architecture — applied by the engineers who wrote that architecture.