AI Workforce / Agent Deployment OS
Move from one-off automations to managed agent packs with cleaner launch and governance posture.
Connector lanes
3
Required provider or connector categories that have to be ready before the lane is fully live.
Workflow templates
1
Workflow blueprints already mapped to this family in the shared service catalog.
Recommended bundles
1
Reusable launch bundles and vertical packages already linked to this service family.
Managed entry points
1
Flagship managed programs that can deliver this family as part of a broader commercial engagement.
Blueprint map
How this family turns into a real rollout
The shared catalog now maps each public service family to workflows, agent packs, onboarding steps, reporting, and dashboard modules without inventing a separate marketing model.
Workflow templates
Automation blueprints
Agent Launchpad
Stages agent-pack launches with approvals, readiness checks, and rollback posture.
Agent packs
AI workforce coverage
Workforce Orchestrator Pack
Launch and governance agents for multi-pack operational rollouts.
Onboarding
What must be ready before launch
Agent Launch
Stage agent-pack launch, fallback posture, and operator ownership.
Workflow Approvals
Review risky automations and sign off on change-control rules.
Dashboard modules
Where the work becomes visible
Agent Deployments
Agent-pack launch posture, rollouts, and launch guardrails.
Ops Exceptions
Queues for failures, retries, and operator intervention.
Provider readiness
Connectors and reporting that support the service family
These are the connector categories, reporting lanes, and supporting routes already mapped to this family in the shared service catalog.
Agent orchestration
Launch, govern, and observe agent-pack execution paths.
Workflow engine
Durable automation orchestration, approvals, and operational handoffs.
OpenAI runtime
LLM and retrieval runtime for grounded assistants and agent logic.
Supporting routes
Commercial fit
Managed programs and reusable packages already linked to this family
Each service family can sit inside a flagship managed program, a reusable launch bundle, or a more opinionated vertical package depending on how much of the operating model you need NEXA to own.
Trust posture
Why this public page stays believable
The catalog can expand the public story before every live execution seam is finished, but the repo still keeps the truth boundary explicit.
Shared catalog, not page-local copy
Services, bundles, pricing posture, workflow links, and form deep links resolve from the same typed service catalog.
Lead capture stays durable-first
Contact and audit requests still flow through one shared capture service with hashing, rate limits, and downstream dispatch tracking.
Delivery state stays honest
Public pages describe scope and rollout inputs, while real workspace activation and readiness remain in dashboard and admin service ledgers.