Enterprise Migration

Enterprise Migration

This guide covers adopting AgentCTX in an enterprise environment — phased rollout strategy, data migration, compliance considerations, and multi-tenant setup.

Migration Phases

Phase 1: Pilot (Weeks 1–2)

Start with a single team on a non-critical project:

1. Install AgentCTX locally or via Docker Compose
2. Connect existing MCP backends (GitHub, filesystem)
3. Enable knowledge plane on project documentation
4. Measure token savings and agent productivity gains

actx init
actx add github --command "npx -y @modelcontextprotocol/server-github" --roles "code"
actx start --transport sse --port 3100

Phase 2: Team Rollout (Weeks 3–4)

Expand to the full team:

1. Deploy Docker Compose stack for shared SurrealDB and NATS
2. Enable team-level memory (#team layer)
3. Configure RBAC roles per team member’s agent
4. Set up token budgets

Phase 3: Organization (Weeks 5–8)

Scale across the organization:

1. Deploy to Kubernetes for HA and multi-tenant isolation
2. Enable org-level memory (#org layer)
3. Integrate 1Password for secrets management
4. Enable Sentinel monitoring in active mode
5. Set up compliance audit trail via actx verify

Phase 4: Production (Ongoing)

1. Enable federation for cross-org communication
2. Deploy Rust native components for performance
3. Set up SurrealDB clustering for HA
4. Enable NATS superclusters for global messaging

Data Migration

From RAG Systems

If you’re migrating from a RAG (Retrieval-Augmented Generation) system:

1. Export documents from your vector store
2. Ingest into AgentCTX’s knowledge plane:

   actx ingest exported-docs/

3. Verify with semantic search:

   ?k "your test query" ^5

From Custom Memory Systems

Export memories as JSON and import via the CLI:

actx import memories.json --plane memory --layer team

Compliance

Audit Trail

Every agent action produces a cryptographically signed translation:

• What the agent did (CTX statement)
• How it was described (human-readable translation)
• Proof it wasn’t tampered with (Ed25519 signature)
• When it happened (ISO 8601 timestamp)

Run actx verify at any time to validate the entire audit trail.

Data Residency

• SurrealDB can be deployed in any region
• Content-addressed store keeps data local
• NATS superclusters support geo-aware routing

SOC 2 / ISO 27001

AgentCTX’s security model maps to common compliance frameworks:

Control	AgentCTX Feature
Access control	RBAC + ring-based access
Audit logging	Signed sidecar translations
Data encryption	AES-256-GCM convergent encryption
Key management	1Password integration or local Ed25519
Monitoring	Sentinel + OpenTelemetry

Multi-Tenant Setup

For SaaS or shared infrastructure:

# Each tenant gets isolated namespace
tenants:
  - id: team-alpha
    namespace: alpha
    budget: { perDay: 1000000 }
    roles: [code, issues, admin]
  - id: team-beta
    namespace: beta
    budget: { perDay: 500000 }
    roles: [code, issues]

Tenants share infrastructure but have isolated:

• SurrealDB namespaces
• NATS subjects
• Memory layers
• Token budgets

See Also

• Deployment — infrastructure options
• Security Model — compliance-relevant security
• Configuration — setup reference