Baseball Lab

How it works

Two sides,
never joined

A coach gets planning tools that work from a roster. A player gets a place to learn the game. The two halves share a team code and nothing else — by design, and enforced by the shape of the database rather than by a policy.

The coach side

Your roster, your pitching records, your lineups. Names are optional — jersey numbers alone work everywhere, including printed cards. Everything here belongs to your account and no other coach can read it.

The player side

A device joins a team with a share code. It gets an anonymous token and, optionally, a jersey number. No name, no email, no account. Nothing on this side can see a roster.

There is no column in the database linking a device to a roster entry, and there is no table that could carry one. If a feature ever appears to need that link, the feature gets redesigned. The full detail is on the privacy page.

Getting started

  1. A coach creates an account from an invite, then a team.

  2. They add players — pasting a list from a team email takes about a minute.

  3. Outings get logged as they happen, including ones thrown for other teams.

  4. The planner answers "who can pitch Thursday?" from the actual rules, not a guess.