Identity and access
Organization membership, teams and permission checks establish who can do what. Applications use shared authentication and operation-level guards, with optional two-factor authentication. Access is configured for each business.
Platform Shared systems
The foundation behind the work.
Blurr’s applications share the systems every business needs. We build your workflows on that foundation, with your own rules and interfaces.
Talk about your businessA connected workflow
- Shared business service
- Your rules and permissions
- Your team’s interface
- Connected operations
Built around your team.
People. Knowledge. Work.Explore the approach
The approach
Our monorepo brings common business services into one maintained codebase. Core’s workforce tools, the 90 Fabrication application and Blurr’s administration tools draw on these foundations. Each product adopts the services it needs.
Operations and approvals
Business actions share input validation, authorization and configured approval gates. Approval policies can route decisions through several people, support delegation and retain the data submitted for review. Screens and agent tools use the same operation contracts.
Background work
A persistent queue carries follow-up work beyond the initial request. Registered workflows support retries, deferral, recovery and visible failure states. Scheduling services add timers and SLA actions for the workflows that use them.
Documents and activity
Shared document services connect files and versions to business records, with expiry reminders and missing-document reports. Activity views help users review changes and decisions within their access. Product teams choose which records and operations adopt these services.
Search and notifications
A common search surface brings indexed records into view. In-app and email notifications connect events to the right people, with preferences, quiet hours and digests. These services use each application's configured events and recipients.
Integration delivery
Connection records, signed webhooks, retries and health checks provide infrastructure for integrations. The provider adapter and field mapping are built for the system being connected; this is not a claim of ready-made connectors for every business tool.
Tools for AI
The MCP layer exposes selected business operations to agents under an identified user. Permission and approval checks remain in the execution path. The local assistant prototype uses real operation results and persistent conversation history; production deployment is scoped separately.
In practice
Built into our work.
The same foundation can support Core’s people operations and a dedicated interface for 90 Fabrication. A document, an approval and a notification follow common rules, while each application keeps the workflow its team needs.
Shared services are adopted and configured per application.