AgentKube
Sign in Contact sales

Build AI agents like ChatGPT

The enterprise platform to rapidly orchestrate, build, test, and deploy AI agents, with infrastructure configured for you and running in your environment.

Contact sales → Get started
Agent builder MCP integrations Testing Deployment infrastructure Ready to run in your environment.
02 · The problem

Every enterprise wants agents. Getting one into production still takes months

Infrastructure, code, integrations, security checks, testing and validation all have to happen before go-live, and that can take one to six months before anyone uses it.

Before anyone uses the agent1 to 6 months
Infrastructure2 to 6 weeks
Code2 to 8 weeks
Integrations2 to 6 weeks
Security checks1 to 4 weeks
Testing1 to 3 weeks
Validation1 to 2 weeks
Week 0Month 2Month 4Month 6
With AgentKubeconfigured for you
days
03 · The platform

One development stack
for every agent

Build, connect, test and deploy in one place, so the second agent reuses everything the first one needed.

Buildwithout starting from scratch

Describe the agent in plain language, generate its steps and tool calls, then refine it with your team.

✓One prompt or turn by turn✓Steps you can read and edit✓Teams and Slack
Connectusing MCP and existing systems

Connect approved tools, APIs, data sources and internal services without rebuilding integrations for each agent.

✓Your own MCP servers✓SaaS apps and data stores✓Scoped per agent
Testbefore anything goes live

Run test cases on every change. Check answers, tool calls, permissions and what happens when a system fails.

✓Test cases per agent✓Tool-call validation✓Compare versions
Deployin your environment

Move from development to your infrastructure with repeatable deployment and operational controls.

✓Local, private or your cloud✓Versioned, gradual rollout✓Audit log
Testing is part of the buildEvery change runs the agent’s test cases: expected answers, tool-call checks, permissions and failure handling.
✓Eligible employee enrolls in a plananswer
✓Calls workday.submit_enrollment oncetool call
✓Contractor is told they are not eligiblepermission
✓Workday timeout: retries, then hands offfailure
!Dependent without a birth date: asks againanswer
04 · See it in action

From agent specification
to working implementation

Example: an employee benefits agent connected to your HR and benefits systems.

1
Describe the agentIts purpose, rules, data sources and actions, in plain language.
2
Generate the agentAgentKube creates the steps, tool calls and configuration.
3
Connect enterprise systemsUse MCP to connect approved tools and data sources.
4
Test and validateCheck expected behavior, permissions and failure handling.
5
DeployRun the agent in your target environment.
AgentKube builderagents/open-enrollment.md
Describe
Describe the agent…↑
Time to a tested, deployable agentfrom first description to live in your cloud≈ 2 days
Describe · 20 minGenerate · 10 minConnect · 4 hTest · 1 dayDeploy · 2 h
Illustrative breakdown for the benefits agent. Replace with your measured builds.
05 · Deploy in your environment

Local while you build. Your cloud when it ships

Run on a laptop, your private infrastructure, or your Google Cloud, Azure or AWS account. Create environments for each place it runs, then manage deployments: versioned, rolled out gradually, rolled back in one step.

Versioned releasesGradual rolloutRollback

Pick a target

The same agent files run everywhere. Change the target, not the agent.

This computerwhile you build
Your serversDocker or SSH
Google CloudCloud Run or GKE
AzureContainer Apps
AWS Bedrockmodels in your account
$ npx agentfile up

Environments

+ New environment

Create one per place your runtime runs, pick its containers, tag it, and see whether it is connected.

prodAzure App Service · eastus
tier:prodregion:usteam:benefits
Connected
stagingGoogle Cloud Run · us-central1
tier:staging
Connected
devDocker on this machine
tier:dev
Disconnected

Deployments

Deploy a version

Ship versions to environments by tag, gradually or all at once. Roll back in one step, or automatically when a check fails.

v15prod
Rolling out20% · health ok
Roll back
v15staging
Liveall conversations
v13prod
Rolled backauto: a test case failed
06 · Security and governance

Your agents
Your infrastructure
Your control

Deploy agent runtimes within your environment. Control which tools and data each agent can access, manage who can build and publish agents, and keep visibility into agent activity.

Visit the Trust center →
DeploymentYour cloud, private infrastructure, or local development.
Access controlSSO with Entra ID and Okta, roles and permissions.
Integration boundariesOnly approved MCP servers, tools and data sources.
OperationsAudit logs, versioning, testing and monitoring.

SSO with Entra ID and Okta

Staff sign in with the account they already have. Groups decide who can build, publish, or only pick up handoffs.

Continue with Microsoft Entra ID
Continue with Okta
SAML and OIDCSCIM provisioningAudit log

Memory and knowledge base

What an agent remembers is a folder of plain files you can read, edit and delete. Answers cite the documents they came from.

memory/
Closes early on FridaysLearned Oct 3 · you accepted it
memory/
Dana prefers text messagesLearned Sep 28 · conversation 4821
Knowledge · 5 sources indexedWebsite, help center, policies, price list
Agents propose memories. Nothing is saved without your OK.

Your data stays in your network

The runtime runs inside your network. Conversations, memory and your data stores never pass through AgentKube.

Inside your network
RuntimeConversationsMemory filesKnowledge indexData stores
outbound only
Sent to AgentKubeVersion check-ins and usage counts. No conversation content.
07 · Integrations and models

Use the models and systems
you already have

Switch model providers per agent. Connect approved MCP servers and data stores once, and reuse them across agents.

Model providers

BYOK
OpenAI
GPT-6 AstraGPT-6.1 SolGPT-6 Luna
Anthropic
Fable 5.1Opus 5.5Sonnet 5.5Haiku 5.5
Gemini
Gemini 4 ArgonGemini 3.8 Flash
Meta
Muse Spark 1.3
Mistral
Mistral Large 4Mistral Medium 3.5
OpenRouter
Any model, one key
Ollama
Qwen3.8DeepSeek V4.1 FlashGLM-5.3
Bring your own API key for every provider. Pick a model per agent; keys stay in your vault.

MCP and data stores

Plug in your MCP servers and connect agents to the data stores you already run. Nothing gets copied out.

your-tools-mcpyour own server · ready to add tools
Salesforceaccounts, cases, opportunities
AtlassianJira and Confluence
ServiceNowincidents, requests, CMDB
OracleERP, finance, HCM
Postgresorders, customers
Snowflakeanalytics warehouse
WWorkdayemployees, benefits, enrollments
Each agent sees only the tools and data you give it.
Reach people where they work

One platform
Every audience

Deliver AI agents to your customers, empower your employees with internal agents, and give your teams and developers AgentKube Designer to build, test, and deploy them.

For your customersFor your employeesFor your teams and developers
Northwind Health LocationsServicesBilling northwind.health
Care close to home, open late.
Northwind HealthPowered by AgentKube
Ask anything…

For your customers: embed agents on your public website and customer-facing applications.

See your first agent running in your environment this week

Bring one use case. We’ll build, test and deploy it with your team in a technical session.

Contact sales →Book a technical demo