About Forgeborn
Software forged by humans and AI
The Story
Forgeborn started with a simple idea: what if a solo developer could build at the speed of an entire team? Not by working longer hours, but by building smarter — with AI agents that actually write code, run tests, and ship features autonomously.
That idea became ForgeTeam — a multi-agent orchestration system where specialized AI agents (Planner, Developer, Tester, Evaluator) work together on real projects. Each agent has its own role, its own tools, and its own persistent memory. A Manager agent breaks down goals into tasks, dispatches work, and evaluates results — all without human intervention.
The infrastructure runs on Claudinator, a self-hosted Proxmox cluster with dedicated VMs per project. Every product you see on this site was built — or is being built — by this system. One developer. Multiple AI agents. Real software, shipping continuously.
The Philosophy
We build tools that solve real problems. Not pitch-deck products — working software that does what it says on the tin. Every project in the Forgeborn catalog exists because someone needed it, and nothing else did the job right.
Self-hosted wherever possible. Open source where it makes sense. No vendor lock-in, no subscription traps, no data leaving your network unless you want it to. Your infrastructure, your rules.
AI is a tool, not a gimmick. We use it to write code, review security, generate documentation, and run tests — because it genuinely makes the software better and ships it faster. If AI doesn't add real value to a workflow, we don't use it there.
The Stack
Technologies we use across Forgeborn projects.
Infrastructure
Everything runs on a self-hosted Proxmox cluster — dedicated VMs per project, isolated environments, full control. No cloud providers in the critical path. Deployments go from git push to live in minutes via systemd services behind nginx reverse proxies.
ForgeTeam agents run concurrently across projects, each with MCP access to a shared persistent database for tasks, decisions, and session notes. The orchestrator handles priority scoring, resource allocation, and automatic dispatch — scanning for pending work and spinning up Dev+Test loops without manual intervention.