Live
Anatomy of a fall.
It does everything, all at once, and none of it is simple.
None of it fits the way you work, and every module is billed.
So the real work moves to spreadsheets next door.
It tinkers to catch up: custom patches, nailed on wherever it hurts.
Then every upgrade is a building site, and the patches do not survive it.
It goes generic, and every need becomes a gas factory.
It plugs into twenty thousand services, give or take.
Everyone else has AI. Here, half of it is plugged in, and that half misfires.
And once you are in, you are fenced in: your data has no way out.
Every question it cannot answer becomes one more ticket on the pile.
Until the whole thing blows.
Forge your
internal tools.
Pick a ready-made tool. Shape it to your team with AI. Ship it to your people and your agents.
npx forgeron initGet started- Forging at
Pick. Shape.
Ship.
From a tool that already works to a tool that fits your team, live for your people and your agents.
Start from a tool that already works.
A CRM, a help desk, a notes app: browse finished tools and install one.
- Installed in one click
- Kept up to date by its maintainers
- Yours to fork
- CRMCompanies, contacts, dealsInstall
- Data hubImports and syncsInstall
- DashboardSales at a glanceInstall
- Help deskRequests, answersSoon
- TicketingBoards and issuesSoon
- NotesPages for the teamSoon
Make it fit your team, with AI.
Pick a recipe, or ask for your own. Recipes and plugins hand the AI tested code and the method to add it.
- A preview for every change
- Every change, a version
- Recipes: documents the AI follows
- RecipesSoon
- Add a field3 files
- RenewalsApply
- RECIPE.mdthe method
- schema/renewal.tsfield
- actions/renewals.tsaction
- views/renewals.tsxpage
- renewals.test.tstest
- Weekly digest4 files
- PluginsSoon
- Kanban board
- Email sync
- Odoo bridge
- Renewals
Out to your people and your agents.
One click, and the tool is live on the web, in the terminal, over the API and in Claude, behind your SSO.
- One click to production
- The same rights on every door
- Made for agents, not bolted on
For your peopleWebIts own interface, behind your SSO.For your agentsMCPClaude uses the tool, with each person's rights.CLIforgeron crm deals move, for coding agents and you.For your applicationsAPIAn endpoint per action, for your integrations.
One framework,
six layers.
What the platform stacks under every tool, so your change only touches what makes it yours.
- InterfacesWeb, CLI, MCP and API, from one definition.
- AccessCompany SSO, teams, permissions per action.
- ToolsVersioned on every push, previewed before production.
- ObservabilityCalls, time per call, errors and logs.
- DataTables, files, and one vault for secrets.
- RuntimeCloudflare Workers. Hosted by us or by you.
Everything
on tap.
A tool lists what it needs; the platform hands it over, one per tool and environment.
- Database
Its own SQL database, per environment.
- Files
Uploads and exports, with size and type limits.
- Cache
Keys it reads often, served fast.
- Secrets
The app's keys and each person's, in one vault.
- Queue
Work handed off and run in the background.
- Cron jobs
Runs on a schedule, in your time zone.
- Observability
What it does, how fast, for whom.
- Realtime
Channels, messages and presence, live.
Who did what,
with which rights.
Every door goes through the same gateway: sign-in, team check, audit log. None bypasses another.
Company SSO
Your teams sign in with the identity provider you already use.
Every call, measured
Calls, time per call, errors and logs, per tool, with no setup.
Audit log
Usage, deployments and every change, with who made them.
From your laptop
to everyone.
Try a tool locally, share it in a preview, publish it. In your terminal, or from Claude.
- 01Localforgeron dev runs the tool on your machine, with local data.
- 02PreviewEvery branch gets its own link, to share before it ships.
- 03ProductionA release goes live. forgeron rollback takes it back.
Our cloud,
or yours.
The same platform in every case. Only who runs it changes.
We run the platform for you, on our Cloudflare account.
- Updates applied for you
- Security patches applied for you
- Resources provisioned for you
- Priority support
- One bill for the workspace, per seat
The same platform, installed on your own Cloudflare account.
- Installed and updated with the forgeron CLI
- You provision resources and apply patches
- You see the Workers, databases and logs
- Your data stays in your account
- Support through GitHub
The platform on a machine or a VPS you run, without Cloudflare.
- No Cloudflare account needed
- The same tools and interfaces
- Less redundancy than Cloudflare's network
- Fewer usage features
The small
extras.
Usage per team
One unit for everything a tool runs: CPU, storage, crons. Heavy storage and light CPU even out, with no overage per resource. AI spend beside it (soon).
One AI gateway
Every model behind one entry, and who calls what.
One vault
Application secrets and each person's own keys, sealed together. Nobody reads them back.
Teams and permissions
Access given to teams, action by action, on every door at once.
Marketplaces
Add a GitHub repository of your team's tools as a private catalog.
Approval policies
A tool asking for a new resource waits for an admin; approved, it is plugged in.
Questions,
answered.
Q.01What is a tool?
A business application your team uses: a CRM, a help desk, a dashboard. Underneath, it is a folder of actions; Forgeron serves each one on the web, in the terminal, over the API and to Claude.
Q.02Can I change a tool I installed?
Yes. Fork it, ask the AI for what you need, try it in a preview, then ship it. Every change is a version you can roll back.
Q.03How do agents use my tools?
Over MCP, with the rights of the person they work for, or with a token. Every call goes through the same gateway and lands in the audit log.
Q.04Do I need servers?
No. Each tool runs as its own Cloudflare Worker, per environment, with its own database, files and cache.
Q.05Can I host it myself?
Yes. The same platform installs on your own Cloudflare account with the forgeron CLI. Or let us run it on Forgeron Cloud.
Q.06Is it open source?
Yes, under the Apache-2.0 license.
Forge your
first tool.
Pick it, shape it, ship it. Open source, Apache-2.0.
npx forgeron init