"The app works." You hear that a lot, shortly after someone has built something with an AI tool. And it's true. You click, something happens, the data shows up. But "works" on your own screen means something different from "works in day-to-day operations".
An app is ready for real work when a team can rely on it even while the person who built it is on holiday. When something changes. When someone leaves the company. When someone asks who changed what, and when.
We've written down how we judge that. The list applies no matter what an app was built with.
1. It knows the people in the company
An app that is ready for real work has no user management of its own with its own passwords. People sign in with the accounts they already have. Whoever leaves the company and is removed from the workspace also loses access to the app, without anyone having to remember.
In Openbase.one, people sign in with Google Workspace, Microsoft Entra ID, an email code or a password. Admins can switch passwords off for the whole workspace.
2. Permissions apply to every access
A hidden button isn't a permission model. If a manager shouldn't see salaries, the salaries must never reach them, whichever way they ask.
That is why apps in Openbase.one write no SQL. Every data access goes through the SDK and a gateway that checks each call against the workspace, the app and the person's permissions. Workspaces are separated from each other at database level.
3. Every version is checked, not just the first
The first version of an app usually gets a careful look. The fifth change doesn't. That's exactly where the unpleasant mistakes happen: a small tweak to a list quietly reveals a column that should have stayed hidden.
In Openbase.one, every version has its data model and access rules checked and its records classified: internal, personal, sensitive, tax. Then every page is opened in a real browser as every test persona. "As a manager: no salary visible." "As HR: all salaries visible." A version goes live only when the check passes. If the build or the check fails, the current version stays live.
4. It runs sealed off
An app that works with company data shouldn't be able to talk to the internet at will. Not because all code is malicious, but because nobody reads every line of generated code.
App code in Openbase.one runs in an isolated runtime with no network access. It reaches neither the internet nor other workspaces. What an app may do with data isn't decided by its code, but by the check on every single call.
5. There is a way back
Mistakes happen. What matters is how fast you can undo them. An app that is ready for real work has versions, and the previous one can be live again quickly, without anyone reconstructing things late in the evening.
In Openbase.one, every version is kept. The previous live version is restored in one click. Then you can calmly describe what should change.
6. Updates follow your rules
Apps a team installs rather than builds raise their own question: who decides when something changes? In some areas, automatic updates are exactly right. In others, such as payroll, you want to see what's new first.
In Openbase.one, installed apps update automatically or only after approval, set per app. If you customise an installed app, you get your own copy and don't change anyone else's version.
7. Code and data belong to the company
An app that only exists on one account effectively belongs to that account. Ready for real work also means the company can take the app with it.
The code of every app you build lives as a git repository in the workspace, and the data can be exported. An audit log records who changed what, and it can be exported too.
8. Someone owns it
The last point isn't technical. Every app needs a team that stands behind it: one that decides what the app should do and signs off on changes. A check can prove that permissions are respected. Whether a leave policy or an approval limit is right is a question no check can answer.
We think that split is the honest one. Openbase.one is responsible for the environment: isolation, permissions, checks and versions. The team is responsible for the content. Admins see every app in the workspace.
What it doesn't mean
Ready for real work doesn't mean nothing ever goes wrong. No environment turns an unclear requirement into a correct app. It means mistakes show up early, do little damage and are gone quickly.
And it means nobody is left on their own. Platform support is included in every plan. With a support contract we help with your own apps, and with Premium we also review new apps before they go live. If you'd rather build an app together with us, you can book that as a one-off package.
Try it
You can build your first app for free, with €15 of AI credit and no credit card. Plans and support contracts are on the pricing page.
Describe your first app and watch it go live, checked.
Start for free