Vantage

Overview

Vantage is the operations platform described in the public repository as one login for the work an FRC team already does. The source is public. The license is PolyForm Noncommercial 1.0.0. The project calls that source-available rather than OSI open source, because the license reserves selling it. Teams, schools, students, and anyone learning from the code may read it, run it, change it, and self-host it when the use is noncommercial.

The README says the project is in active development and used by its author's team.

Problem

The repository describes a season that usually lives in spreadsheets, group chats, shared drives, and paper scouting forms. Vantage is the attempt to put that in one place that already knows the FRC season, and to teach new members on the way in.

What he built

The web app is Next.js in apps/web, deployed on Vercel. The hosted database is PostgreSQL on Neon. Tenancy is row-level security, and the schema is a numbered series of append-only SQL migrations. apps/desktop is an Electron shell with Windows and macOS builds. Optional hardware — a storage node, a Raspberry Pi relay for AI, and a Fusion 360 relay — pairs to a team with a code and is not exposed to the internet.

Signed in, the README lists a home dashboard the team can arrange, four workspaces, and Ask AI on every page:

• Competition — event-day command, schedule and rankings, scouting that works offline, match prediction and strategy, alliance selection, a pit checklist, and repair triage.
• Team — calendar, chat, people and attendance, shop hours, tasks, the playbook, and files.
• Build — kickoff planning, CAD through Onshape and Fusion 360, robot code, readiness, inspection, and batteries.
• Business — budget and purchases, sponsors, grants, outreach hours, and awards.

Ask AI is documented as a helper that answers from the team's own data and public event data, shows what it read, and can run on hardware the team owns before a paid key is involved. Schedules, results, and rankings come from The Blue Alliance and Statbotics through one shared cache.

An empty screen says what is missing instead of inventing a number.

The same README states a few product rules: pages keep a last snapshot when venue Wi-Fi drops; a team's rows can be exported. A package note in that README also says access is closed to provisioned owners and invited emails, with a waitlist for everyone else. Both statements are in the public docs; this page does not collapse them into a simpler claim.

Host	Where it is named
vantagefrc.vercel.app	docs/STATUS.md, called production
vantagefrc-scouting.vercel.app	docs/STATUS.md, scouting
vantage-frc-web.vercel.app	README hosted link

Both app hosts responded when this page was written. The scouting host redirects to a sign-in screen.

Process

The repo is a monorepo (apps/*, packages/*). Each core package README states what that package owns and what it refuses to do. The map of the system is docs/ARCHITECTURE.md. The screen list is docs/FEATURE_MAP.md. Self-hosting, for a team that wants its own Postgres and Vercel project, is docs/SELF_HOSTING.md.

apps/web        Next.js, deployed on Vercel
apps/desktop    Electron shell, Windows and macOS
packages/*      product queries go through withRls
                prediction skips rather than guessing a game action
                modelling stays in Onshape

Those boundaries are the ones named in the top-level README.