Trust
- Security & access control
- Identity & authentication
- Privacy & data protection
- Compliance & risk management
The platform
Six layers, one runtime, every action traced.
Zensible orchestrates, governs and audits AI-driven HR workflows across the employee lifecycle. Named components, deployed today.
Agentic infrastructure platform
Six layers. One platform.
The key components of the Zensible agentic infrastructure, from the channels people use down to the systems you already run.
- 1ExperienceWeb, mobile, Teams, Slack, email, APIs & integrations
- 2IntelligenceSupervisor agent, workflow orchestrators, functional agents, specialist agents
- 3Agent platformRuntime, workflow engine, planner, memory, tools, scheduler, model gateway, APIs
- 4Enterprise contextKnowledge graph, ontology, policies, business rules, context, decision memory
- 5Foundation servicesModel providers, vector DB, databases, cache, storage, messaging, analytics
- 6Enterprise systemsHRIS, ERP, ITSM, payroll, identity, collaboration, BGV & third-party systems
Trust, governance, observability
The cross-cutting layer.
Not a module you switch on. Trust, governance and observability are applied at every layer, on every run.
Governance
- Policy engine & guardrails
- Approval workflows (human in the loop)
- Model & prompt governance
- Audit trails & compliance
- Tenant isolation
Observability
- End-to-end tracing
- Monitoring & alerts
- SLA & performance metrics
- Cost & usage analytics
- Audit & reporting dashboards
- In-flight PII masking
- Customer-managed keys
- Zero AI retention
- OAuth & OpenID
- AES-256
- TLS 1.3
Pricing model
Agent-month pricing.
You pay for the work agents take on, measured in agent months. Here is how it adds up for an onboarding agent.
-
Step 1
Map one onboarding
From offer acceptance to Day 1, across 12 process steps.
- Onboarding initiation
- Document collection
- BGV initiation
- Asset provisioning
- Induction
- Payroll initiation
- + 6 more
28agentic steps5human-in-the-loop steps -
Step 2
Measure the effort
Human effort per onboarding, split between the agent and your team.
16 hrshandled by the agent
(2 person-days)4 hrswith your team
(0.5 person-days) -
Step 3
Scale to your volume
20agent months2 PD × 200 = 400 person-days5human months0.5 PD × 200 = 100 person-daysPriced on 20 agent months, with 80% of the effort handled by agents.
Illustrative example based on a delivered onboarding agent design. Assumes 8-hour person-days and 20 person-days per month. Sizing is agreed per process.
How it works
Trace one request, end to end.
A new joiner writes I have accepted my offer.
Follow that one message through the Zensible agentic infrastructure.
Step 1 of 9
Request
The candidate or employee asks in natural language, through a chat interface or email.
WhoCandidate
“I have accepted my offer.”
Step 2 of 9
Understand & route
Understands the intent, retrieves context, checks policies and routes the request to the right workflow.
What runsSupervisor agent
- Intent detection
- Context enrichment
- Policy & role check
- Routing decision
Step 3 of 9
Orchestrate
Creates the execution plan, coordinates the agents and monitors progress.
What runsOnboarding workflow orchestrator
- Plan
- Decompose
- Coordinate
- Monitor
- Adapt
Step 4 of 9
Execute with agents
The orchestrator invokes the right functional agents to get the work done.
What runsFunctional agents
- Document validation agent
- Asset allocation agent
- Meeting scheduler agent
Step 5 of 9
Leverage specialists
Specialist agents perform focused tasks and provide reusable capabilities.
What runsSpecialist agents & services
- OCR agent
- Email agent
- Calendar agent
- Notification agent
- Policy agent
Step 6 of 9
Platform runtime
Provides the execution infrastructure: state management, tools, memory, scheduling and reliability.
What runsAgent platform (runtime layer)
- Runtime engine
- Planner
- Scheduler
- Memory
- Tool registry
- Events & messaging
- Monitoring
- Error handling
- Human-in-the-loop
- Retry & state management
Step 7 of 9
Get enterprise context
Agents retrieve trusted enterprise context to make accurate, policy-compliant decisions.
What runsEnterprise context layer
- Org hierarchy
- Employee profiles
- Policies & rules
- Projects & skills
- Assets & inventory
- Historical decisions
- Conversation memory
Step 8 of 9
Execute across systems
Actions run securely across integrated systems through pre-built connectors and APIs.
Systems of recordEnterprise systems
- Workday HCM
- Active Directory
- IT service management
- Outlook / Calendar
- Inventory system
Step 9 of 9
Outcome delivered
The new joiner gets real outcomes, without chasing multiple teams.
ResultEmployee / candidate
- Laptop assigned
- BGV initiated
- Day-1 meeting scheduled
- Welcome email sent
See it on your process