Agent workflows
The job runs on agents, not on an on-demand desktop. A human signs off before anything hits production.
Ontario corporation · US and Canada
The models, the router, and the gate stay on your side of the wall.
Companies that cannot put work through a public LLM still need agents. We put self-hosted models, a custom proxy/model-router, and a human gate before production. Train-the-trainer. Microsoft 365 Teams and tenant admin when the shop is regulated.
What you buy
AI-first workflows for teams that cannot put work through a public LLM. Staff off the on-demand desktop onto agents that run the actual job, with a human gate before production. Train-the-trainer.
Private models and router
Self-hosted models and a custom proxy/model-router on your side of the wall. Not a public LLM dump.
Microsoft 365 when regulated
Teams and tenant admin for shops that already run Microsoft 365 under audit, legal hold, and risk review.
Edge
Cloudflare on 80/443, then nginx, then the app. cloudflared tunnels. Tailscale or WireGuard so the box is not on the public internet. Same for APIs and webhooks. Workers, Pages, Docker, inbound parse, outbound mail are shipped. That is the edge, not an AI-gateway case study.
How change gets in
A feature request opens a work item. Work happens on a git worktree. Merge to main is a pull request. That is the gate. Overmind uses GitLab CE work items for jobs, incidents, and prod.
Work item
Nothing runs until a feature request is a work item.
Worktree
Work happens on a git worktree, not on main.
Pull request
Merge to main is a pull request. That is the gate.
Proof you can open
No client list. These are live.
- Overmind (sysadmin / webmaster / SRE on private GPUs) at openpurse.ca and openpurse.ca/cdn/brain
- Live: tkrpik.com
- Code: github.com/actviteai, omni-term-ai, lumenEh, trouble
Ontario corporation. We invoice the US and Canada.
Companies that cannot put work through a public LLM still need agents. The models, the router, and the approval gate stay on your side of the wall.
No Claw. No tkrswap. No client list. Consulting primer.
Start a conversation
Tell us about your constraints — data residency, latency, evaluation requirements, or legacy integration. We reply like operators, not sales bots, and usually respond in 2-3 business days.
The form uses a short security check when configured. If it does not load, use email or phone — we monitor both.