Drais is being built as a complete bike‑management companion: one place for your bikes, parts, maintenance, routes, rides, service history, and cycling decisions. The first near-term roadmap priority is partner integrations, followed by the product areas below.
Before expanding the wider roadmap, Drais is prioritizing partner integrations that make ride and ownership data flow into the garage with less manual work. We are not naming partners publicly yet, but the goal is clear: connect trusted external activity and service sources to the bike record in Drais.
Bring external ride activity into Drais so bike mileage, component wear, and service timing stay current.
Partner integrations should respect permissions, keep the rider in control, and avoid duplicate bookkeeping.
Where partners can add maintenance or service context, Drais should turn that into useful bike history.
Specific partners will be announced only when access, behavior, and rider value are confirmed.
We plan to bring route creation directly into Drais, with presets that match how cyclists actually ride. Riders will be able to start from practical defaults for gravel, MTB, road, and commute routes, then adapt the route around their bike, terrain, time, and riding style.
Plan mixed‑surface rides with distance, surface, elevation, and exploration in mind.
Build off‑road routes that respect trail character, effort, and technical riding needs.
Create efficient road rides for training, endurance, group rides, and fast local loops.
Plan repeatable everyday routes where reliability, safety, and time matter most.
Drais should make good routes easier to discover, save, and share. We plan to add an in‑app route library where riders can publish routes, browse routes from others, and use ratings to understand which routes are worth riding.
The goal is not just a list of GPX traces. A useful route library should help riders understand route quality, surface, difficulty, bike fit, and real‑world feedback from people who have actually ridden it.
We plan to support route capture directly in Drais, so riders can record a ride, save the route, connect it to the right bike, and use it later for mileage, maintenance, and route sharing.
Bike mileage, component wear, service timing, and route history should all stay connected by default. Recording a ride should never feel like double bookkeeping.
Drais is also moving toward workshop integration, built for both the rider and the shop. Riders should be able to book service, share bike specs, maintenance history, and current issues when creating an appointment. Workshops should be able to manage service agendas, view relevant bike details, and update the current state of a service job.
Book appointments with the bike, issue, preferred timing, and service context already attached.
Share the information a mechanic needs without rebuilding the bike profile in another system.
Give workshops useful history around parts, previous work, mileage, and recurring issues.
Let shops update riders as work moves through intake, diagnosis, parts, repair, and pickup.
Drais is committed to continuous development based on real user feedback, not just a fixed feature checklist. As riders use the app, request workflows, and expose friction in everyday bike ownership, those signals will guide what gets refined, added, or reworked.
Have a feature request, a workflow we should support, or a sharp edge in everyday bike ownership? Send it. We read everything.
Roadmap items above shift when riders push back, prove a different priority, or show us a better path. That's the point.
The Drais beta is small on purpose. Riders in the program get the most direct line into what we work on next.