trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
small: a preview shows a forge in grace, so the forge's own looks picture the Plan line and the /forges row, and docs/features/plan-row.md shows them
7 of 7 done
0 open · 7 merged in 7 days · moved
Everything beneath it is done.
Limbs
Merged in 7 days
- A forge's billing moves active → grace → none → active as plain data, with grace and retention as settings
- A Stripe subscription or invoice event writes what Stripe says now, so events out of order cannot undo a payment
- POST /hooks/stripe answers a signed event once: 400 on a bad signature, 200 and nothing on a replay
4 more merged
- A Stripe signature is checked by one pure function: good, bad, stale and rotated secrets each have a test
- Stripe is connected by pasting one key: checkout and the customer portal run over fetch, with nothing to set up in Stripe's dashboard
- Billing is a seam with two providers, none and stripe; with none, every forge is free within its plan
- Plans are a setting: free, small, medium and large, each with a size, a monthly price, a monthly crew credit and a forge count
Issues
None open.