How it works
How we work and why exactly this way.
Six topics that come up in every client conversation: from where the data lives to what parting ways with us looks like. We explain them here the same way we do in meetings, concretely and without technical jargon.
AI generators
Code that nobody has read.
Tools that generate applications from a description, such as Lovable, Bolt, or Replit, are among the fastest-growing products in the history of software. What they produce, however, is code: thousands of lines nobody has read. The vendors themselves note in the fine print that these are prototypes to be rewritten before production use.
The industry knows this script from the days of Access and Excel macros. First the enthusiasm, then the applications grow into critical processes, until finally someone has to audit them, secure them, and integrate them with the rest of the company. The only documentation turns out to be a chat history.
On our platform, AI leaves no code behind to read. It builds the application as a model: a description of data, screens, and rules that the platform can validate, version, and audit. The pace of building is the same. What remains afterwards is a readable description of the application, not code nobody knows.
Generating an application is easy these days. Maintaining it safely for years is hard. We designed the platform for the second part.
Data ownership
Where your data lives.
Every business application is screens and data. Clients ask about the screens during demos. They usually ask about the data only when parting ways with a vendor, when it turns out the data sits in a closed format on someone else's servers, with limits and a separate price list for access. That is how most business application platforms work, Salesforce and Power Apps included.
Your data lives in your own PostgreSQL database, on your servers or in a cloud chosen by your security team. PostgreSQL is the most popular open database in the world: no licences, no fees per gigabyte. We maintain that database and build applications on it. You remain the owner.
AI systems are exactly as useful as the data they can reach. An agent working directly on your database analyses and reports without limits or extra fees. PostgreSQL also happens to be the database language models know best, so they make the fewest mistakes on it.
Access to your own data should not have a price list.
Application model
The application as a model.
In classic IT, every change to a system is a small project: a developer, tests, a deployment. Not because people work slowly. Because the application is code, and in code it is easy to break something and hard to notice in time.
In DEX, the application is a model: a description of data, screens, and rules the platform understands in full. Three practical differences follow.
- Changes without risk. A new field, screen, or workflow is first checked by the platform, then saved as the next version. Reverting a change is one step.
- Updates without breaking customisations. Your customisations and the platform live in separate layers. The platform can be updated without touching what was built specifically for you.
- AI that does not guess. The agent does not dig through code. It reads the model and its rules, so every change it makes can be reviewed before it reaches users.
A change to a system should be a decision, not a project.
Migration
Oracle Forms migration.
Companies running on Oracle Forms have so far been offered two paths. First: rewriting the system from scratch, which means years of work, a substantial budget, and the risk that the new system behaves differently from the old one. Second: moving to another Oracle technology, which means the same licence costs in new packaging.
We migrate the system automatically, preserving the way it works: screens, logic, and keyboard shortcuts. Users need no training because after the migration they work exactly as before. The company also comes off Oracle database licences, often the largest line in the IT budget. That saving alone can cover the cost of the project.
After the migration, the system stands on a platform where further changes and applications take days. Modernisation then proceeds step by step, at a pace set by the company, not by the schedule of a giant project.
We do not sell a system-rewrite project. We move a system that works the same after migration and can grow faster.
System development
Why changes need no deployments.
In classic technologies, an application is first programmed, then compiled and deployed. Every change, however small, travels that whole road. Hence the schedules, maintenance windows, and a project manager for every fix.
On our platform, the application is not compiled. The platform reads the model live, so a change in the model is visible in the running system immediately. If something is off, reverting takes one step.
A great deal. An AI agent cannot safely change a compiled application, because there is nothing in it to read. It can, however, work on a description of the application that can be reviewed before going live. The largest business application platforms, Salesforce and Power Apps among them, are built on the same principle. We add an open database and data on the client's side.
A small change should take an hour, not a quarter.
Exit terms
How to leave us.
Every platform vendor hears this question: what happens when we want to leave? Answers tend to be evasive, because the honest one is usually uncomfortable. Parting ways with an application platform most often means a file export and a multi-year project of rebuilding the system elsewhere.
With us, that answer is part of the offer. The data sits in an open database, on your infrastructure, and can be taken out at any time. The application structure is a documented model. The business logic is standard TypeScript, a language every modern development team knows. The screen layer can be rebuilt in any popular technology in weeks, not years.
We prefer clients who stay by choice, not by necessity. A client who knows the exit terms makes the decision to enter calmer and faster.
We show the exit terms before the contract is signed, not after.
Let's talk about your system.
20 minutes. We will show a migration on a real system and estimate what your licences cost you today. No obligations.