JockeyBox
Docs

Self-Hosted Setup

Everything you need to get JockeyBox running on your own hardware.

Why Self-Host?

Maybe you don't love the idea of your maintenance history sitting on someone else's server. Maybe you already run a homelab and want one more thing on the stack. Maybe you just like having full control. Whatever the reason — I built this option for you.

Your service records, fuel logs, mileage data, receipt photos, vehicle details — all of it stays on hardware you own and control. You still get multi-device sync (just point every phone at your server), family sharing, full backups, PDF report generation, and the achievement system. The only difference is where the data lives.

And if you ever want to move to the cloud tier later, there's a one-click export. No lock-in.

Community Parts Catalog

Even on a self-hosted setup, the app can still tap into the JockeyBox Community Parts Catalog — a shared, crowd-sourced database of parts, part numbers, and pricing that other JockeyBox users contribute to.

This is opt-in by default and can be toggled off at any time in the app settings. When enabled, the app sends the following upstream to the community catalog:

  • Part names, part numbers, brands, and categories you log during service records
  • Pricing data (what you paid, where you bought it)
  • Vehicle fitment info (year/make/model — not your VIN, plate, or personal details)

In return, you get access to parts data from the entire community — so when you're adding an oil filter for your 2019 Tacoma, the app can suggest part numbers and prices that other Tacoma owners have already logged. The more people participate, the better it gets for everyone.

No personal information, vehicle identification numbers, license plates, account credentials, or location data ever leaves your server. The community catalog only deals in parts.

Requirements

Nothing crazy. If you can run Docker, you can run this.

WhatMinimumRecommended
Dockerv20.10+Latest stable
Docker Composev2.0+Latest stable
RAM1 GB2 GB
Disk500 MB2 GB+ (depends on how many receipt photos you hoard)
NetworkPort 16399 openReverse proxy + SSL

Platform Support

I'm working through platform testing as the container matures. Here's where things stand right now.

PlatformArchitectureStatus
Docker Composelinux/amd64 Tested
Portainerlinux/amd64 Tested
Docker Composelinux/arm64 Coming Soon
Raspberry Pi 4+linux/arm64 Coming Soon
Synology / QNAPlinux/amd64 Coming Soon
unRAIDlinux/amd64 Coming Soon
TrueNASlinux/amd64 Coming Soon
Proxmox (LXC)linux/amd64 Coming Soon
Windows (WSL2)linux/amd64 Coming Soon
macOS (Docker Desktop)linux/amd64, arm64 Coming Soon

If you get it running on something not listed here, let me know — I'd love to add it to the list.

Get Started