When business teams start building their own apps, IT has one question first: what could such an app break? In Openbase.one, the answer is short. An app can only do what its environment allows. And the environment allows very little.
Sealed off, no network
Every app's code runs in its own isolated runtime (workerd isolates). That runtime has no network access:
- The app can't reach the internet. It can't send data to outside servers.
- The app can't reach other workspaces.
- The only thing it can reach is Openbase.one's own interface.
That holds for every app alike, the ones you build and the ones from the App Store.
No SQL, every access checked
Apps don't write SQL and never touch the database directly. Every data access goes through the Openbase.one SDK and a gateway that checks each individual call:
- Does this call belong to this workspace?
- Does it belong to this app?
- Is the person the app is working for allowed to see or change this data?
So when you describe that only HR sees salaries, that's not a line of code someone might drop in the next rewrite. The rule is enforced on every access.
Separated at the database level
Workspaces are separated from each other at the database level, with row-level security. That separation doesn't depend on an app behaving correctly. It sits underneath.
The same permissions for the assistant
Each person's personal assistant works with exactly that person's permissions. It only sees what they're allowed to see, including in the apps you build, and it brings every change for approval.
What else IT gets
- Sign-in with Google Workspace, Microsoft Entra ID, a passwordless email code or a password. Admins can switch passwords off. SAML is available on Enterprise.
- An audit log records who changed what, and it can be exported.
- The code of every app you build lives as a git repository in the workspace, and data can be exported.
- Openbase.one's data is hosted in Frankfurt. AI calls go through commercial providers; in EU mode through AWS Bedrock in eu-central-1. A DPA is available on request.
What isolation doesn't replace
Isolation and permissions limit what an app can do technically. Whether it does the right thing in substance is decided by the team that builds it. That's what the check before going live, the way back to the previous version and, if you want one, a support contract are for.
Plans
Isolation and permission checks apply on every plan, to every app. Plans and support contracts are on the pricing page.
Describe your first app and watch it go live, checked.
Start for free