Deliver AI agents without hard-coding the client’s org chart
Add a reusable participant-resolution layer to the AI agents and workflow automations you build for clients. Roster resolves the current person, group, role, owner, approver, or delegate using the client’s organizational context.
Keep client-specific responsibility out of prompts, agent code, and workflow definitions — and reduce the routing logic your team has to build and maintain. Works with the agent frameworks, automation platforms, models, and directories already in your delivery stack.
Every client deployment eventually hits the same “who” problem
Agent frameworks and automation platforms help your team decide which tool to call, what action to perform, when to request human review, and how the workflow should continue.
But once a solution enters a real client environment, it must answer a different set of questions — questions your framework and platform were never designed to answer.
Most implementation teams solve them separately for every client: fixed email addresses, prompt instructions, manager lookups, group aliases, workflow variables, or custom routing tables. It gets a prototype working, but the maintenance cost lands on your team.
Roster gives your agents and automations a dedicated participant-resolution layer — outside prompts, agent code, and workflow definitions.
One resolution layer between the workflow and the client organization
Roster sits between the client’s directory of record and the agents, workflows, and applications you build — resolving the current participant when a solution needs one.
Hard-coded routing vs. a resolution layer
The difference isn’t abstract — it shows up on the next reorganization, the next role change, and the next handoff.
Turn organizational routing into a reusable delivery capability
Controls reasoning, tools, state, and execution. Chooses the next action and when to pause for human review.
Controls workflow logic, sequencing, retries, and actions on downstream systems.
Resolves the current person, group, role, owner, approver, or delegate from the client’s organizational context — on demand.
Use Roster across the solutions you already deliver
Resolve the appropriate business, finance, security, legal, or operational approver before the workflow creates an approval task.
Find the current owner of an application, service, process, project, or operational responsibility.
Route policy exceptions and low-confidence agent outcomes to the group or role responsible for reviewing them.
Determine who should receive an escalation based on the relevant project, responsibility, and organizational context.
Select the participant for a review or decision while the agent framework or workflow engine controls when execution pauses and resumes.
Resolve the active delegate when the usual owner or approver is unavailable.
Fits the tools, platforms, and models in your delivery stack
Roster complements the systems your consultants, forward-deployed engineers, automation specialists, and AI engineers already use — it doesn’t replace them.
Designed for repeatable client delivery
- 01Start without adding infrastructure
Run Roster in a single Docker container with its included database for straightforward deployments and evaluations.
- 02Integrate through the surface that fits the project
Use MCP for tool-enabled agents, REST for explicit application integrations, CLI for engineering workflows, or the web interface for administration.
- 03Keep client environments separated
Deploy Roster within the environment and operational boundary appropriate for each client rather than centralizing multiple clients’ organizational data in your delivery tooling.
- 04Hand control to the client
Project owners can maintain their projects and participants as responsibilities change, reducing dependency on your implementation team after go-live.
- 05Expand when the deployment requires it
Begin with the self-serve edition appropriate for the engagement, then evaluate Enterprise deployment options when a client requires PostgreSQL, high availability, or additional enterprise capabilities.
Protect project margins after go-live
Small routing changes can consume disproportionate delivery time: replacing an approver, tracing a stale group alias, updating a workflow variable, retesting an agent, and redeploying the solution.
Roster moves those changes into a client-managed organizational layer — making participant resolution easy to include in fixed-price implementations, repeatable solution packages, and managed AI services without turning every organizational change into a support request.