It's looks like you started this project 6 hours ago. Are you sure it's tested and production ready?
Hi Anton,
Haha, fair point! The public repo is definitely younger than the core logic.
To clarify, the backend rules have been running privately on my production server for a couple of months (managing ~200 devices across 30 accounts). Today's 6 hours were spent refactoring, cleaning up, and packaging everything to publish it as an open-source repo.
You're completely right, though—it's still a fresh public release and needs broader testing and community feedback before calling it rock-solid. Over the next few days I'll be adding a couple of missing pieces (like payment receipts / delivery notes), but the underlying suspension and billing logic is already thoroughly tested.
Appreciate you taking the time to check out the repo!
What do you mean by backend rules? Are they effectively reimplemented from scratch or you reused some of the code?
Hi Anton,
By backend rules I mean the entire billing, pricing, and suspension logic was built completely from scratch in Go.
It doesn't reuse any Traccar codebase—it's a standalone service that purely interacts with Traccar REST API.
So the core engine (calculating recurring fees, grace periods, account locking, SQLite/MySQL persistence) is 100% custom code that I've been running and refining over the past couple of months on my setup.
By reusing I meant your own code that you run in prod. Because the repo shows everything as completely new.
Hello Traccar Community,
As many of us know, Traccar is an incredible GPS tracking server, but it does not natively manage billing, subscription lifecycles, or automated customer suspension upon expiration.
To solve this, I developed traccar-billing, a standalone, multi-tenant billing & revenue management panel designed specifically for Traccar operators and SaaS providers.
Key Features
Automated Account Suspension & Reactivation: Monitors expiration dates and automatically disables users in Traccar past their grace period via REST API. Upon payment registration, access is instantly restored.
Dynamic Per-Device Pricing: Automatically reads device counts per account from Traccar and calculates recurring fees based on active GPS units.
Rolling & Calendar Billing Cycles: Support for custom billing cycles (e.g., 30-day rolling or fixed calendar day payouts).
Multi-Line Charges & One-Off Items: Charge monthly fees alongside installation charges or accessories without affecting subscription expiration dates.
Multi-Tenant Architecture: Connect and manage multiple independent Traccar servers/tenants from a single dashboard.
Sellers & Expenses Tracking: Track sales representative commissions and net profit per cycle.
Installation Scheduler: Appointment management with built-in WhatsApp confirmation links.
Tech Stack & Deployment
Built as a single Go binary (no heavy PHP stacks or complex JS frameworks required).
Embedded templates, native SQLite or MySQL support.
Lightweight, fast, and fully Docker-ready.
Source Code & Repository
The project is 100% Open Source under the MIT License.
GitHub Repository: https://github.com/emmanuelh-dev/traccar-billing
I built this to help anyone running a commercial Traccar server who wants to replace manual spreadsheets with an automated solution. Feedback, suggestions, and contributions are very welcome!