Describe your business.
Get the software.
oikapi turns the way you actually work into running apps. Describe what your team needs to track, and the screens, the permissions, and the audit trail come with it. Governed from the first record.
One definition. Four things you didn't build.
On most platforms these are four separate projects, four sets of bugs, and four things that drift apart. Here they are all derived from the same definition, so they cannot.
Screens
Lists, forms, filters, and detail views your team can use the same day. Change a field and every screen that shows it changes with it.
Rules that run on save
Approvals, validations, and calculations happen as the record is written, not in a nightly job that finds the problem a day late.
Permissions
Who can see which records, and which fields on them. Enforced underneath every screen and every report, not inside the one that happens to be asking.
An audit trail
Who changed what, when, and from where, on every record, from day one. Records soft-delete, so "it's gone" is always recoverable and always accountable.
Start from an app. Or from nothing at all.
Install a ready-made app and change it until it fits. Everything inside it is yours to edit, because it is built from the same pieces you would use yourself. Nothing is locked behind a vendor's idea of how your business works.
Helpdesk & Ticketing
Queues, SLAs, escalation, and a customer portal where external submitters are always free.
On-Call Management
Rotations, overrides, and escalation policies that know who is actually reachable right now.
CRM & Sales
Accounts, contacts, and pipeline on the same records your delivery and billing teams use.
Inventory & Purchasing
Stock, suppliers, and purchase orders with approval thresholds you set as a rule, not a ticket.
Projects & Expenses
Tasks, time, and spend against the same project record, so margin isn't a month-end guess.
Human Resources
People, roles, and onboarding, with field-level permissions that survive a reorg.
The rules live in the database, not the prompt.
Automation is only as trustworthy as what stops it. On oikapi, permissions, approval rules, and the audit trail are enforced underneath everyone who writes: a person, an integration, or an AI assistant. There is no way around them, because there is no way to reach the data that skips them.
- Access limits hold on every route to the data: screen, report, or export alike
- An approval that fails stops the save outright, so a record is never half-written
- An AI agent inherits a person's role and gets no more reach than they have
- Every one of those limits is a property of the data, not a promise made by an app
The same repair list, opened by three people Dana · technician, Leeds site 34 repairs cost hidden Priya · finance 1,209 repairs cost shown Scheduler · automation order refused over $10k, needs sign-off Nobody configured three views. It is one list, enforcing itself.
Configure it, or drive it from code
Everything the admin UI can do, the CLI and API can do too, so apps are reviewable, diffable, and promotable between environments instead of clicked into existence twice.
# Build it in the UI, or drive it from the CLI oi app create facilities # Package the whole app up oi app export facilities > facilities.oikapp # Review it, then promote it oi app install facilities.oikapp --env staging
$19 per user. Every app included.
One per-user fee, billed annually. No platform fee, no module gating, no per-app tiers, no charge for usage. Customers, vendors, and public submitters never count as users.
Tell us what you'd build.
Describe the thing you would otherwise keep in a spreadsheet. We will show you it running on oikapi, screens, permissions and all.