Ambera
Ambera Forge · for engineering teams

Estimates that account for the person doing the work.

A story point isn’t the same size for everyone. Ambera Forge sizes effort to each engineer, tracks per-person velocity, and holds a QA reserve so the sprint has room to breathe — then flags over-commitment early, while there’s still time to rebalance the load. Your team commits to what will actually ship.

AMB-412

Migrate auth to the new session service

5 pts· for Dana
Confidence band4–7 pts

3 pts

Team baseline

+15%

QA reserve

82%

Sprint load

How it fits

Sits on top of your tracker.

Forge doesn’t replace your tracker — it works alongside it. Linear is live today, Jira is on the way. Your team keeps planning where it already does; Forge adds a layer of estimation that knows who’s doing the work.

Estimate personalization

The same ticket, sized to who picks it up.

A senior who owns the service and someone seeing it for the first time don’t carry the same cost. Forge sizes the estimate — and its confidence band — to whoever the work lands on.

AMB-412

Migrate auth to the new session service

DK

Dana

owns the service

5 pts
4–6 pts
SR

Sam

first week on it

9 pts
7–12 pts

Same ticket. The estimate follows the person who picks it up.

Per-person velocity

Velocity that reflects reality, not a blended average.

Velocity stops being a single team number. Forge learns how each engineer actually closes points over time, so the plan is built on how the team really moves.

Per-person velocity

last 30 days

DK
Dana8.4 pts/day
PR
Priya6.7 pts/day
SR
Sam5.1 pts/day

A single team average would’ve hidden every one of these.

Sprint QA reserve

Room for QA and the unplanned, held back up front.

Every sprint keeps a slice of capacity for testing, review, and the things you can’t see coming — visible from day one instead of discovered on the last.

Sprint 24 · capacity

120 pts

68%

Committed

15%

QA reserve

17%

Open

The reserve is set aside on day one — not discovered on the last.

Over-commitment, caught early

Flagged while there’s still time to rebalance.

When a plan runs past what the team can sustainably carry, Forge surfaces it early — with enough runway to move work and protect the delivery date.

Sprint 25 · load

118%
CommittedSustainable pace

12 pts past sustainable pace

Flagged on day 2 — still time to move work or extend the window.

The Ambera app pulls your tracker into a personal energy ledger. Forge is the other direction — it sits on the tracker your team already uses and makes its estimates personal. Same idea, team scale.

The privacy membrane

Your energy stays yours.

Forge personalizes estimates without ever handing your energy data to your team. Each person’s ledger lives in their own Ambera account. The organization sees the estimate — never the reason behind it.

Stays private to each person

  • The energy ledger and how a day felt
  • Why an estimate moved up or down
  • Recovery, depletion, and check-in history
Membrane

What the org ever sees

  • De-identified story-point estimates
  • Confidence bands on each estimate
  • Sprint capacity and reserve, in aggregate

This is enforced structurally, not just promised in a policy. The energy data never crosses into the org’s side of the membrane, so there’s nothing on that side to leak or subpoena.

Proof over promises

Estimates you can stand behind in planning.

No borrowed benchmarks, no confidence you can’t see, no data leaving your team. The trust is built into how it works — here’s where it comes from.

Grounded in your own history

Estimates come from how your team has actually closed work — not a vendor benchmark or an industry average. The longer you use it, the sharper it gets.

Confidence bands, not false precision

Every estimate carries its own uncertainty. When the history is thin the band stays wide and says so — Forge never pretends to know more than the data supports.

Privacy enforced in code

The membrane is structural, not a line in a policy. Personal energy data never crosses to the org’s side — so there’s nothing there to leak, sell, or subpoena.

A free tier that’s a real product

Bring your whole team onto the board and judge the estimates against your own sprints before a single seat is paid. No trial clock on the core loop.

See it on your own board first.

Forge is young, and we’d rather earn a handful of teams than chase everyone. Connect Linear, pull in a real sprint, and see whether the estimates hold up against how your team actually ships. If they do, we’d love to build the rest with you.

Design partners get a direct line to the founder, a say in what ships next, and Forge free while we build together.

Pricing

One plan, priced per seat.

Start free, then add Forge Pro per active seat. Billing is on the web through Stripe — no app store cut, no per-feature gates.

Forge Pro

$12/ seat / month

or $120 / seat / year — 2 months free

Estimation that knows who’s doing the work.

14-day free trial
  • Personalized, per-engineer story-point estimates with confidence bands
  • Per-person velocity that learns from how work actually closes
  • Over-commitment caught early, with a reserve held back for QA and the unplanned
  • AI assists tuned to your team’s calibration history
  • Team calibration depth that sharpens as you log

A free tier is always available — try Forge with your team before adding seats.

Plan for the people, not the average.

Bring Ambera Forge to your team’s tracker and start estimating with the person in the picture. Free to try, no app store required.