One record per person
From the first interview to the relieving certificate, with the attendance, pay, leave and equipment that went with it.
Your data, your database, your audit trail
People operations on a record nobody can quietly change
Payroll, attendance, leave, hiring, projects, chat, a shared drive and video meetings in one workspace. Every approval is shared between people, every entry is sealed to the one before it, and every customer gets their own database — not a row in somebody else's.
Half an hour, on your own headcount and pay cycle. No sales sequence afterwards unless you ask.
One each
PostgreSQL database per customer
Hash-chained
audit trail, verified hourly
Nightly
backups, read back and checksummed
15 modules
included in every tier
Six subscriptions, four spreadsheets, and nobody sure which number is right
Attendance in one tool, payroll in another, approvals over email, files on somebody's laptop. The work is not the problem; the seams are. Apex removes the seams by holding the whole employment record in one place, with one set of permissions over it.
Approvals that need more than one person
Payroll takes three roles. A salary bank-account change takes three different people. Nobody signs their own.
An audit trail you can prove
Every entry hash-chained to the one before it, so a quietly edited history fails verification instead of passing unnoticed.
Permissions, not job titles
What someone can see is a permission map you edit in the console — and the menu is built from it, so there are no hidden doors.
Your own database
Not a tenant column. Your workspace is a separate PostgreSQL database, backed up and restorable on its own.
No third-party dependencies
Chat, calls, recording and storage all run inside the service. Nothing leaves it to a provider you did not choose.
Nobody signs their own
A payroll run takes three people and leaves a trail
HR audits the figures. An executive approves them. Accounts disburses. Each stage is a different person, each stage is recorded, and the record of it is sealed to the record before it. Change one line later and verification names the row.
- Three roles on every payroll batch
- Three different people on a salary bank-account change
- A second PIN before money or personal data opens at all
Every tier includes every module
Tiers differ by how many people you have, not by which features you are allowed. There is no matrix to study and no customer who paid and still found a door locked.
Core workspace
Directory, org chart, attendance, leave, tasks, calendar, mailbox, notifications, approvals, certificates, service requests and the administration console.
Messaging
Channels and direct messages with typing indicators, read receipts, mentions and attachments.
Shared drive
Folders, versioned files, resumable large uploads, internal and public sharing, trash and an access log.
Meetings & calls
In-portal video calls with screen sharing, a lobby, host controls and recording.
Payroll & finance
Multi-currency payroll, payslips, expenses and claims, salary bank accounts, the general ledger and the currency configurator.
Recruitment & onboarding
Candidate pipeline, interview scheduling and onboarding requisitions with IT provisioning.
Resignations & offboarding
The resignation funnel, clearance gates and final settlement.
Promotions & bonuses
Promotions, increments and bonuses routed through the approval engine.
Policy & discipline
Policy violations, warnings, freezes and performance improvement records.
Projects & delivery
Projects, task boards, revisions and deadline escalation.
Sales pipeline
A lead pipeline for client-facing teams.
Credentials vault
Shared credentials with allocation, PIN-protected reveal and a full reveal audit.
IT helpdesk & assets
Tickets, asset register, assignment disputes and service-account requests.
Biometric terminals
Device registration, token authentication and a live punch stream.
Developer tools
The developer settings console, diagnostics and maintenance commands.
Security
Built for the day somebody asks you to prove it
Payroll and personal data attract both auditors and attackers. Apex assumes both will arrive.
Read the privacy notice-
Separate database per customer
Your records are not in a shared table behind a filter. A query that forgot its scope cannot reach another organisation, because the data is not there to reach.
-
A second PIN for money and personal data
Payroll, bank details and the credentials vault need a Financial Security PIN as well as a password, so a borrowed browser session is not enough.
-
Tamper-evident history
Audit entries are hash-chained and sealed. Verification is a command anybody with the right to run it can run, and it either passes or names the row that changed.
-
Support access that cannot be quiet
When our support staff enter your workspace it is by single-use link, with a reason recorded, and your users see a banner for the whole session.
-
Backups proved, not assumed
Every workspace is dumped nightly, read back, and checksummed. Restores take a safety copy of the current data first.
Priced by headcount, discounted for committing
One monthly figure for the whole workspace. Paying for longer costs less, because it is worth more to us.
Before you book
How long does it take to start?
A workspace is created the same day. Bringing your people across is a spreadsheet import; a company of a hundred is usually running within a week, including the permission map and the approval chains.
Can we get our data out again?
Yes, at any time and without asking us. Exports are built into the data transfer screen, and if you close the account you are sent a download of your whole workspace before anything is destroyed.
What happens to our data if we leave?
It is kept for the retention period you agreed, you are emailed a final download link before that ends, and then the database copy and the files are destroyed together.
Do you read our data?
No. Support staff enter a workspace only by single-use link with a reason recorded, and your users see a banner for the whole session. It is in the audit trail like everything else.
Is there a per-module price?
No. Every tier includes every module, and the tier only reflects how many people you have.
Who hosts it?
The service runs in France (EU). Chat, calls, recording and file storage all run inside it, so nothing is handed to a third party you did not choose.
Hiring in Pakistan? We keep a sourced reference for salary tax, EOBI and provincial social security, with the Act or circular each figure was read from — and an honest blank where the sources disagree. Free to use, no sign-up.
From the blog
All articlesSecurity / 25 Oct 2026 / 4 min
Support access that cannot be quiet
Every SaaS vendor can see your data. Most of them do not tell you when they do. Here is how ours works, and why we made it impossible to do silently.
Read it
Product / 22 Oct 2026 / 4 min
Nobody should be able to run payroll alone
Separation of duties is not bureaucracy. It is the control that makes payroll fraud hard, and most HR software quietly skips it.
Read it
Engineering / 16 Oct 2026 / 5 min
How we back up — and how we prove the backup works
A backup nobody has read back is not a backup, it is a hope. Here is the order we do things in, and why that order is the whole point.
Read it
See it with your own numbers
Half an hour on your own headcount and pay cycle. You will see the payroll chain, the audit trail and the permission map on your own figures — not a canned tour.