The weekly research, the recurring digest, the sweep nobody gets to, the ticket that has waited a quarter. Describe it once in plain English and a team of agents picks it up — product, architect, developer, QA — with an independent manager checking each step before the next one starts. The whole record lands in your git repository.
One workflow — the one that builds this platform — counted from the control plane's own records.
Every run the workflow made in that window — not a sample, not a pilot, not a case study we cannot show you. A person performed every merge. OpenSSF Scorecard 10/10, MIT licensed.
Five things that hold against every tool we get compared with.
Everywhere else, the agent that asked for the work also decides whether it was any good. Forge puts an independent management agent on each edge between roles: it can pass the work, send it back with specific rework instructions, or escalate to a person — before the next role builds on it.
Every run leaves a branch in your repository: the spec, the brief and each role's handoff as commits, authored by the persona. Readable with git log, months later, by someone who was not there.
No canvas, no nodes, no edges to keep in sync. Name the roles, say what done looks like, and the engine assembles the run — then keeps it working when the job changes.
Learn more → your keys, your metalSelf-hosted runners keep execution on your machines. Inference routes across a provider pool you control — priority weights, automatic failover, any OpenAI-compatible endpoint, including models you host yourself. Agents never hold your keys.
Research that verifies its own sources, a recurring digest, a content desk, an ops rotation. Same roles, same review loop, same audit trail — software delivery is one archetype, not the product.
Learn more →Each page quotes the other product in its own words, then names the thing it does not do.
An assistant speeds up a person who is sitting there waiting for the answer — so the work is bounded by their time. Forge takes the brief and does the work when nobody is there.
Perfect for a question you can answer in one sitting. You hold the thread, you steer every step, and the session ends when you close the tab.
AsynchronousBrief it the way you would brief someone who works for you, then close the laptop. It reads twenty sources, sweeps your telemetry, or takes a ticket to a pull request — on a schedule or right now — and it is still working during your commute. When you come back you get two things: the finished work, and a full account of how it was done — every step, every decision, every dead end.
The question isn't which model is smarter. It's whether you have to be present while the work happens — or can delegate it and read the report.
A team of agents runs the job. A supervisor reads every handoff and decides whether the next step gets it — so weak work stops instead of travelling.
Ours and our partners'. Each one with the evidence behind it.
A researcher gathers sources; a separate analyst re-opens each one and confirms the quote. On a live run: 18 gathered, 11 verified by direct fetch, 2 figures shipped marked unverifiable rather than passed off.
Pinned sources checked on a schedule, filtered by an analyst, posted to your channel. The publication that quietly costs an analyst-day a week — running without one.
Agents read your metrics and logs, correlate findings to the responsible code, and file a deduplicated issue — or a fix PR a human still merges. Credentials never enter the model.
Five roles with a supervisor between them take a ticket to a PR a human merges. We know it works because it is how Forge builds itself — every run leaves its branch, handoffs and verdicts behind.
The parts you meet in week two, once the first run is behind you.
A role is a named character with a voice, a tool policy of its own and a memory that outlives the run. The reviewer who caught a regression last month still knows what to look for this month.
Cron, a GitHub issue, a chat message, an inbound webhook. The run dispatches without you and asks for a person only when the supervisor escalates.
Secrets are bound to the roles that need them and injected at call time — never pasted into a prompt. Every outbound model call is logged with its provider, model and destination.
Run the agents on your own machines — a spare workstation, a rack, a private cloud — against the managed control plane, or host the whole thing. The toolchain is MIT-licensed and the runners are yours.
Describe your workflow in plain English. Forge runs it — across SDLC, research, content, and ops.
A person reads it next and replies to the address you gave. Nothing is sent to you automatically — no confirmation mail, no list.
Nothing has been sent yet — this page has no inbox of its own. Send it as an email and a person reads it next.
Send it as an email