self-hosted AI agent operations: You own the execution layer.

ConvOps is the operations layer for AI agents, on your own infrastructure. Teach your process once. Every AI and every person runs it the same way, with the gates, the record and the controls your enterprise needs.

self-hosted · your Kubernetes · your models

ConvOps cloud6 of 8
Engine
Shared memory
Audit
Web app
Runs
Secrets
your AI client over HTTPSoutbound only
Your Kubernetes2 of 8
Models
Repos

Cloud ConvOps Cloud runs the operation. Your AI tools, models and repositories stay yours and connect over HTTPS.

in short

What does ConvOps give an enterprise AI program?

The operations layer for AI agents across the enterprise: one process for every AI tool and team, gates that hold a step until a condition is met, an audit trail, and the option to self-host on your Kubernetes.

ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.

key facts · october 2026

  • Self-hosted, the engine, shared memory, the audit and every run live in your own Kubernetes cluster, installed from one Helm chart delivered with the Enterprise plan.
  • You bring the model provider and credentials. Runs use Claude Code or OpenCode today.
  • Claude, Cursor, ChatGPT and Codex all connect to the same workspace, so teams keep the AI tools they use.
  • Approval gates and field-level audit rows support the human oversight that Article 14 of the EU AI Act asks for.
  • Enterprise starts from $2,500 a month, under a commercial licence.

best for

  • Companies rolling AI agents out to several teams that need one process and one record.
  • Regulated organizations that cannot send code or data outside their cluster.

not for

  • Buying AI models or seats. ConvOps does not resell models and does not price per seat or per token.

updated

the questions

Where does our code run?

Security asks that first. The business asks the next three, usually after something went wrong.

“Who approved that?”

An agent changed something that matters. The approval lived in a chat, if it happened at all.

“Where did that decision go?”

It was made in one AI tool, in one session, by one person. Nobody else can find it now.

“What happens when someone leaves?”

The process lived in their prompts. It leaves with them, and the AI never learned it.

the architecture

Your stack, governed.

Your AI tools on top. ConvOps in the middle, holding the process. Your executors and your cluster underneath, doing the work.

your AI toolskeep them
Claude
Cursor
ChatGPT
Codex
MCP
ConvOps owns the governancecloud or self-hosted
Workflow enginesteps, in order
Shared memorydecisions, reasons
Governancegates · audit · roles
waiting for workexample
dispatch
you own the execution layer
Your machinelocal
Your runnercustom
Isolated runKubernetes
your Kubernetes · convops-runsone pod per run
free
free
free
free
what you control

Yours, end to end.

The cluster, the models, the keys, the network, the record and the boundaries between teams. ConvOps governs the work; it does not take any of these.

Your cluster

Every run is a pod in your Kubernetes. Self-hosted, the engine, shared memory and the audit live there too.

Helm chart, with Enterprise

Your models and keys

Bring your own model provider and credentials. Isolated runs use Claude Code or OpenCode; people work locally with any AI client that connects.

bring your own

Your secrets

Stored through a one-time link, never pasted in chat. Each run gets its own Secret, masked in every log and transcript.

never in the chat

Your network policy

Your network plugin enforces it: run pods take no inbound traffic and cannot reach the rest of your cluster. No service-account token, non-root, every capability dropped.

pod security: restricted

Your audit

Every task and every workflow instance keeps its history, step by step. Every run keeps tokens, cost, duration and result.

tasks + workflow instances

Your workspaces

One per team, business unit or customer, each walled off. Three roles in each: owner, admin, member.

walled off by default

the rollout

Roll out at your own pace.

Start with one real process. Add checkpoints where your risk team wants them, and let the rest run on schedules.

01your pilot team

A pilot workspace.

One team, one workspace, one real process. Put a checkpoint on every step if your risk team wants to start that way. Every run leaves a record.

ConvOps · workspace pilotexample

Refund review · pilot · a checkpoint on every step, by choice

planwaiting for you
changeapproval
testapproval
shipapproval
approvals4 of 4 steps
example · Claudeconnected to ConvOps
Refunds over 200: check the order, draft the reply, a lead approves, then send.
workflow created · Refund review · 4 steps · 1 approval
Done. Every refund request now runs this workflow, from any AI tool your team uses.

the same workflow runs in Cursor, ChatGPT and Codex

ConvOps · workflow Refund reviewexample

week one

planwaiting for you
changeapproval
testapproval
shipapproval

now

plan
change
test
shipapproval
done
approvals1 of 4 steps · the one that ships
schedules · example
000306091215182101:0003:0004:30
22:30sun · Europe/Londonnight window
schedulesEurope/London
  • 01:00KYC file reviewevery weekday 01:00not today
  • 03:00Nightly reportevery day 03:00in 4h 30m
  • 04:30Control checksmondays 04:30not today
next: KYC file review in 2h 30m
example · your cluster · Enterprise Helm chartdelivered with Enterprise
your Kubernetesyour modelsyour keysyour network
Engineering
fix
reviewapproval
ship
owner · admin · member
Support
triage
replyapproval
close
owner · admin · member
Finance
check
approveapproval
post
owner · admin · member
Customer: Northwind
intake
deliverapproval
report
owner · admin · member

example workspaces · each walled off · same governance

02your process owner

Teach the first processes.

Describe how the work goes, in the AI tool you already use. ConvOps turns it into a workflow that every AI runs the same way.

ConvOps · workspace pilotexample

Refund review · pilot · a checkpoint on every step, by choice

planwaiting for you
changeapproval
testapproval
shipapproval
approvals4 of 4 steps
example · Claudeconnected to ConvOps
Refunds over 200: check the order, draft the reply, a lead approves, then send.
workflow created · Refund review · 4 steps · 1 approval
Done. Every refund request now runs this workflow, from any AI tool your team uses.

the same workflow runs in Cursor, ChatGPT and Codex

ConvOps · workflow Refund reviewexample

week one

planwaiting for you
changeapproval
testapproval
shipapproval

now

plan
change
test
shipapproval
done
approvals1 of 4 steps · the one that ships
schedules · example
000306091215182101:0003:0004:30
22:30sun · Europe/Londonnight window
schedulesEurope/London
  • 01:00KYC file reviewevery weekday 01:00not today
  • 03:00Nightly reportevery day 03:00in 4h 30m
  • 04:30Control checksmondays 04:30not today
next: KYC file review in 2h 30m
example · your cluster · Enterprise Helm chartdelivered with Enterprise
your Kubernetesyour modelsyour keysyour network
Engineering
fix
reviewapproval
ship
owner · admin · member
Support
triage
replyapproval
close
owner · admin · member
Finance
check
approveapproval
post
owner · admin · member
Customer: Northwind
intake
deliverapproval
report
owner · admin · member

example workspaces · each walled off · same governance

03you decide

Place checkpoints where they belong.

A checkpoint can wait for a person, or require a metric or a report before the run moves on. Keep them where production, money and customers are at stake. Leave them out where the work can run by itself.

ConvOps · workspace pilotexample

Refund review · pilot · a checkpoint on every step, by choice

planwaiting for you
changeapproval
testapproval
shipapproval
approvals4 of 4 steps
example · Claudeconnected to ConvOps
Refunds over 200: check the order, draft the reply, a lead approves, then send.
workflow created · Refund review · 4 steps · 1 approval
Done. Every refund request now runs this workflow, from any AI tool your team uses.

the same workflow runs in Cursor, ChatGPT and Codex

ConvOps · workflow Refund reviewexample

week one

planwaiting for you
changeapproval
testapproval
shipapproval

now

plan
change
test
shipapproval
done
approvals1 of 4 steps · the one that ships
schedules · example
000306091215182101:0003:0004:30
22:30sun · Europe/Londonnight window
schedulesEurope/London
  • 01:00KYC file reviewevery weekday 01:00not today
  • 03:00Nightly reportevery day 03:00in 4h 30m
  • 04:30Control checksmondays 04:30not today
next: KYC file review in 2h 30m
example · your cluster · Enterprise Helm chartdelivered with Enterprise
your Kubernetesyour modelsyour keysyour network
Engineering
fix
reviewapproval
ship
owner · admin · member
Support
triage
replyapproval
close
owner · admin · member
Finance
check
approveapproval
post
owner · admin · member
Customer: Northwind
intake
deliverapproval
report
owner · admin · member

example workspaces · each walled off · same governance

04the schedule

Unattended runs, on a schedule.

Nightly and weekly work runs on its own, each run in its own pod, at the times and in the time zone you set. Each run leaves a record.

ConvOps · workspace pilotexample

Refund review · pilot · a checkpoint on every step, by choice

planwaiting for you
changeapproval
testapproval
shipapproval
approvals4 of 4 steps
example · Claudeconnected to ConvOps
Refunds over 200: check the order, draft the reply, a lead approves, then send.
workflow created · Refund review · 4 steps · 1 approval
Done. Every refund request now runs this workflow, from any AI tool your team uses.

the same workflow runs in Cursor, ChatGPT and Codex

ConvOps · workflow Refund reviewexample

week one

planwaiting for you
changeapproval
testapproval
shipapproval

now

plan
change
test
shipapproval
done
approvals1 of 4 steps · the one that ships
schedules · example
000306091215182101:0003:0004:30
22:30sun · Europe/Londonnight window
schedulesEurope/London
  • 01:00KYC file reviewevery weekday 01:00not today
  • 03:00Nightly reportevery day 03:00in 4h 30m
  • 04:30Control checksmondays 04:30not today
next: KYC file review in 2h 30m
example · your cluster · Enterprise Helm chartdelivered with Enterprise
your Kubernetesyour modelsyour keysyour network
Engineering
fix
reviewapproval
ship
owner · admin · member
Support
triage
replyapproval
close
owner · admin · member
Finance
check
approveapproval
post
owner · admin · member
Customer: Northwind
intake
deliverapproval
report
owner · admin · member

example workspaces · each walled off · same governance

05your platform team

Self-hosted on your cluster.

Your platform team installs one Helm chart, delivered with Enterprise, in your Kubernetes. Your models, your keys, your network. Nothing has to leave.

ConvOps · workspace pilotexample

Refund review · pilot · a checkpoint on every step, by choice

planwaiting for you
changeapproval
testapproval
shipapproval
approvals4 of 4 steps
example · Claudeconnected to ConvOps
Refunds over 200: check the order, draft the reply, a lead approves, then send.
workflow created · Refund review · 4 steps · 1 approval
Done. Every refund request now runs this workflow, from any AI tool your team uses.

the same workflow runs in Cursor, ChatGPT and Codex

ConvOps · workflow Refund reviewexample

week one

planwaiting for you
changeapproval
testapproval
shipapproval

now

plan
change
test
shipapproval
done
approvals1 of 4 steps · the one that ships
schedules · example
000306091215182101:0003:0004:30
22:30sun · Europe/Londonnight window
schedulesEurope/London
  • 01:00KYC file reviewevery weekday 01:00not today
  • 03:00Nightly reportevery day 03:00in 4h 30m
  • 04:30Control checksmondays 04:30not today
next: KYC file review in 2h 30m
example · your cluster · Enterprise Helm chartdelivered with Enterprise
your Kubernetesyour modelsyour keysyour network
Engineering
fix
reviewapproval
ship
owner · admin · member
Support
triage
replyapproval
close
owner · admin · member
Finance
check
approveapproval
post
owner · admin · member
Customer: Northwind
intake
deliverapproval
report
owner · admin · member

example workspaces · each walled off · same governance

06the whole company

Every team, its own workspace.

Engineering, support, finance, each customer. One workspace each, walled off, with the same governance in every one.

ConvOps · workspace pilotexample

Refund review · pilot · a checkpoint on every step, by choice

planwaiting for you
changeapproval
testapproval
shipapproval
approvals4 of 4 steps
example · Claudeconnected to ConvOps
Refunds over 200: check the order, draft the reply, a lead approves, then send.
workflow created · Refund review · 4 steps · 1 approval
Done. Every refund request now runs this workflow, from any AI tool your team uses.

the same workflow runs in Cursor, ChatGPT and Codex

ConvOps · workflow Refund reviewexample

week one

planwaiting for you
changeapproval
testapproval
shipapproval

now

plan
change
test
shipapproval
done
approvals1 of 4 steps · the one that ships
schedules · example
000306091215182101:0003:0004:30
22:30sun · Europe/Londonnight window
schedulesEurope/London
  • 01:00KYC file reviewevery weekday 01:00not today
  • 03:00Nightly reportevery day 03:00in 4h 30m
  • 04:30Control checksmondays 04:30not today
next: KYC file review in 2h 30m
example · your cluster · Enterprise Helm chartdelivered with Enterprise
your Kubernetesyour modelsyour keysyour network
Engineering
fix
reviewapproval
ship
owner · admin · member
Support
triage
replyapproval
close
owner · admin · member
Finance
check
approveapproval
post
owner · admin · member
Customer: Northwind
intake
deliverapproval
report
owner · admin · member

example workspaces · each walled off · same governance

ConvOps · workspace pilotexample

Refund review · pilot · a checkpoint on every step, by choice

planwaiting for you
changeapproval
testapproval
shipapproval
approvals4 of 4 steps
example · Claudeconnected to ConvOps
Refunds over 200: check the order, draft the reply, a lead approves, then send.
workflow created · Refund review · 4 steps · 1 approval
Done. Every refund request now runs this workflow, from any AI tool your team uses.

the same workflow runs in Cursor, ChatGPT and Codex

ConvOps · workflow Refund reviewexample

week one

planwaiting for you
changeapproval
testapproval
shipapproval

now

plan
change
test
shipapproval
done
approvals1 of 4 steps · the one that ships
schedules · example
000306091215182101:0003:0004:30
22:30sun · Europe/Londonnight window
schedulesEurope/London
  • 01:00KYC file reviewevery weekday 01:00not today
  • 03:00Nightly reportevery day 03:00in 4h 30m
  • 04:30Control checksmondays 04:30not today
next: KYC file review in 2h 30m
example · your cluster · Enterprise Helm chartdelivered with Enterprise
your Kubernetesyour modelsyour keysyour network
Engineering
fix
reviewapproval
ship
owner · admin · member
Support
triage
replyapproval
close
owner · admin · member
Finance
check
approveapproval
post
owner · admin · member
Customer: Northwind
intake
deliverapproval
report
owner · admin · member

example workspaces · each walled off · same governance

governance at scale

Same rules, every team.

Gates the engine checks on every move. A history for every task. Three roles. A workspace per team, business unit or customer.

every request, every team · example
requestany AI tool
planthe workflow
approveapproval
runyour cluster
recordedtask history

policies guide · gates hold Policies are guidance the AI reads. Gates, required metrics and required reports are what the engine checks. A gated step holds until an explicit approval is given, recorded with the account that gave it.

examples

Processes you could start with.

Examples, not customer stories. Each card names the feature that does the work, with a link to how it works.

example · retail bank

Periodic KYC refresh

Each customer file records a completeness check with a link to the document as evidence. The batch step holds until the check is recorded, and the trend shows the completion rate against the target your compliance team set on that step.

Metrics

example · finance

Month-end close

One program groups the close schedules under one owner and goal. Each run files a reconciliation report, and the program tells you which runs are healthy, late, silent or failing.

Programs

example · compliance

SOC 2 control checks

Each control check files the same structured report: the control, the result and the evidence. The step holds until the report is filed, so a missing check is visible, not assumed.

Governance

example · global support

Follow-the-sun triage

Three schedules on one workflow, each at 08:00 local time in Singapore, Dublin and Chicago. Each schedule keeps its own time zone, and daylight saving does not move it.

Unattended runs

example · restricted networks

Your runners, your network

Your own runners claim work from ConvOps over HTTPS. Runs and secrets stay inside your network, with no inbound ports.

Executors

the difference

Scattered AI vs governed AI.

  • Each person prompts the AI their own way.
  • Approvals live in chat, if they happen at all.
  • Agents run on laptops, with whatever access they have.
  • Nobody can say what ran, or what it cost.
  • Knowledge leaves with the people who had it.
  • Each security review starts from zero.
  • One process, taught once, run the same way by every AI.
  • A gate holds the step until an explicit approval is given, recorded with the account that gave it.
  • Every run in its own pod on your cluster, with only its own secrets.
  • Every run keeps tokens, cost, duration and result.
  • Decisions and reasons kept in shared memory, linked to the work.
  • Self-hosted on your Kubernetes. Nothing has to leave your cluster.

One chart, one values file

The Helm chart delivered with Enterprise takes one values file: the run namespace, pod posture, network policy, time limit and model credentials.

payload
# install (example): the chart is delivered with Enterprise
helm install convops ./convops \
  --namespace convops --create-namespace \
  -f values.yaml

# values.yaml (example keys)
runs:
  namespace: convops-runs
  podSecurity: restricted
  networkPolicy:
    ingress: none
    egress: limited
  timeLimit: 4h
models:
  existingSecret: model-credentials
example · chart delivered with Enterprise · keys are illustrative

An isolated executor

One call names the engine, a pinned version, the model, the time limit and the provider connections it runs with. A key on the executor is refused; each key lives on a connection, handed over once.

payload
executors_manage({
  "action": "create",
  "workspace": "engineering",
  "slug": "isolated-sonnet",
  "runner": "convops",
  "connections": ["anthropic-team"],
  "config": {
    "backend": "isolated",
    "isolated": {
      "agent": "claude-code",
      "agent_version": "2.1.4",
      "model": "sonnet",
      "time_limit_s": 14400
    }
  }
})

// response (abridged)
{
  "slug": "isolated-sonnet",
  "connections": [{ "name": "anthropic-team", "provider": "anthropic" }],
  "active_check": { "status": "queued", "trigger": "create" }
}
example · executors_manage create, isolated backend

Unattended work runs on a schedule

A schedule fires on a cadence you pick, in the time zone you set. It creates the task and runs it on the executor you name.

payload
{
  "tool": "schedule_create",
  "arguments": {
    "title": "KYC file review {date}",
    "vertical": "operations",
    "project": "customer-onboarding",
    "cadence": { "kind": "weekdays", "at": "01:00" },
    "timezone": "Europe/London",
    "executor": "isolated-sonnet"
  }
}
example · schedule_create

A workspace per customer

Members join a workspace with one of three roles. Invites wait to be accepted and expire after seven days.

payload
{
  "workspaces_members_manage": {
    "action": "create",
    "workspace": "northwind",
    "email": "lead@northwind.example",
    "role": "member"
  }
}
example · workspaces_members_manage
how we engage

Three steps to a governed rollout.

No big-bang migration. We start on one real process of yours and grow from there.

01you and us

Discovery call

We walk through one process you want to run on ConvOps, and where your models, runs and data need to live.

02your pilot team

Pilot on your process

One workspace, checkpoints where your risk team wants them, your team in the loop. Weeks, not quarters.

03your platform team

Self-hosted rollout

Your platform team installs the Helm chart delivered with Enterprise. Teams move over one workspace at a time.

book a demo

See it run your own process.

Bring one process and your security questions. We show ConvOps running it, and where it would live in your cluster.

questions

What procurement asks.

What is ConvOps Enterprise?

ConvOps Enterprise is ConvOps, the operations layer for AI agents, run on your own Kubernetes or next to it. Your teams keep their AI clients; ConvOps holds the process as workflows with gates, a shared memory, schedules, programs, metrics and an audit trail. Self-hosting comes as one Helm chart, delivered with Enterprise, with support from the engineers who build it.

Where does our data live?

Self-hosted, ConvOps runs in your own Kubernetes cluster, in the region and under the controls you already operate. The engine, shared memory, the audit trail and every run live there, and nothing has to leave your cluster. In a hybrid setup, runs and secrets stay in your cluster and your runners claim work from ConvOps over HTTPS, with no inbound ports.

Which AI models can we use?

Your own. With ConvOps you bring the model provider and the credentials, handed over through a one-time link and masked in every log. Isolated runs use Claude Code or OpenCode, with the model you pin on each executor. People work locally with any AI client that connects to ConvOps, such as Claude, Cursor, ChatGPT or Codex.

Can we run it without the ConvOps cloud?

Yes. Self-hosted, the whole of ConvOps runs in your cluster from one Helm chart, delivered with Enterprise. Runs reach only the model endpoints, repositories and connected tool servers you configure. Metric trends and program KPIs read from OpenSearch in your cluster; recording metrics and the gates that require them work without it.

How does licensing work?

Self-hosted ConvOps runs under a commercial licence, scoped with you on a call around your teams, your workspaces and your rollout. Programs, the Plan board, schedules and metrics are included, as they are on every ConvOps plan. There is nothing to sign before the pilot shows you it works on a real process of yours.

Who supports it?

Neomanex, the team that builds ConvOps. You talk to the engineers who wrote the engine, from the first call through the rollout and after it. Support terms are part of the commercial licence and are agreed with you, around the teams, the workspaces and the processes you run on ConvOps.

How long does a pilot take?

Weeks, not quarters. A ConvOps pilot is one workspace and one real process of yours, for example a KYC file review, a month-end close checklist or support triage. You place checkpoints where your risk team wants them, watch the process run on your own work, and decide on the rollout after that.

Do our people have to change their AI tools?

No. Claude, Cursor, ChatGPT and Codex connect to ConvOps as they are, with a browser sign-in. Your teams keep the tools they use; the process, the gates and the record move into ConvOps. Unattended work runs as isolated runs with Claude Code or OpenCode, inside your cluster when you self-host.