Case Study2026

Moto Track

A live SvelteKit SaaS web application for motorcycle operations, covering fuel, maintenance, documents, costs, professional shifts, and profitability with Neon and Cloudflare.

Role:Product engineering, full-stack delivery, UI, and deployment strategy

  • SvelteKit
  • TypeScript
  • Neon Postgres
  • Cloudflare
  • Stripe
  • Resend
Moto Track preview

Problem

Riders and professional motorcycle operators need one reliable place for fuel, upkeep, documents, costs, and the work that makes a motorcycle profitable.

Constraint

The product needs fast app-like workflows, offline capture, edge deployment, and paid plans without splitting operational data across separate systems.

Decision

Rebuild the product with SvelteKit, Neon Postgres, and Cloudflare services, then connect Stripe for plans and Resend for transactional email.

Outcome

The live product now covers day-to-day motorcycle operations, including professional shifts, profitability, offline fuel capture, and supporting guides.

Live SaaS

Product status

Fuel capture + sync

Offline workflow

Stripe plans

Business model

Overview

Moto Track is a live SvelteKit motorcycle operations platform. It brings fuel, maintenance, tires, documents, reminders, expenses, professional shifts, and profitability into one place instead of leaving the rider to reconcile notes and spreadsheets.

The product serves both everyday ownership and work use. Riders can record fuel while offline and synchronize it later, follow maintenance and tire history, review operating costs, and use work and report views to understand whether professional riding is paying off.

Product Decisions

The current application uses SvelteKit and TypeScript for the product surface, Neon Postgres for persistent data, and Cloudflare for the edge runtime and object storage. Neon Auth handles authentication, while app-layer ownership checks protect records. Stripe powers the paid plans and billing lifecycle; Resend sends transactional app email in-process.

This keeps the operational workflows close to the data while preserving a deployment path that is fast to iterate. Offline fuel capture is deliberately narrow and explicit: it queues the supported record locally and synchronizes it when connectivity returns instead of pretending the entire product is offline-first.

What I Built

  • A live motorcycle dashboard for fuel, maintenance, tires, documents, reminders, expenses, and reports.
  • Professional work-shift records with cost and profitability views.
  • Offline fuel capture with a visible queue and synchronization path.
  • Pricing and Stripe checkout/portal flows, plus transactional email through Resend.
  • Public guides and supporting product surfaces around the authenticated application.

Current Scope

Moto Track is live at moto-track.net and remains an actively evolving product. Its public roadmap can describe future work, but the workflows above are already part of the current product.

Next step

Have a system to build or a process to fix?

Tell us about the problem. You get a first technical read, a suggested path, and next steps.