Support denn-gubsky's open source work# About loomcycle

The Agentic OS, in a sidecar. loomcycle is one ~30 MB Go binary that
runs alongside your application — not inside it. The agent loop,
multi-provider routing, memory and channel primitives, MCP on both sides,
OpenTelemetry, and multi-replica HA all live in the binary. Your
application stays in whatever language you wrote it in.

loomcycle.dev · GitHub
· Engineering blog

What sponsorships fund

v1.0 shipped in 2026-05 with multi-replica HA, the substrate trio
(AgentDef / SkillDef / MCPServerDef), an OpenAI-compatible gateway, MCP
on both sides of the protocol, and an n8n community-node package. The
runtime is stable; the next year is about hardening the operator
surface and growing the community.

Sponsorships directly fund:

• Maintenance — security disclosure pipeline, regression testing
  across the six provider drivers, MCP spec tracking, n8n / LangChain
  ecosystem compatibility as those moving targets evolve.
• Operator surface — Helm chart, settings UI completion, cookbook
  of postures (sandbox vs dev vs production multi-replica), Postgres
  migration runbooks, the docs that turn "I read the README" into "I
  shipped it to production."
• Sustained engineering time — the per-tier work to keep the
  binary small, the substrate stable, and the wire surfaces honest.

The commitment

loomcycle is Apache-2.0 and stays that way. There is no managed cloud
requirement; the OSS runs standalone on a single VPS or multi-replica
cluster, indefinitely. No license change, no fork-paid-tier that
cripples the OSS, no SDK-coupling. Sponsorships are how the work gets
funded — they are not a precondition for using it.

If loomcycle is useful to you or your team, monthly sponsorship at any
tier helps it stay healthy and growing. Companies depending on it in
production are especially welcome at the higher tiers; the engagement
benefits there (priority issue triage, office hours) are designed to be
worth the line item.

— Dennis (Romania-based; primary maintainer of loomcycle and the team
behind JobEmber, which uses loomcycle as its
runtime substrate)