Skip to content
ride.dev
Help centerNorthStarFleetMobile docs
Log in
← Help center

Engineering & Platform

System architecture, posture reports, and in-flight design proposals.

  • Schedule Templates — ProposalDesign proposal for saving a successful van route and repeating it on a schedule, with the five-level fallback and the decisions still open. Restricted
  • People & Identity PostureWho the system knows and how it knows them — the two-layer auth model and the RBAC phase timeline. Sign in
  • Trip Management PostureHow a trip flows through seven codebases from booking to billing — status lifecycle and integrations. Sign in
  • MEF & Eligibility PostureHow a Medicaid Eligibility Form submission moves from intake through automated checks to an authorized trip. Sign in
  • Funding Source PostureBilling architecture and the data gaps blocking invoicing despite finished code. Sign in
  • Architecture PostureCost, security, CI/CD, and compliance posture across the estate. Sign in
  • Estate Dependency AtlasDependency inventory, vulnerability counts, and version skew across all six repos. Sign in
  • Access & Identity ReferenceCognito auth architecture — roles, permission tokens, cookie/session mechanics, and enforcement layers. Sign in
  • Access & Identity HandoffRBAC rollout status across the five identity surfaces, and what's left before enforcement. Sign in
  • The Authorization GapWhy most live trips have no authorization record, and the two remediation tracks under consideration. Sign in
  • Trip Operations Domain MapVisual domain model and lifecycle for the entities behind trip scheduling. Sign in
  • Admin Panel LayoutHow every /admin list page is built — components, conventions, and a surface-by-surface audit. Sign in
  • Pulsar Trip Management SpecExtending the Vapi voice assistant's trip tools — current gaps and the new capabilities planned. Sign in
  • MEF Voice Agent Policy Decisions46 policy questions from QA testing of the MEF voice agent, with recommendations and a priority matrix. Sign in
  • Verizon HOS RemediationSix defects in the Hours-of-Service data pipeline, five fixed and verified, one still open. Sign in
  • Reporting Engine OverviewArchitecture of the self-serve reporting platform — three data sources, marts, and governance. Sign in
  • Persistence CI — What We Changed and What It MeasuredHow the persistence integration-test CI run went from ~30 minutes to ~15, and what didn't work. Sign in
  • Dev API Gateway Setup LedgerUnblocking the orchestrator's OAuth2 API client system — IAM grants, Cognito branding, and a real bug fixed. Sign in
  • AWS Platform Stack RenameMigrating CloudFormation stacks from legacy names to the ride-* naming convention, dev through prod. Sign in
  • Alerting Review — API Gateway IncidentPostmortem of an API Gateway quota exhaustion incident and the alerting gaps it exposed. Sign in
  • Mobile Testing SetupTesting ride-mobile across all four roles — account creation, endpoints, and role readiness status. Sign in
ride.dev

Non-emergency medical transportation, run on one record.

Colorado, USA · est. 2026

© 2026 ride.dev · All rights reserved

Portals

  • Admin portal↗
  • School portal↗
  • MedRide↗

Legal

  • Privacy Policy↗
  • Cookie Policy
  • Accessibility Statement↗
  • Terms & Conditions↗
  • Help center

Platform

  • NorthStar
  • Intake
  • Fleet
  • Reporting