English
LubeLogger Hosting
Track vehicle maintenance, fuel, repairs, reminders, upgrades, and operating costs.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
LubeLogger’s official links and original website
LubeLogger Website
More
Tech
- Docker image
- ghcr.io/hargata/lubelogger:latest
- Default port
- 8080
How LubeLogger works
LubeLogger organises records around vehicles and equipment. Users can log service work, repairs, upgrades, fuel purchases, odometer changes, taxes, inspections, supplies, plans, and notes, then review costs and maintenance history through dashboards and reports. Recurring reminders can be driven by dates, mileage, or both, helping operators plan work before a task becomes overdue.
Documents and images can be attached to supported records, while the API and optional integrations enable additional workflows. The value of the history depends on accurate entries and authorised records; LubeLogger does not verify invoices, mileage, mechanical condition, tax compliance, or whether a maintenance task was performed correctly.
Key LubeLogger features
Upstream LubeLogger leaves authentication disabled by default, and the catalogue does not set EnableAuth=true. The freshly deployed public address can therefore expose the application until the owner enters Settings, enables authentication, and creates the root user. That security step must be completed immediately before vehicles or documents are added.
New users follow an invitation model after authentication is enabled. Upstream recommends SMTP for a smoother invitation flow, but application email is disabled across the hosting service services. The page should not promise emailed invitations, password messages, or reminder mail. Administrators must use supported non-email workflows and verify how invitation tokens are delivered to trusted users.
Who uses LubeLogger
Individuals maintain ownership records for one or two vehicles, enthusiasts document modifications and consumables, and small fleets track service intervals and operating costs. Workshops can use the system as an internal log when everyone understands that it is not a certified repair-management or accounting platform.
LubeLogger is not a telematics service, legal odometer authority, tax adviser, inspection provider, or substitute for manufacturer maintenance guidance. Sensitive invoices, registration documents, and vehicle identifiers require careful access control and an appropriate retention policy.
Self-hosting LubeLogger: requirements and cost
LubeLogger resource use grows with vehicle count, records, uploaded documents, images, reports, API requests, users, reminders, and concurrent sessions. PostgreSQL and MariaDB are Not required by the catalogue template; persistent application, document, and image directories hold the deployment’s records. LubeLogger itself has no separate hosted software fee, while attachment-heavy histories can consume more storage than text-only logs.
On AvaHost, LubeLogger uses Plan 1 at €2. The hosted LubeLogger package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Authentication is disabled at first launch and must be enabled immediately by the owner. Application email, SMTP delivery, telematics feeds, legal validation, tax advice, manufacturer data, document authenticity, and third-party service accounts are not included.
F.A.Q
LubeLogger starts at €2 on Plan 1. A household or small fleet with mostly text records fits that entry plan. Vehicle count, uploaded documents, images, reports, API activity, reminders, users, and concurrent sessions are the main factors for reviewing capacity, with attachments usually driving storage growth fastest.
No. Upstream authentication is disabled by default, and the catalogue does not enable it through an environment setting. The intended owner must open Settings, enable authentication, and create the root user before storing vehicle records or exposing the address to others. Until that step is complete, treat the new application as publicly reachable.
Application email is disabled across AvaHost cloud apps. LubeLogger’s invitation model and optional reminder messages therefore cannot rely on SMTP from this package. Enable authentication, create or deliver supported invitation tokens through a trusted non-email channel, and use the in-app reminder views unless a separately approved service design is introduced outside this hosted offer.
AvaHost applies application updates automatically and includes scheduled backups for the persistent records, documents, and images. After a release, verify authentication, vehicle lists, service and fuel entries, reminders, reports, document uploads, images, plans, inspections, and any API consumer. Export or retain authoritative invoices and legal records separately from the maintenance database.