Mecânica Ágil

Complete management for auto repair shops

Web system turned into an Android app via Capacitor. Manages service orders, parts inventory, clients, finances and vehicle maintenance history.

Platforms
SaaS · Web · Mobile
Year
2025
Status
In production
Role
Full stack — API, web and app

From the estimate to delivery, everything in one system built for mechanics. Mecânica Ágil handles the shop's services, clients, vehicles and finances, and every car moves through a visual kanban from arrival to pickup.

It was built for a real repair shop and became a SaaS: the codebase was converted to multi-tenant, with full isolation between shops in the same database. It runs in any computer's browser and, through Capacitor, as an Android app with its own mobile navigation.

What the system does

  1. Real-time dashboard

    Estimates created, approved, finished and delivered, revenue and status distribution, by day, week, month or custom period.

  2. Visual service kanban

    Each vehicle becomes a card with client, plate, amount and items, and moves through pending, approved, in progress, finished and delivered with a drag.

  3. Professional estimates

    Services, parts and products line by line, discount by amount or percentage calculated on the fly and a PDF to send to the client.

  4. Clients and vehicles

    Registered at drop-off with make, model, color and plate from a catalog of hundreds of models, plus estimate history per client.

  5. Financial control

    Receivables are created when a job is finished. Forecast of what is open, payments received, payables and payment methods.

  6. Parts and product stock

    Catalog with cost and sale price, current stock and movements, plus product purchases that create the payable.

  7. Multi-user with permissions

    Employees and users with per-screen permissions, and the shop's name and logo in the system.

How it was built

Frontend
Vue 3Quasar 2PiniaChart.js
Mobile
CapacitorAndroid
Backend
Laravel 12PHP 8.3Sanctum
Data
PostgreSQL

Technical challenges

  1. Single-tenant to multi-tenant with the system live

    The conversion used a single database with a company column and an Eloquent global scope, a tenant context resolved by middleware and a command to provision new shops with their statuses and payment methods. 82 tests covered the isolation before deploy.

  2. Global catalog, per-shop data

    Makes, models and colors are a shared read-only catalog; services, parts, clients and finances belong to each shop. The same query has to see both without leaking anything between tenants.

  3. Permissions that cover every route

    Every route requires a permission scope. A regression test compares route scopes with the seeder's and fails if any profile, including the admin, loses access to a protected screen.

  4. One front end, two devices

    The same Quasar code delivers a sidebar layout on desktop and bottom navigation on the phone, with hash routing to work inside Capacitor.

Need something
like this?

Tell me the idea or the problem. I help shape the solution and build it from the API to the app.

Let's talk