FleetDesk is the multi-brand fleet manager that runs the operator side of addFleet. Keep your booking site. Keep your customers. Plug FleetDesk in behind it and stop asking your front-desk to live in spreadsheets, WhatsApp, and three partner portals at once.
Not every feature lives on this page — the full list is below. These are the ones the woman behind the counter mentioned first.
Sticky-left vehicle column, virtualised day grid that scrolls to 2030 without breaking a sweat. Drag empty cells to create a booking. Drag pills to reassign cars. Five sort modes when one operator likes plate order and the other lives by busyness.
VikRentCar + ADDCAR (Rentway SOAP). Inbound polling and outbound status push.
Inbound rows resolve to your highest-priority free car. Dashed-amber pulse until accepted.
Each provider owns its own logo, terms (ET + EN), and allowed status set. Contracts pick the right header automatically.
WebAuthn on every device. PIN gate is brute-force throttled — 3 fails and the IP is blocked for 24 hours.
Add to home screen. Safe-area inset support. Two giant action tiles for Pick Up / Drop Off.
No marketing renders. These are the real workspaces operators use every day at Keevise 10 in Tallinn.
Multi-unit vehicles stack into lanes. Pre-booked holds show as a striped fill. The current hour is a faint indigo line you can't miss. Scroll horizontally for months; nothing janks.
Structured customer fields beat a freeform "customer" string every time. Driver licence, flight number, country of origin, DOB, notes — round-tripped to partners that accept them, kept locally for those that don't.
Two giant tiles for Pick Up and Drop Off. A 3-up stats row to know if today is busy before the first coffee. Full-screen trip sheets with smart defaults — current time, previous-booking mileage, 100% fuel.
Drop a logo (PNG/JPG/SVG, 2 MB max). Paste terms in Estonian and English. Pick which statuses your operators are allowed to set. The PDF contracts pick the right header automatically.
provider_id FK.No "AI-powered" anything. Just the eight areas FleetDesk currently covers, end-to-end, in production.
no_show and ra_closedVEHICLE_EVENTS registry — adding a 4th event type is one lineProviderResolver source-prefix mappingext-soap dependencysync_log per attempt(source, source_ref) — never clobbers manual overridesextra_details JSON/uploads/contracts/booking-{id}/X-Fleet-Token auth?t= for image / link resourcesenv(safe-area-inset-*)src/ public/ sql/ uploads/ + env example_migrations tabletehno, tüv, mtpl, liiklusBearer token in, HMAC-SHA256 signed webhooks out. You can drive every important surface of FleetDesk from your existing booking site, your data warehouse, or a cron on someone's MacBook.
The same REST surface that powers the FleetDesk frontend is the one we hand brokers. No second "partner API" tier. If we can build a console feature with it, you can build whatever you want on top.
$ curl https://manager.addfleet.ee/api/reservations \ -H "Authorization: Bearer fd_live_5b7f9c…" { "reservations": [ { "id": 4218, "source": "vrc:vaikebussirent24", "source_ref": "19874", "provider_id": 2, "vehicle": { "id": 17, "plate": "261LMA" }, "customer": { "first_name": "Anneli", "last_name": "Tamm", "driver_license": "EE 1248471", "flight_number": "OV332", "country_of_origin": "EE" }, "pickup_at": "2026-05-28T11:00:00Z", "dropoff_at": "2026-06-01T07:00:00Z", "status": "pending" } ], "sync_log_id": 8124 }
# Outbound — every reservation lifecycle change X-Fleet-Event: reservation.confirmed X-Fleet-Signature: sha256=9c1f… Content-Type: application/json { "event": "reservation.confirmed", "reservation_id": 4218, "provider": "vaikebussirent24", "vehicle_plate": "261LMA", "actor": "operator:liisi", "at": "2026-05-25T14:02:11Z" } # Verify (PHP) $expected = hash_hmac('sha256', $rawBody, $secret); $ok = hash_equals('sha256='.$expected, $headers['X-Fleet-Signature']);
| GET | /api/ping | health check, returns server time |
| GET | /api/vehicles | all vehicles + categories + locks |
| PUT | /api/vehicles/{id} | edit dates / ownership / inspection |
| PUT | /api/categories/{code}/vehicle-order | priority list for auto-preassign |
| GET | /api/reservations?from&to | window of bookings |
| POST | /api/reservations | create a booking |
| PUT | /api/reservations/{id}/status | status transition (per-provider set) |
| DEL | /api/reservations/{id} | soft-delete to Trash |
| POST | /api/reservations/{id}/restore | restore from Trash |
| POST | /api/reservations/{id}/photos | multipart photo upload |
| GET | /api/providers | brands + logos + terms |
| POST | /api/providers/{id}/logo | PNG / JPG / SVG, 2 MB |
| POST | /api/sync/run?adapter=vrc | manual sync trigger |
| GET | /api/sync/log?adapter&since | attempt-by-attempt history |
| POST | /api/backups/run | on-demand zip, daily cron-gated |
| GET | /wp-json/fleet/v1/... | booking-site plugin REST surface |
No hand-wavy quarter graphics. This is the actual handoff doc, copy-pasted, with the dates rounded.
We've been the broker on the other side of these pitches. So we'll keep it short.
FleetDesk slots in behind whatever you already sell on — WordPress + VikRentCar, addCar, your own custom thing, or three of them at once. We don't want to be your storefront. We want to be the brain that the storefront talks to.
Operators don't switch tabs between three partner portals. Owners get a unified P&L across brands. New providers are added in a settings screen, not a deployment.
Self-host on €5 shared hosting and own every byte. Or use ours — your data exports as a single zip whenever you want. Daily auto-backups are yours by default, not a paid add-on.
The front-desk operator is productive on a tablet the same day. The PWA installs to home screen on iOS, the layout adapts at 768 px, and the two giant tiles for Pick Up / Drop Off mean nobody asks "which menu is it under?"
Every feature shipped this quarter came from a question the woman behind the counter asked us. Damage marks. Flight number. After-hours surcharge. None of that is on a board deck. All of it ends a real recurring argument in a real rental office in Tallinn.
FleetDesk is run by a two-person team that already operates one fleet. We can do hands-on onboarding for five brokers a quarter without breaking the thing that makes us useful. After that, you go on the list for next quarter.