Independent SaaS · In development
Every organization works differently. Its software should adapt.
Dutyrex is an independent workforce operations platform where tasks, approvals, multi-location operations, and employee engagement are all configurable. Built on a multi-tenant foundation, it lets organizations define their own processes instead of adapting their operations to rigid software.
- Product
- Dutyrex
- Sector
- Workforce operations and workflow automation
- Year
- 2026
- Category
- Multi-tenant workforce operations SaaS
Every organization builds its own structure
The problem
Different organisations assign, approve, and track work differently. An off-the-shelf task tool that fits one organisation typically doesn't fit the next, because department structure, approval chains, and location requirements vary from one to another. The architectural requirement here is that different organisations can operate fully independently on the same infrastructure — genuine multi-tenancy.
Context
Dutyrex is Relay Atelier's own independent product. Its first practical validation opportunity comes from operational requirements identified in healthcare organisations, but its long-term product vision is cross-industry and international. Dutyrex is not exclusively a hospital employee application — initial market validation is proceeding in Turkey, with Turkish and English localisation.
The system
A multi-tenant architecture built on tenant-level data isolation, tenant-specific users and permissions, and organisation-specific configuration; a no-code workflow builder letting each organisation define its own tasks, departments, roles, approval sequences, recurring checklists, and templates; tenant-scoped role-based access control; multi-location operational support; task tracking, approvals, and auditability; and an engagement layer built on task-based progress, points, and achievements.
How organizations stay separate on shared infrastructure
Organization A
- Opening checklist
- Inventory count
3 roles · 1 location
Organization B
- Shift handover
- Supplier approval
- Compliance review
6 roles · 3 locations
Organization C
- Deployment check
- Audit log review
2 roles · 1 location
An illustrative example — not a real customer organization.
Engagement layer
A secondary layer on top of operational execution — progress, points, and achievements.
What we delivered
Multi-tenant architecture
- Tenant-level data isolation
- Tenant-specific users, permissions, and configuration
No-code workflow builder
- Custom task, department, and role definitions
- Approval sequences, recurring checklists, and reusable templates
Roles and multi-location operations
- Tenant-scoped role-based access control
- Location-specific task, schedule, and approval structures
Task management and engagement
- Task assignment, completion tracking, and manager approvals
- Task-based progress, points, and achievement mechanics
Implementation
Cross-tenant data isolation was a foundational architectural decision from the outset, not a feature bolted on later.
The hospital's workflow was never hardcoded as Dutyrex's universal template — healthcare templates are only an editable starting point.
The engagement and rewards layer was designed as a secondary layer on top of operational execution, not the whole product.
Development status
Built
- Multi-tenant architecture and per-tenant data isolation, as the foundational layer.
In development
- First operational validation is proceeding via a pilot direction developed from healthcare-sector requirements.
Not yet
- Billing and payment infrastructure
- General market launch
Only verified scope appears on this page. No claims about paying customer count, revenue, or general availability are made.
Getting started
Where are you losing enquiries?
Tell us about the enquiry that goes unanswered, the follow-up done by hand, or the work that scatters between systems. In the first call we'll establish what can be systematised and where to start.
After you send the form
- A reply within two working daysWe read your message and suggest a time that suits you.
- A 30–45 minute discovery callA working session that maps the process, not a sales pitch. If it isn't a fit, we'll say so plainly.
- A written summaryAfterwards we put in writing what could be built, in what order, and within what scope.