FAQ
Frequently asked questions.
We have collected the questions we hear in meetings with boards and IT teams, the hard ones and the practical ones. We answer here the same way we do in the room. If your question is missing, we will gladly answer it on a call.
Proprietary technology? What if you disappear from the market?
Your data sits in an open database on your side, not ours. The platform code goes into escrow, the business logic is standard TypeScript, and the screen layer can be rebuilt in a popular technology in weeks. Even in the worst-case scenario you are left with a working system and full access to everything it is made of. We discuss the exit terms before the contract is signed, not after.
Oracle recommends APEX. Why not go there?
APEX solves the old-technology problem, but not the cost problem: it is still Oracle technology, on an Oracle database, with Oracle licences. The largest line on the IT bill stays exactly where it was. With us that line disappears, and the licence savings often cover the cost of the entire migration.
Why not rewrite the system by hand?
Because that means years of work, a budget in the millions, and a risk nobody prices into the offer: a rewritten system behaves differently from the old one, and users pay for it in lost productivity. We migrate the system's behaviour automatically. Modernisation happens afterwards, step by step, at the company's pace.
Where will we find people to maintain it?
The logic is standard TypeScript, the most popular programming language on the web. The application structure is a documented model, not a niche technology. A large share of changes is done by the built-in AI agent, and the rest can be handled by any ordinary development team. Those are not hard to find.
Where will our data be?
In an open PostgreSQL database on your infrastructure: in your own server room or in a cloud chosen by your security team. No licences and no capacity fees. We maintain the database and build applications on it, but you remain the owner and can take your data out at any time.
Do users need training after the migration?
No. Screens, logic, and keyboard shortcuts work the same after the migration as before, so employees sit down to a familiar tool. What changes is the technology underneath, not the way people work. It is one of the first things we show in a demo.
How long does a migration take?
It depends on the scale: the number of forms, triggers, and integrations. That is why we start with a free analysis of your system, after which we give a concrete scope, schedule, and budget. Throughout the project the old system runs in parallel with the new one, until a safe switchover.
Are our data and work safe?
Permissions work at the level of a single row of data, and every change to the application and the data leaves a full audit trail. Because the application is a described model, the platform checks every change before it goes live, saves it as the next version, and can revert it in one step.
How is this different from code generators like Lovable, Bolt, or Replit?
Generators are excellent for prototypes, but they leave behind code nobody has read. Here, AI builds the application as a model the platform can validate, audit, and evolve for years. The speed of building is similar. The difference shows up later: at audit, integration, and maintenance time.
Let's talk about your system.
20 minutes. We will show a migration on a real system and answer the rest of your questions. No obligations.