The whole platform.
Open source. All of it.
No closed core. No enterprise gate. The knowledge pipeline, the tool registry, the agent runtime, the chatbot widget — every line is on GitHub under MIT. Use the hosted product for convenience, or run it yourself. Your choice, always.
The platform monorepo
Everything that makes Forge work. Knowledge ingestion, embedding pipeline, tool registry, agent orchestration, multi-agent handoffs, and the embeddable chat widget — all in one repo, all under MIT. The hosted product is this repo, deployed. Nothing more.
Packages — each one earns its place.
Each package is independently useful. Pull one into your own stack, or use them all together through the hosted platform.
Ingestion pipeline. Chunk documents, generate embeddings, and store them in a vector index ready for semantic retrieval.
Data source adapters — Amazon S3, SharePoint, and local file upload. Syncs on a schedule and keeps the index fresh.
Tool builder and registry. Define any REST API as an agent tool with a name, description, and parameter schema.
Agent runtime. Routes queries through the knowledge layer and tool calls, manages multi-agent handoffs, enforces step limits.
MCP server support. Plug any MCP-compatible tool or server directly into an agent — no adapter code needed.
Embeddable chatbot UI. One script tag, streaming responses, source citations, and tool-call indicators out of the box.
The commitments we're making.
Open source isn't a marketing move. It's a constraint we're choosing so you never have to trust us blindly.
→ No closed core
Everything that ships, ships under MIT. There is no "enterprise edition" with the good parts locked away. What you see on GitHub is what powers the product.
→ Transparent build
Commits, issues, and roadmap decisions happen in public. If we change direction, you can read why in the issue thread, not in a changelog months later.
→ Replaceable parts
Each package is independently useful. You should be able to take the knowledge ingestion layer and use it without the rest. No forced coupling to the hosted platform.
→ Your data, your repo
Self-hosting is a first-class path, not an afterthought. The hosted product is convenience — the open-source repo is the escape hatch if you ever need it.
Build this with us.
Forge will be built in the open, commit by commit. The repo goes public at launch — when it does, the most useful thing you can do won't be submitting PRs. It'll be using it on a real problem and telling us what breaks.