Topview Motion StudioGet a launch video for about $3, not thousands
Promoted
Linchpin
Open-source, self-hostable runtime for managed AI agents
37 followers
Open-source, self-hostable runtime for managed AI agents
37 followers
Linchpin is an open-source, self-hostable runtime for managed AI agents. Apache-2.0. One `docker compose up` and you get a full agent platform — REST + SSE API, per-session Docker sandbox, MCP tools, encrypted vaults. Bring any cloud model via OpenRouter, or local via Ollama.
Linchpin
Managed AI agents often feel like a black box, so a self-hostable runtime is a breath of fresh air for privacy-conscious teams. What’s the resource overhead like for running a single agent instance on a local server?
Linchpin
@rivra_dev
Thanks! Rough breakdown for a single agent instance:
* Runtime itself (Node + small Postgres for sessions/event log): ~500 MB idle
* Sandbox container per task: ~300 MB while a run is active, freed when idle
* Model calls go out to a provider, so no local GPU or inference RAM
I would love to hear your feedback once you try it out!
As a CS student who's been trying to self-host agent setups, the gap between 'here's a library' and 'here's a running platform' is genuinely painful. One thing I'm curious about is that how do you handle the agent going rogue inside the Docker sandbox? Like is there a kill switch or resource cap per session, or is that still on the roadmap?
Linchpin
@shwet_gaur
Honest answer, partial today, hardening on the roadmap. Worth being upfront because you'd feel this on day 1 of a self-host.
Today (v0.1):
- Manual kill via DELETE /v1/sessions/{id}, cancels the orchestrator and destroys the container.
- TTL reaper, set ttl_seconds at session create; expired sessions get terminated every 60s.
- Soft interrupt, a user.interrupt event stops the model loop between tool calls (doesn't kill the container).
- Network isolation, two Docker networks: linchpin-none (no egress) and linchpin-open.
What's missing is the actual resource caps:
- No CPU / memory / PID / disk limits on the sandbox container.
- No exec timeout, a shell command in the sandbox can run forever.
- No per-session iteration or token budget beyond TTL.
So today: trusted-environment self-host. A misbehaving agent can pin CPU or fill RAM until the host complains. The kill switch works, but only if you (or the TTL) pull it.
Sandbox hardening, cgroup caps, exec deadlines, a hard-kill interrupt, optional iteration budgets, is on the roadmap. Putting up a numbered release doc for it this week and linking it from the README so it's visible.
Good question, this is the gap a self-hoster hits first.
@nikhil_aourpally1 honestly appreciate the straight answer here a lot of makers would've just said 'roadmap' and left it vague. the TTL reaper + manual DELETE is workable for a trusted environment, but yeah the no CPU/memory caps thing is exactly what I was nervous about. good to know it's a known gap and not a blind spot. will keep an eye on the release doc, this is still one of the more serious self-host agent setups I've seen
Linchpin
@shwet_gaur Please feel free to create a pull request if you feel something is missing.