Choosing the vendor of a system your company will run on for years calls for hard
questions. We have collected the ones we hear most often, along with the answers. Not to
pre-empt the conversation, but because our entire offer rests on these answers.
Four questions that come up in every conversation.
Every board and every IT team asks them. Rightly so. Here are the answers we give in
meetings.
Question
Proprietary technology? What if you disappear from the market?
The 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.
Question
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. With us that line disappears, and the licence savings often cover the cost of the migration.
Question
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, and users pay for it in productivity. We migrate the system's behaviour automatically. Modernisation happens afterwards, step by step, at the company's pace.
Question
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.
Alternatives
How we compare with the alternatives.
Each of these paths has its uses. Below is what, in our view, most sets them apart from
our offer.
Oracle APEX
Solves the technology problem, leaves the licence problem. You keep paying the Oracle database bill. With us, that line disappears.
Salesforce / Power Apps
Building from scratch on someone else's infrastructure, with the data at the vendor and a per-user subscription. We move the system you already have, and the data stays with you.
Code generators
Excellent for a prototype. Maintenance is another story: what remains is code nobody has read. With us, what remains is a documented model that can be audited and evolved.
Software house
A rewrite means years of work, and at the end the system behaves differently from the old one. With us it behaves the same, from day one.
Exit terms
Four things that always stay on your side.
With us, the ability to leave is not a declaration but a consequence of the
architecture. Here is what, concretely, you take with you if it ever comes to that.
Data in an open database. PostgreSQL on your infrastructure.
The data can be taken out at any time, in a standard, readable format.
Platform code in escrow. An escrow agreement guarantees you access
to the platform code if our company ever ceased to exist.
A replaceable screen layer. The screens can be rebuilt in any
popular technology in weeks, not years.
Logic in standard TypeScript. The business rules are written in a
language every modern development team knows.