LxCars

LxCars is an ERP for vehicle repair shops and dealerships that brings workshop, vehicle and accounting workflows together. It is best suited to operators prepared to run software on their own infrastructure. The free Community plan includes the full software, but buyers who want managed hosting or a simpler setup should look elsewhere.

Overview

LxCars combines customer management, vehicle records, work planning, mechanic time tracking and invoicing. That breadth can help a shop keep service operations and billing in one system; a business that needs only a focused repair-order tool may find an ERP broader than necessary.

Deployment is a consequential choice. LxCars can run locally or through Docker on customer infrastructure, using PostgreSQL on its own server without a cloud dependency. That gives operators control over where the system runs, but also leaves them responsible for server setup and maintenance. The documented route uses Linux components including PHP 8 and PostgreSQL 16, or Docker and Docker Compose.

Key features

The vehicle database connects to KBA vehicle data, and an AI-assisted scanner extracts information from photographed or uploaded registration documents. This can reduce manual entry when creating vehicle records. Vehicle history adds continuity across visits, while work orders and parts inventory support the operational record around each job.

Mechanic mode provides work instructions, time tracking and spare-part requests. The TÜV module handles defects and inspection reminders, useful for shops that need to track follow-up as well as active repair work. Quotes, orders, invoices and delivery notes cover core transaction documents; DATEV export and role-based access rights add accounting handoff and access control.

Six optional AI functions include call transcription, vehicle chat, work-item suggestions, number-plate recognition, incoming-invoice analysis and the Weroni office assistant. Text requests go encrypted to Anthropic or OpenAI APIs; number-plate recognition runs locally, with camera image and video data kept on the server. Shops should weigh those distinctions against their data-handling requirements. WhatsApp messaging uses the Meta Business API and requires a Meta Business account and verified phone number, so it is not a plug-and-play channel.

Pricing

The Community plan costs nothing and is self-hosted, MIT-licensed and described as including the full software. It is the clearest fit for technically capable shops that want to avoid a software charge and can manage their own deployment; the trade-off is that hosting and upkeep remain theirs.

Professional has custom pricing and is hosted, with setup, updates and backups included. It suits businesses that want those operating tasks handled rather than running servers themselves. Enterprise also has custom pricing and offers a dedicated server and individual configuration for multi-branch businesses. Neither paid plan's price is stated, so buyers should compare a quote against the value of managed operations or dedicated infrastructure.

Platforms

LxCars is web-based and supports Linux and self-hosted deployment. Its Linux and Docker installation paths make it a fit for organizations able to operate server infrastructure, not buyers seeking a conventional desktop-only product.

Who it's for

LxCars is aimed at motor-vehicle repair shops and dealerships that want customer, vehicle, workshop and accounting work in one ERP. The maker also presents its kivitendo migration service for workshops and smaller dealerships. Migration price depends on data volume, workstation count and training scope, and the package includes two to four weeks of extended support after transition. Automatic migration does not carry over custom Perl extensions, non-standard custom reports or archived email correspondence, which may matter to businesses with substantial customization or historical records.

The live demo uses sample data that is regularly reset. WhatsApp, telephony and AI capabilities are limited in the demo because they rely on external services, so it cannot show every connected workflow in full.

Pros and cons

• Pros: The free Community plan includes the full software, making the feature set accessible to organizations able to self-host.
• Pros: Workshop, vehicle and accounting functions share one ERP, including KBA-linked vehicle data, job tools and DATEV export.
• Pros: The option to run locally or in Docker without cloud dependency gives infrastructure control to businesses that want it.
• Cons: Linux server requirements or Docker deployment demand technical ownership that will not suit shops seeking turnkey software.
• Cons: WhatsApp needs a Meta Business account and verified phone number, and some demo functions depend on external services.
• Cons: Automatic kivitendo migration leaves out certain customizations and archived email, so some legacy data may need separate handling.

Alternatives

Automotive Repair Software is a useful starting point for comparing products across the category. Carstio is another free, self-hosted web option with unlimited users, clients and cars and all features included; its stated €0/ month forever price makes it a straightforward alternative for teams prioritizing those unlimited records and seats.

OpenAuto may suit buyers specifically seeking free, open source software for Windows, while LxCars is web-based and self-hosted. Shop OS is free for shops under 10 jobs/month, making its stated threshold relevant to very low-volume operations. ARI is a paid alternative with a free plan and trial, spanning Android, iOS, web and Windows; its ARI Pro monthly plan is $39.99 a month.

Bay-Master, CCC ONE Repair Workflow, Mitchell RepairCenter and Repair360 are other options to consider.

Verdict

LxCars is a strong candidate for repair shops and smaller dealerships that want a broad workshop ERP, value infrastructure control and can take responsibility for self-hosting. Its full-featured free Community plan is the main reason to choose it. Look elsewhere if you need managed hosting without custom-price evaluation, or want to avoid server administration and the external-account requirements of some integrations.