Nothing is for sale. The plugin is published and free; this page states what paid seats will cost when billing exists, so you can hold us to it.
Synchrobuilder 0.1.0 is published under the MIT license. Pricing is decided now so that nobody installs on one basis and pays on another.
0 USD, no time limit
Free means the code is the same. There will be no separate free build.
3 USD per person per month, billed yearly
There is no payment form on this site and there will not be one until billing exists.
| Who | Price | Status |
|---|---|---|
| Seats 1 to 3, any team | Free forever | available in 0.1.0 |
| Seat 4 and up | 3 USD per person per month, billed yearly | coming soon |
| Students and classroom teams | Free at any size | process undecided |
| Founding teams (first 50 paying) | Half off for life | coming soon |
Students and classroom teams: free at any size. How a team shows that it is a classroom is not decided yet. Nothing about it is written down in the plan, and we will not invent a process here. Until billing exists it needs no process at all, because nothing is enforced.
Founding teams: half off for life for the first 50 paying teams. "Paying" means the team pays for additional seats once billing exists. There is no list to join for this beyond the releases link above.
One isolated module, one non-blocking note, nothing disabled.
v1 has no payments, no license enforcement and no accounts. The plugin has no way to know who is paying and no server to ask.
The only seat-related behaviour is a count. /synchrobuilder:status counts distinct active handles over the last 30 days from the team state the plugin keeps locally anyway. A handle is the identity Synchrobuilder derives from your git email through the committed .synchrobuilder/team.json file. When that count is more than three, status shows a non-blocking note once a week pointing at this page. That is the whole mechanism.
The logic is one isolated file, plugins/synchrobuilder/lib/features/seats.mjs, so you can read it in one sitting and confirm it does nothing else. Its test asserts that the notice appears once per week only when more than three handles were active in 30 days.
/synchrobuilder:status when the count is above three.lib/features/seats.mjs and nowhere else.Every claim in this section is implemented and covered by the seats test; docs/commands.md documents the status entry.
Short answers with the document each comes from.
No. There is no sign-up, no password and no token. Your identity is a handle: your git config user.email is matched against the .synchrobuilder/team.json file committed in the repo. If your email is not listed you get a provisional handle derived from it and keep working. /synchrobuilder:iam overrides the handle for one checkout on one machine. See How it works and ADR-002.
No. Team state travels over the git remote you already have. Each developer and device publishes one small ref of its own; nothing is merged and nothing is hosted. A team that can push to its remote can use it. See ADR-001 and the Security page.
A seat is a distinct handle that was active in the last 30 days; that is all the plugin counts (ADR-002). The details may change, and they will be documented on this page before any billing exists.
There is nothing to host. The plugin is designed to run on each developer's laptop and talk to your git remote. A hosted hub is out of scope for v1. ADR-001 keeps the transport interface open for one later and docs/hub-api.md sketches it, but none of it is implemented or priced.
npx synchrobuilder@latest install, or the two /plugin commands on the Install page. The plugin is on npm and the marketplace is in the public repository.