Basemate
Sign in

Basemate

Ride coordination built for commands — not another group chat.

A reliable ride to work every day keeps your people on time for muster and mission readiness.

Not every sailor in your command has a vehicle — and Uber and Lyft do not operate on a military installation. Basemate is the command-scoped ride board for that gap: drivers post the mornings they're already heading down, riders claim open seats with fixed pickup labels, and both sides get confirmed matches with status updates instead of group-text guesswork.

Sponsors enroll the command once. Members register with an invite-only join code in the browser — no app install, no cross-command board, and no duty-day maps. Flexibility when schedules shift, reliability when a seat is confirmed, and accountability from the moment a driver posts to the moment a rider gets picked up.

Flexibility · Reliability · Accountability

Sponsor-led onboarding — reach out to enroll, not self-service.

Get in touch

  • Limited parking at the boat

    Share rides command-wide so fewer cars fight for pier parking and everyone still makes muster on time.

  • Rides where sailors already go

    Drivers post the duty mornings they're heading down. Riders match seats going the same direction — no empty runs.

  • Empowering teamwork

    Drivers and riders stay accountable through confirmed matches, live status updates, and backup when plans change.

Select a Feature

What's happening

Coordinate the run — never reconstruct who was where, when.

Foundation · 1 of 4

01 · Foundation02 · Duty-day03 · Scope04 · Safe Ride

Foundation

The defining rule

Coordinate the run — never reconstruct who was where, when.

  • Basemate gets people to lower base on time — not a system that tracks unit movements.
  • OPSEC doctrine: small, unclassified details add up into one picture — an indicator.
  • Screenshots and subpoenaed exports must never reveal schedules or live locations.
  • A leaked group-chat image should never become a movement timeline for your command.
  • Every rule below exists to block that aggregation — not for arbitrary caution.

Why we built it this way

  • Every feature is checked against this rule before it ships.
  • Safe defaults beat hoping someone configures things correctly after rollout.

Command Advantage

Basemate bakes OPSEC into the product — least privilege, data minimization, Zero Trust scoping — so you can champion coordination without accidentally building fleet-wide movement tracking.

  • Duty-day rides use named pickup points and status text — never maps or GPS, the same leak vector as consumer fitness-app location sharing
  • Invite codes, RLS, and minimal disclosure are defaults — not settings to misconfigure
  • Safe Ride is the only mapped exception, off-base only, with location data purged after pickup

How it works

Basemate is OPSEC-first by design: fixed pickup labels and status text on duty-day rides, command-scoped data with invite-only access, sponsor metrics without positions — least privilege and data minimization applied throughout, with Safe Ride as the only narrow, temporary mapped exception off base.

Results

  • Duty-day rides coordinate without maps, pins, or tracking links
  • Every ride table scoped by command — no cross-command leakage
  • Sponsors see adoption trends, not a live map of where people are
  • Safe Ride maps purge when the ride ends — the exception stays narrow