For Conferences & Leagues
Conference media on one account. Member schools as users, not as charges. Names embed in the file.
Start Free →The hidden multiplier
Most billing models scale with the league. Ours scales with the storage. Big difference.
Structural parallel
Same workflow. Same product. The scope is bigger.
Upload rosters for the teams the conference covers. Photographers upload galleries. MatchID runs against the league's combined roster pool. Names embed in the file. Distribute through shared galleries, FTP, downloads, and named files to media partners. The mechanics are identical to a single athletic department's. The scope is what changes.
Built for the league
Three ways member schools access the conference archive. All on the same bill.
Cross-team naming
A conference photographer covers a league game. The cover photo has athletes from both schools, named.
Most platforms scope identification to one team at a time. That works for a single athletic department. It doesn't work for the conference covering both teams in a league game.
Because the conference uploads rosters for the teams it covers, MatchID searches across all of them. The home QB. The visiting linebacker. The home libero. The visiting setter. All named in the same gallery, from the same upload. The schools downstream get named files of their own athletes. The conference does nothing extra.
Media Day to championship Sunday
The conference's photo year, on one bill.
What we don't charge for
Conference pricing
Starts at 2 TB. No per-member-school fees. Volume pricing kicks in at 5 TB for conferences running large archives.
Cover the league. Bill once.
Start Free →Common questions
It's essentially the same product, scaled to the league. The conference account holds the archive, uploads rosters for the teams you cover, and runs MatchID. Member schools can be added as users on your account so they have direct access to the photos, or you share with them via gallery links, FTP, and downloads. Schools that want their own branded system can run their own GalleryID account, separately.
Yes. Add each member school as a user on the conference account and they get direct access to the photos and galleries you grant them. That's the simplest setup: schools log in, see what they need, download or share. Schools that prefer to manage their own archive can run a separate GalleryID account, and you share with them through gallery links, FTP, or download. Photos aren't linked across separate client accounts.
Upload rosters for the teams your conference covers. When a conference photographer covers a game between two member teams, MatchID names athletes on both teams against the rosters you've uploaded. Same workflow any athletic department uses, scaled to whichever teams play in your league.
AthleteID belongs to the school that owns the relationship with the individual athlete. Conferences hand named photos to member schools — via direct user access, gallery shares, FTP, or download — and schools that run their own GalleryID account use AthleteID to push that content to their athletes under the school's branding. The conference doesn't manage athlete-facing distribution directly.
Storage-based, scaled for the conference. Starts at $160/mo for 2 TB. No per-member-school fees. Add storage as the archive grows. Pricing covers the conference account; member schools that want their own GalleryID accounts run those separately. Volume pricing kicks in at 5 TB for conferences with larger archives.
Yes. Built-in download store with per-photo or per-gallery pricing and 0% commission. Set prices for championship galleries, media buys direct, proceeds go to the conference or to member schools depending on how you scope the gallery.