WorkTrack
Build what you need. Pay for what you use.
Start free with the core. Install only what your team actually uses.
Oona ID emails you a six-digit code, and you choose your password there. No credit card.
- Free core, forever
- No credit card
- Cloud or on-premise
The application layer
Add what the business needs. Nothing else.
The core is free and stays the same for everyone. Every capability beyond it arrives as a signed application you switch on when you need it.
WorkTrackv2.4.1 · signed by OonaVerified
Permissions requested
people.readRead the employee directorytimesheet.writeWrite hours and shift recordsnotify.sendSend shift reminders
28 seats£4 / seat / month · proratedSee this application
Live in about 40 seconds. No redeploy, no downtime for the people using it.
What's new in Oona
Released this quarter, already on every site.
Payroll
Approve a run from your phone
Studio
Rota drafts you can edit
Platform
On-premise upgrades in one command
Oona ID
Sign-in links replace passwords
The free core
Start on a core that already runs the basics.
People, organisations, roles, seats and sign-in are part of the platform, not an application you buy. Every site gets the same core on day one.
- One directory every application reads from
- Roles and permissions defined once
- Seats you can move between people
£0
what the core costs, for every seat, forever
People · 28
Invite| Name | Role | Applications | Seat |
|---|---|---|---|
| Nadia FischerOperations lead · 4 | Active | ||
| Tomas BernShift manager · 3 | Active | ||
| Aiko MoriPayroll · 2 | Active | ||
| Ruben DiazDriver · 1 | Invited | ||
| Sara WhitfieldDriver · 1 | Invited | ||
| Lena VogtWarehouse · 2 | Active |
Install
Switch a capability on while people keep working.
An application is a signed artefact the core verifies, mounts and bills for. It appears in the sidebar of everyone entitled to it — no release window, no downtime.
- Signature and permissions checked before load
- Seats prorated to your billing day
- Remove it and the data stays yours
40 sec
from install to people using it, on a running site
Installing WorkTrack
00:00- Signature verifiedECDSA P-256 · trust store: releases
- Permission manifest accepted3 scopes granted by the owner
- Migrations appliedtenant northwind · 6 tables
- Remote registered[email protected] loaded in the hub
- Seats assigned28 of 40 seats, prorated
Verifying the artefact before anything loads…
Deployment
In our cloud, or on your own servers. Genuinely the same platform.
This is not a full product and a cut-down community edition. Same core, same applications, same updates — the only thing that changes is who runs the machines.
Moving between the two is a migration, not a rewrite: identical platform, identical applications, identical data model. On-premise has no marketplace, and no on-premise site holds a licence signing key.
Same core. Very different application sets.
Four teams paying only for what they switched on.
- Northwind LogisticsTransport · 240 people
Rotas and payroll on one set of hours.
- WorkTrack
- Payroll
- Notifications
- Vinsure RetailRetail · 90 people
Shift swaps without a phone call.
- WorkTrack
- DMS
- Corabel CareCare · 410 people
Rota drafts a manager can actually edit.
- WorkTrack
- Studio
- Payroll
- Ardent BuildConstruction · 60 people
Certificates where the core can find them.
- Payroll
- DMS
One platform, priced by what you switch on.
- 11
- applications in the catalogue today, each one optional
- 2
- ways to run it — Oona Cloud or your own servers
- 0
- redeploys needed to add or remove a capability
Pricing
The platform is free. Applications are what you buy.
Run the core for nothing, in our cloud or your own network, for as long as you like. What costs money is applications — priced per seat, listed in the marketplace.
Security & licensing
Identity, access and licensing belong to the platform — not to each application.
An application should not be able to invent its own idea of who you are or what you are allowed to do. In Oona it cannot: the core owns those answers and every application asks it.
Single sign-on across the hub and every application through OpenID Connect, with a per-tenant client and the authorization code flow with PKCE. One session to grant, one session to revoke.
Applications declare the scopes they need up front. The interface gates on them and the backend enforces them independently, so a hidden button is not the security control.
Every site is its own tenant. An application reads the tenant from the platform and has no way to address another one.
A release is provisioned only if its manifest carries a valid signature from a key the site trusts. An unknown key id, a bad signature and an empty trust store are three different failures, reported as three different reasons.
Licences are signed artefacts validated by the platform, and an on-premise site validates its own offline — so it is exactly as accountable as a hosted one, without calling home.
Each application pins the core version it supports. An update that would break an application you depend on is refused before it lands, not discovered afterwards.
For developers
Build against the platform instead of around it.
The hub handles loading, routing, navigation and permissions. Your application ships a backend, a manifest and one exposed frontend entry point — and it ships on your schedule, not the platform's.
The CLI, today
- oona validate
- Checks module.json against the same schema and core-scope rules the release registry runs server-side.
- oona login
- Stores the package-feed credential an application needs to restore the SDK and contracts packages.
- oona env
- Reports the environment the CLI is pointed at.
- oona logout
- Discards the stored credential.
Scaffolding, local run and packaging are specified and not yet built, so they are not listed. The CLI's own --help does the same thing, for the reason that a developer sent looking for a command that is not there concludes the tool is broken before they conclude it is unfinished.
Start with the core. Add what you need.
Create a site in the Oona cloud, or talk to us about running it inside your own network.