Operation Kit

The infrastructure layer for AI implementation consultants.

Install it once per client, on the client's own server. They own it; you build on it.

Operation Kit is a ready-made base for putting AI to work inside a business. A consultant installs
one copy per client, on a server the client owns, in under an hour. The client gets a private web
app with a knowledge base of their own documents, AI workers that run jobs as cards on a board, an
optional chat with ready-made agents, and a secure connection for the AI apps their people already
use (Claude, ChatGPT, Grok). The consultant starts every engagement 80 to 90 percent of the way
there and spends their time on the client's actual workflows.

Why the client owns the install

• Their server, their data. Every client has its own copy on its own server. There is no shared
  Operation Kit cloud and no central database holding several clients' data.
• Their AI accounts. Work runs on the client's own Claude subscription or API key (OpenAI and
  Gemini optional). No pooled or resold seats.
• Fewer vendor-risk questions. Because client data never sits on a vendor's systems, the usual
  "is your vendor SOC 2 audited?" question mostly becomes "is our own server set up well?". To be
  plain about it: Operation Kit has no SOC 2 attestation, and we do not claim one. See the
  security overview for what is protected and what is not done yet.
• No lock-in to a model. Agents, skills and the knowledge base are plain files on the server.
  Switch the AI provider and none of it moves.

What is inside

Install

A fresh Ubuntu 24.04 server, the client's domain on Cloudflare, and a Claude account. Claude Code on
your laptop follows INSTALL.md and does the work; you answer a few questions and do two
short sign-ins. About 30 to 45 minutes, most of it waiting for the build.

The code: https://github.com/m1keluka/OperationKit (updates come from the same place, and are
applied by hand: Updating).

Recommended stack (what we run and test): an OVHcloud Rise dedicated server, Backblaze B2
for encrypted off-site backups, and Cloudflare (Free) for the domain, the tunnel and the sign-in.
docs/RECOMMENDED-STACK.md walks through it end to end, from ordering
the server to GitHub tokens and updates. Any Ubuntu 24.04 server works.

How big a server. Plan 6 GB of memory plus 3 GB per AI session running at once, 2 CPU threads
plus 1.5 per session, and 60 GB of disk plus about 3 GB per session plus the client's files:

Measured numbers, alternatives and the reasoning: choosing a server.

 Person ──► Cloudflare Access ──► Cloudflare Tunnel ──► client's server (no open web ports)
            who are you?          private connection    ├─ Operation Kit app
                                                        └─ one sandbox per AI job

Docs

Status

Built to be a solid self-hosted install: Cloudflare in front, no open web ports, sandboxed AI jobs,
encrypted secrets, a forced password change for the first admin, encrypted off-site backups with a
restore test, and automatic security updates for the operating system (Ubuntu's patches; Operation
Kit itself is updated by hand, see Updating). It is not an audited SaaS. Known gaps (no SOC 2, no built-in two-factor or SSO beyond Cloudflare Access,
transcripts not encrypted at rest) are listed in the security overview.

License

Apache-2.0, see LICENSE.