Nexor
Operations platform with workflows each organization defines for itself
One chain of work from first enquiry to delivery and service, across every location an organization runs — on workflow pipelines each organization configures for itself, not ones we hard-code.
- Built for
- Organizations whose work moves through stages and across locations — branches, sites, studios or plants — and that want their own process in the software, not a vendor's.
- Where it runs
- Web portal for every role, from the front line to the director
- Role dashboards for location, regional and leadership views
- Signs in through
- Identity
Capabilities
What Nexor does
-
Your workflow, as configuration
Pipelines, stages and transition rules are configuration, not code. Each organization defines its own, each location can work its own pipeline, and every record gets an immutable ID in the format your finance team already uses.
-
Service levels that are actually enforced
SLA rules watch every item of work against your business calendar, holidays included, and escalate before a customer notices.
-
Every location, one tenant
Branches, sites and plants are locations inside your organization. Work can move between them, with the move recorded, but never out of your data.
-
An activity log nobody can edit
Every change to a record or to configuration produces an append-only entry. Audit and activity reports read from it directly.
-
A platform, not a single app
Nexor is built as a module platform. Identity, tenancy, configuration, the activity log, SLAs and dashboards are shared, so the next module starts on a finished core.
Many locations, one chain of work
Work rarely stays in one place. An enquiry arrives at one location, is shaped in another, fulfilled in a third and serviced wherever the customer is. Nexor treats each of those as a location within one organization, so a piece of work that starts in one city and finishes in another stays one record with one history.
Nothing custom per customer
Onboarding an organization needs no code, no schema change and no deployment. Workflow pipelines, stages, role names, tags, SLA targets, record number formats and working calendars are all tenant configuration, editable by the organization’s own administrator.
Identity is not our job, and that is the point
Nexor keeps no user, role or permission records of its own. Members sign in through Garuda Identity, and every request is scoped to the locations that member is permitted to see. Nexor cannot leak what it never stores.
Where Nexor sits
Every Garuda product shares one identity and one engineering foundation. The lit edges are Nexor's.