Deployment
How a Keyra agent reaches your tenant world
Every agent is a clean operational design at the catalog layer. It becomes a deployed digital worker only after passing identity lineage, security, legal, and tenant approval gates.
- 1Browse the marketplaceCustomer selects agents that fit their operational scope and regulatory context.
- 2Build a deployment planAdd agents to a plan. Provide organization, country, and tenant domain.
- 3Keyra reviewKeyra reviews the plan, scopes integrations, and confirms knowledge packs.
- 4Security + legal approvalSecurity and legal approvals are recorded and must complete before activation.
- 5Tenant agent instance generatedA tenant_agent_instance_id is created per deployed agent.
- 6Customer agent world activatesCustomer-specific tenant world receives subscribed agents and integration checklist.
- 7Operate and auditEvery action is audited. Subscription is fully revocable.
Agent ID lineage
Stage 1
Ciright Parent Agent ID
agents.ciright.com — origin
Stage 2
Keyra Catalog Agent ID
ciright.agents.keyra.ie — design
Stage 3
Subscription Agent ID
agents.keyra.ie — commercial
Stage 4
Tenant Agent Instance ID
your tenant world — operational
What customers receive
- · Subscribed agent shells
- · Permission templates
- · Deployment workflow
- · Integration checklist
- · Audit model
- · Customer-specific knowledge pack area
What customers never receive
- · Other customer data
- · Other tenant audit logs
- · Keyra private data, unless explicitly approved