ENTERPRISE AGENT PLATFORM

Build, run and govern
real AI agents.

A unified control plane for enterprise agents, skills, MCP, models and execution runtimes — built for infrastructure you control.

◆ Kubernetes-native ◆ Governance-first execution ◆ Enterprise governance
Multi-tenantEnterprise isolation
KubernetesRuntime execution
PactKitDevelopment runtime
RUNTIME & AGENT ECOSYSTEM
CodexClaude CodeOpenCodePactKitMCPSkillsGitHubSlackFeishuAPI CodexClaude CodeOpenCodePactKitMCPSkillsGitHubSlackFeishuAPI
INTEGRATIONS

Connect every part of
your agent stack

Channels, models, tools and enterprise systems stay composable instead of being hard-wired into individual agents.

Slack
Feishu
⌘ GitHub
◈ MCP
◎ Skills
OpenAI
Anthropic
Microsoft Foundry
Databases
Knowledge Bases
Internal APIs
Custom Channels

And your own enterprise services through APIs and MCP

AGENT CONTROL PLANE

One platform for every agent application

Manage applications, agents, skills, MCP servers, models, jobs and governance as reusable platform primitives.

01Applications & AgentsSeparate the business deployment unit from the executor.
02Skills & MCPReusable intelligence and standardized tool connectivity.
03Models & CredentialsCentralize model access instead of embedding secrets in agents.
pacthorn / applicationsRUNNING
APPLICATION

Engineering Agent

Healthy
RuntimeDevelopment
Agents2
Skills11
PactKit Runtime ReadyCodex Adapter ReadyGit Workspace Mounted
GENERALAgent RuntimeLightweight tasks
DEVELOPMENTPactKit RuntimeCodex · Claude Code · Git
DATAAnalytics RuntimePython · SQL
☸ KubernetesOn-PremCloudHybrid
RUNTIME PROFILES

The right environment for every kind of agent

Application type should not be coupled directly to a container image. Runtime Profiles translate execution needs into Kubernetes workloads.

Isolated executionOne job, one controlled runtime. Toolchain-specificBring PactKit, Git or data tooling only where needed. Policy-awareResources, secrets and network rules follow the profile.
DEVELOPMENT RUNTIME

Let PactHorn launch PactKit —
without breaking PactKit apart

Development is a specialized workload. PactHorn schedules and governs the runtime; PactKit remains the complete spec-driven engineering framework inside it.

development-job.yaml
application:
  type: development

runtime:
  profile: pactkit-dev
  image: pacthorn/dev-runtime

execution:
  agent: codex

workspace:
  repository: pacthorn-demo
01
Development Job

Submit a feature, bug or engineering task through PactHorn.

02
Ephemeral Dev Pod

Kubernetes creates an isolated workspace for the job.

03
PactKit Workflow

Plan → Spec → Implement → Test → Review remains owned by PactKit.

04
Coding Agent Adapter

Codex, Claude Code or OpenCode execute inside the runtime.

PactKitCodexClaude CodeOpenCodeGitCodeGraphpre-commit
REAL AGENT WORK

One platform.
Many agent workloads.

Use the same platform foundation for engineering, research, operations, data and custom business agents.

How it works
ENGINEERING AGENT

Implement feature request

PactKit runtime · Codex · Git

Running tests…
RESEARCH AGENT

Competitive landscape

12 sources synthesized

Complete
OPS AGENT

Investigate latency

Approval required

Waiting
DATA AGENT

Analyze operational KPIs

Semantic query ready

Ready
WHY PACTHORN

Built for enterprise agent operations

Run in your infrastructure

Kubernetes-native deployment across on-prem, cloud and hybrid environments.

Keep capabilities reusable

Skills, MCP, models and runtime profiles remain independent platform resources.

Govern once

Tenant isolation, policy, audit, secrets and observability stay centralized.

Open integration

Connect Feishu, Slack, GitHub, APIs, data and enterprise systems.

Development-ready

PactKit and coding agents fit into a dedicated development runtime.

FAQ & ARCHITECTURE

Common questions

What is PactHorn?

PactHorn is an enterprise agent platform and control plane for managing applications, agents, skills, MCP, model access, runtime profiles, jobs and governance.

Is PactHorn a SaaS service?

No. The product direction is infrastructure you deploy and control, rather than a public hosted SaaS login experience.

How does PactKit integrate with PactHorn?

PactKit is not decomposed into a few skills. A Development Runtime includes PactKit as the engineering framework, while PactHorn schedules and governs the Development Job.

How are Codex and Claude Code executed?

They are installed in the development runtime image and invoked through coding-agent adapters inside the Kubernetes workload.

Can PactHorn integrate with Feishu?

Yes. Feishu can act as a channel into PactHorn, alongside APIs and other supported channels.

CONTACT

Interested in PactHorn?

Evaluating an enterprise agent platform, exploring private deployment, or interested in technical collaboration? Send a short note and tell us what you are working on.

Prefer another channel? GitHub ↗
Security check is loading…

Please do not include passwords, API keys, proprietary source code, or other sensitive information.

PactHorn

Build real AI agents.
Keep the platform under your control.

Explore PactHorn and the wider P.A.C.T. ecosystem.

View on GitHub ↗