Our Approach

Transparency about how we're building LapEvo and what you can expect.

Built by Racers, for Racers

LapEvo is a community-driven project. We're building the telemetry analysis tool we wished existed—one that's transparent about how it works, respects your data, and gets better based on real feedback from sim racers.

Your input directly shapes what we build. Feature requests, feedback, and community discussion drive our roadmap. This isn't just marketing speak—we genuinely want to build something useful for the sim racing community.

Planned Pricing Model

Free

Self-Hosted

Run LapEvo on your own hardware with full functionality. You control everything—your data stays on your machine unless you choose otherwise.

Paid

Managed Cloud

A hosted version for those who want convenience without running infrastructure. Includes automatic updates, backups, and support.

Data Transparency

We believe in being upfront about data practices. Here's how telemetry data works in LapEvo:

  • Optional upload — Telemetry upload to our servers is on by default but can be disabled with one click. We'll never hide this setting.
  • Why we collect data — Aggregated telemetry data helps us train machine learning models to provide better coaching insights. More data = better AI coaching for everyone.
  • You stay in control — Your session data is always yours. Self-hosted users keep everything local. Even with uploads enabled, you can request data deletion at any time.

Source Availability

We plan to make LapEvo's source code publicly viewable under a source-available license (likely BSL 1.1 or Elastic License 2.0) once we release.

What this means:

  • You can inspect the code to see exactly how it works
  • You can modify it for personal use
  • Commercial redistribution is restricted to ensure sustainable development
  • We may transition to a fully open source license over time

This approach lets us be transparent while building a sustainable project. We want LapEvo to exist and improve for years to come.

Have questions or feedback about our approach? We'd love to hear from you.

Share Your Thoughts