Pricing
Free to start. $29 a month, flat. No credits.
One price, two limits: how many products Forge watches for you, and how many rows a day each may send. Nothing inside is metered. Oversight is on every plan; only the model’s spec draft is paid. Free includes 1 product, 20,000 rows a day · kept 30 days and its first 2 briefs.
Forge Free
$0no card
1 product · 20,000 rows a day · kept 30 days · 2 briefs · the alerts keep running
Get the answer before you pay for anything.
- —Oversight of your app: its events, logs and errors counted, an issue opened when a count moves past a stated threshold, the decision, the release and its outcome
- —1 product, up to 12 companies watched each
- —20,000 rows a day per product — events, errors and logs — counted exactly, kept 30 days
- —2 briefs per product — enough for the market-fit number
- —Same-day alerts when a service your app rests on breaks, retires or reprices something
- —The market map, the market sizes and what changes under your app — public, read once for everyone
Forge Solo
$29/ month, flat
3 products · 100,000 rows a day each · kept 90 days · 12 companies watched · nothing metered
The co-founder your agent cannot be.
- —Oversight of your app: its events, logs and errors counted, an issue opened when a count moves past a stated threshold, the decision, the release and its outcome
- —The model’s draft of a work spec from an issue’s evidence, every number it states checked against the counts
- —3 products, up to 12 companies watched each
- —100,000 rows a day per product — events, errors and logs — counted exactly, kept 90 days
- —A brief every week, or every two or four — your choice
- —Same-day alerts when a service your app rests on breaks, retires or reprices something
- —Every spec as Markdown for your coding agent — Forge writes nothing to your repository
- —A brainstorm that argues from the same reading — included
- —The MCP connector, so your coding agent starts from the brief
- —A read you start by hand, once a day per product, on top of the schedule
Building with a team? Team is $69 a month flat for the whole workspace — no seats, 10 products shared, nothing metered — for the first 100 workspaces, $99 after. Premium adds the org layer: talk to us.
Why there are no credits
A meter on a weekly read switches the read off. We tried it.
Nothing runs out mid-week.
The market-fit number needs 2 briefs. A balance that ends after the first pauses your product the week before the number arrives — where every product on the old meter ended. A plan's two limits — how many products it watches, how many rows a day each may send — cannot be reached by waiting, and a day past the rows is a day said to be incomplete, never a bill.
What you pay for never stops.
The weekly brief, the daily check of the services under your app and the alerts run on their own schedule. A meter makes you switch a read off to save money, and a read switched off is a gap in the record.
No arithmetic before a question.
The tracking, the issues, the outcomes, the brief, the brainstorm, the alerts and the MCP connector are in the price. No top-up, no balance in the sidebar. One number on the invoice, and it is the one on this page.
Before you pay
The questions builders ask first.
Where the honest answer is “it cannot see that”, the answer says so.
- What does free include, and why are there no credits?
- 1 product, no card: oversight of its app — the tracking, the issues, the decisions, the releases and their outcomes — its first 2 briefs, the ones the market-fit number needs, and same-day alerts for the services your app rests on, which keep running after. Oversight is on every plan; the one thing paid adds to it is the model’s draft of a work spec. No credits, because a balance ran out at the worst moment: every product on the old meter ended paused the week before its number. Solo is $29 a month flat for 3 products, 100,000 rows a day and 12 companies watched each.
- What does my app send Forge, and what do my users’ data look like inside it?
- Your app sends events (a name, such as a sign-up completed), error logs (name, message, stack and the page) and logs (a level and a message), each with the person and session ids your app chose, from the snippet in the product’s Settings or the npm package. Before a row is stored, its texts are scrubbed — e-mail and IP addresses, long digit runs and anything shaped like a secret are replaced, a web address keeps its path and loses its query string — and the request’s IP address is never read. The person and session ids are hashed together with the product’s id, so the stored value cannot be turned back into yours and the same person is a different value in every product. Each product’s rows live in a store of their own and are deleted after the plan’s days (30 days on Free, 90 on Solo, 180 on Team and 365 on Premium); the counts, issues and outcomes derived from them stay with the product. No surface shows a person, lists the people behind a count, or ranks them. The privacy policy’s “Your users’ data” says the same in full.
- What happens when I reach my plan’s limit?
- A plan has two limits — how many products Forge watches for you, and how many rows a day each may send: 20,000 on Free, 100,000 on Solo, 100,000 on Team, 35,000 on Premium — and the product says so in the plan’s own sentence when you reach either. The rows are kept 30 days on Free, 90 on Solo, 180 on Team and 365 on Premium; the daily counts the issues and outcomes rest on are kept a year on every plan. Nothing is paused and nothing inside a product is metered: the tracking, the issues, the outcomes, the brief, the brainstorm and the alerts keep running for every product already on the plan. Past the day’s rows a store refuses the rest, counts the refusal and withholds any comparison over that day — it never bills you for them. Two rails on the model calls a person starts are not a meter either: a spec is drafted at most once an hour per issue, and a workspace takes 40 brainstorm turns a day.
- Is there a plan for a team?
- Team is $69 a month flat for the whole workspace — no seats, 10 products shared, nothing metered — for the first 100 workspaces, $99 after. Premium adds the org layer with 30 products; write to hello@ambera.app.
- Will the price change with usage?
- No. Monthly is the only price any purchase surface shows, and the one on the invoice is the one on this page. There is no top-up and no balance in the sidebar. A read you start by hand, once a day per product on a paid plan, is in the price too. An app that outgrows its plan’s rows a day is told so on the day, and moves up a plan when you say so — never by an invoice.
- How does Forge know what my product is, and does it read my code?
- It reads what you already publish about the product: its website and, if a repository is linked, its README. A model writes a few sentences from those, each naming the source it came from, labelled as Forge’s reading and read again only when the website or README changes. You can add a correction in your own words, and Forge carries it beside the reading; when nothing could be read, your own description is used and the page says so. Forge does not read your code to say what your product is: from a connected repository it reads the manifests, for the services your app rests on, and the README.
Start free
Bring the hammer. The smithy is lit.
Google, GitHub or an email. 1 product free, no card, no credits: add the snippet to your app, and the counts start with its first row.