Standalone instance

A carrier’s own TMS instance in a day: migration from SaaS and a GPS tracker of choice

📅2026
⏱3 weeks
👥1 developer
SaaS platform · tenantsCompany 12Company 27Company 34 · reefer carrierCompany 4198 trips · 44 counterparties · 128 expensesfleet:import-alemiIDs kept · bcrypt as is · PII re-encryptedCcarrier-brand.comown hosting · own domain · own Telegram botTrips98Drivers / trucks9 / 9Payments66Documents43✓ live in 1 day — nothing re-enteredGPS provider contractWialonunits + messagesRuptela FMSobjects + tracksFreetrack1 request / kind / 300 s
1 day
from empty hosting to a working system
3
GPS providers behind one contract
2
PRO clients in a week

The challenge

Two carriers wanted “the system the big client has”, but on their own domain and hosting, with their own tracker. One already kept records on our SaaS platform (98 trips, 44 counterparties, debts worth millions) — nobody would re-enter that. The other ran the budget Freetrack tracker, which allows one request of each kind per 5 minutes and answers 429 to anything else.

What was built

We built a PRO-client playbook. An import command exports all of a company’s tables from the platform to JSON and loads them into an empty instance, keeping IDs, password hashes and PII encryption, with a dry-run mode. GPS went behind a provider contract: Wialon, Ruptela FMS and Freetrack are configured in settings, and for Freetrack the service keeps rate-limit windows per request kind and a position queue by itself. Each client is a separate branch, a brand folder (logo, colours, robots) and a deploy target that the script refuses to run from a foreign branch.

1

One-command import

all company data from SaaS into the new instance: trips, drivers, counterparties, payments, documents, photos; IDs preserved.

2

Passwords and PII without resets

password hashes as they are, personal data re-encrypted with the new instance key.

3

GPS provider of choice

Wialon, Ruptela or Freetrack; one contract, three implementations, a switch in settings.

4

Freetrack limits under control

one request of each kind per 300 s per token; the service keeps windows, queues and retries after 429.

5

Client brand and domain

letter, colours, favicon, Telegram bot and domain are the client’s; the code is shared and updated by merge.

6

Deploy mistake guard

a deploy target is allowed only from its own branch; shipping code into someone else’s instance is impossible.

The result

The first client moved to its own domain in a day with no manual entry: 98 trips and ₴4.3M of debts in place. The second, with 17 trucks on Freetrack, got a copy with its tracker within a week. New features reach both with a single merge.

Tech stack

LaravelMariaDBWialon APIRuptela FMSFreetrack APIHostinger

Have a similar challenge?

Discuss a project

Next case

Warehouse in TMS

Warehouse loop in a TMS: planner, BOLs, Telegram →