HR operations control layer
The control layer for modern HR operations.
Muurel is an HR system you can actually change. Model your workforce without a migration, design the screens your team needs, and let AI agents draft the work — with every change validated, versioned, and reversible before it goes live.
The cost of change
Add one field to your employee record.
Not a migration. Not a new module. One field, because a regulator, a works council, or a reorganisation now requires it. Here is what that costs in the system you have today — and what it costs here.
Today Weeks, and a permanent dependency.
- Weeks of research Vendor archaeology and internal guesswork about what the system will even allow.
- Months of back-and-forth It becomes a scoped consultant project that costs more than the change was worth.
- A workaround that never leaves So it happens in a spreadsheet — now a permanent dependency somebody maintains.
In Muurel An afternoon, and it's reversible.
No schema migration
Validators and rules included
Versioned and reversible
You don't have to rip anything out to start.
Replacing a system of record is a multi-year program with a body count. Muurel is built to run beside what you already have — API-first, with an integration hub for connections, webhooks, and a full event log — so the operations layer can move before the record layer does.
Start with the part that hurts: the data model you can't change, the screens you can't edit, the approvals that live in email. Grow from there.
Page builder
Design the screens your team actually needs.
Employee detail, list views, add forms — even the login page — are layouts you compose in a visual designer and publish with version history. The same builder produces the change-request forms behind termination, leave, transfer, and compensation changes, so process lives in configuration instead of a PDF.
Draft, publish, roll back
Any entity
Reusable fragments
Governed configuration
Every change previewed, versioned, and reversible.
Configuration is never edited in place. It is validated, previewed, and written as a numbered version carrying its actor, timestamp, and diff — then rolled back in one click when it turns out to be wrong. Adaptability without an audit trail is just a faster way to break production.
Validation before apply
Full audit trail
One-click rollback
Structure and time
An org chart that knows what day it is.
Workforce structure is navigation and trust infrastructure, not a diagram for the all-hands deck. And because employee data is effective-dated, you can schedule a reporting-line change for next quarter, correct one from last year, and ask the chart what the organization looked like on any date.
As of any date
Scheduled changes
Retroactive corrections
AI agents
An assistant that proposes. A product that decides.
Ask in plain language — in whatever language your admins actually speak — and the assistant can look up people, draft field and picklist changes, author pages, and prepare employee updates. What it cannot do is write to your system. Every mutation comes back as a preview a human approves, and anything the requester lacks rights for fails closed rather than guessing.
Rights-aware
Preview before apply
Fails closed
Fully traced
From system of record to system of operations.
The last generation of HR software won by being the place the data sits. That job is largely done, and it is not where the cost is anymore. The cost is in everything that happens around the record: the change nobody can make, the process nobody can see, the exception nobody planned for. That is the layer Muurel is building.
Built for the teams stuck paying too much for change.
Muurel is not claiming every configuration change goes through an AI-style preview-and-apply loop. The AI boundary is one thing. Governed configuration is another. Both are real, and keeping them distinct is the point.
Model your workforce your way
Dynamic employee records let the system match enterprise reality instead of forcing the company into hardcoded fields that age badly the second the org changes.
Govern configuration like product, not spreadsheet ops
Validation, version history, rights, and auditability make configuration changes controlled and reviewable without pretending every admin action is an AI workflow.
Keep AI agents inside the trust boundary
Muurel treats AI agent work as controlled leverage. Rights-aware, page-aware, observable, and previewed before apply when the agent is proposing a change.
A credible wedge now, a bigger platform over time.
Start with the painful, believable wedge. Then watch that wedge grow into the operating layer for governed HR work.
Flexible records that fit the company, not the other way around.
Trusted structure for navigation, reporting, and operational context.
Validation, rights, versioning, and auditability around the changes that matter.
Agent-proposed change runs through preview before apply, with clear human review before the system moves.
We're early. That's the offer.
Muurel is in active development, and we are looking for a small number of design partners who run HR systems somewhere the cost of change genuinely hurts. You get direct influence over what gets built next. We get the thing every early product needs most: real operational reality to build against.
No pretend customer logos on this page, and no roadmap theatre. Here is honestly what is running today.
Live Employee master data with dynamic fields, validators, and behaviors
Live Directory, org chart, and effective-dated employee change requests
Live Page builder with draft, publish, version history, and rollback
Live Governed configuration: validation, versioning, audit, rollback
Live Picklist management and import, configurable search, integration hub
Live Rights-aware AI assistant with preview-before-apply on every mutation
Live Row-level employee visibility rights
What we're building next
The next three things, and why they're next.
Design partners have direct influence over the order. If one of these is the reason you'd switch, say so and it moves up.
People reporting and executive snapshots
Trusted headcount, movement, upcoming starters and leavers, and data completeness — as custom reports, exports, and a leadership-ready summary. The numbers your CHRO asks for, without an analyst rebuilding them by hand every month.
Workflow automation and approvals
Approval routing on top of the change-request forms that already exist: who reviews what, review history, a safe preview of the outcome, and an auditable record of the approved change actually being applied.
Permission-aware document knowledge
Answers grounded in your own policies and documents, with tenant isolation, access control, and citations — and a fail-closed default, so the assistant declines rather than leaking a document someone shouldn't see.
Tell us where change costs you the most.
A working session, not a pitch. Bring your ugliest HR configuration problem and we'll show you what it looks like in Muurel.
Prefer email? Write to info@muurel.com.