What Drivurs is building through 2027
This roadmap covers what Drivurs is actively tightening now, the major platform priorities for the rest of 2026, and the longer arc into 2027.
- Beta roadmap
- Now / 2026 / 2027
- Real priorities, flexible timing
How to read this page
How Drivurs prioritizes work
Drivurs is still in beta, so the priority is to make the connected workflows feel tight: garage records, local discovery, event setup, crew coordination, community context, and controlled-environment performance review.
This roadmap is meant to show what is being actively improved now, what the platform is growing into across 2026, and what the longer-term shape looks like by 2027. Timing can move during beta, but the direction here is real.
Now
What is being tightened right now
Immediate beta work focused on clarity, trust, and fewer broken handoffs.
Onboarding, handoff, and first-use clarity
- Tighten the path from the public website into the right app workflow
- Make onboarding clearer for builders, organizers, and performance users
- Reduce confusion around what Drivurs already covers today versus what is still in beta
Core reliability in Garage, profiles, and event flows
- Reduce friction in add, edit, save, and manage flows across vehicles, profiles, and events
- Improve trust in the details that matter: current setup, hosts, route info, attendance state, and visibility settings
- Raise readability and polish across the product and public site, especially on mobile
Events, clubs, and meet-day coordination
- Make schedule, venue, hosts, route, visibility, and attendance easier to understand before the day starts
- Clean up organizer and club workflows so event setup feels less scattered
- Tighten the handoff between event detail and messaging when plans change live
Racing trust, moderation, and reporting baseline
- Make RaceBox connection state, session flow, warnings, and run-validity signals easier to trust
- Improve diagnostics so saved runs and sessions feel less ambiguous
- Strengthen baseline moderation, reporting, and trust surfaces without bloating the product
2026
The main platform priorities for the rest of 2026
The goal is a more complete, more dependable platform for builders, organizers, crews, and performance-minded users.
Garage as a better long-term build record
- Richer history around what changed, when, and why
- Better continuity between maintenance, modifications, photos, and public sharing
- Cleaner ways to summarize a build without flattening the detail builders actually care about
Events and clubs that are easier to operate
- Stronger host workflows around invites, attendance clarity, visibility, and linked club context
- Cleaner club roles, member flows, and club-event management patterns
- Better event structure so organizers spend less time restating the plan across channels
Better crew coordination on the day of a meet
- Stronger handoff between event detail and messaging when the route, timing, or regroup point changes
- Clearer presence, conversation context, and real-time coordination flows
- Less ambiguity around where the latest plan actually lives for the crew
Community discovery and more useful public enthusiast content
- Better discovery across city, brand, and custom communities
- Stronger saved-post, search, and profile pathways so good information stays findable
- Better public website paths into the app for local scene, vehicle, and guide intent
Racing and performance history with stronger trust signals
- Clearer saved-session review and stronger validation UX around runs and telemetry
- Better continuity between the vehicle setup, the session, and the performance result
- More dependable performance history for controlled-environment use, not screenshot roulette
Trust, reliability, and calmer operations
- Stronger reporting, moderation, and admin surfaces for a growing enthusiast platform
- Better caching, performance, and resilience across app and website flows
- More dependable deep links, public web surfaces, and website-to-app routing
2027
Where Drivurs is headed as a more mature platform
The longer arc is a connected enthusiast ecosystem where the important context stays attached instead of breaking across tools.
A connected record across the enthusiast lifecycle
- Build, community, event, crew, and performance history should feel like one connected record instead of five disconnected stories
- Identity, profiles, and vehicle context should travel more cleanly across the platform
- The product should feel more coherent to builders, club admins, organizers, and drivers with long-term history in the app
More mature public discovery for builds, events, clubs, and knowledge
- Broader public surfaces for discovering enthusiast knowledge, city activity, and selected public entities without compromising private coordination
- Richer website surfaces that bridge into the app instead of acting like a separate marketing shell
- Stronger public discovery around vehicles, events, communities, and guides where the signal is good enough to deserve it
More complete club and organizer operating tools
- Deeper roles, invites, operating patterns, and event control for communities that run repeatedly
- Better local ecosystem support for clubs, crews, and event operators who need more than a simple post-and-chat workflow
- Calmer moderation and trust patterns as the network gets denser
Deeper performance history and platform integration
- More useful long-term performance history tied back to the car and setup over time
- Careful expansion of device and provider adjacency around controlled-environment performance workflows
- A more dependable platform foundation as telemetry, saved history, and public surfaces scale
Feedback
Help shape the priorities
The most useful feedback is not "please add feature X." It is the actual workflow, where it broke down, what you had to work around, and what a better outcome would have looked like.
If you are a builder, club admin, event organizer, crew member, community user, or controlled-environment performance user, the sharp version of that feedback is what helps set priorities.
Next step
Stay close to what Drivurs is becoming
If this roadmap matches the kind of platform you want, join beta updates, explore the product surfaces already live on the web, or send the specific workflow feedback that would make Drivurs more useful to you.