Two ways to buy
The shape is settled: a cohort has mentors, a team has a manager. What each tier is called and what it costs is not settled.
Cohorts — TBD
TBD
Tier name and price to be announced.
For a group of people working on their own projects with mentors checking their process. Each member's projects belong to the cohort's org, and mentors read the cohort's dashboard.
Whether cohorts are paid at all has not been ruled.
Teams — TBD
TBD
Tier name and price to be announced.
For a team whose manager watches progress. The team's org carries the subscription, members are added to it with roles, and projects are bound to the org.
What every plan includes
There is one product, so both scenarios get the same machinery:
- The plugin in your coding sessions: an estate per project, an honest ledger, every “done” gated on an exit code, each commit banked to the hub.
- The hub at portal.reach.rest, holding your estate's snapshots.
- The dashboard: an org overview in needs-attention order with a process headline and the last seven days of banks, and a project detail view with a 33-signal build lens.
- Sign-in by one-time email code, and a revocable 30-day machine token per device.
How buying will work
Signup and payment are not built on this site yet. When they are, a manager creating a team will pay by card through a payment provider and the team's org will be marked paid; a lapsed subscription will move it back to trial. Card details will never be held by us.
Until then, getting set up is done by hand: the house owner allows your email address, creates the org and the member record, and binds your project. The steps are on the how-it-works page. Get in touch if you want to be set up this way.