Budget: 27000 UAH Deadline: 10 days
Good day.
We are engaged in the development of professional projects ranging from small websites to complex web projects.
About us: viacore.group
Budget: 27000 UAH Deadline: 15 days
A separate logistics system is needed on top of Traccar. What will need to be developed separately:
Deploy Traccar on VPS;
Connect TKSTAR TK-905B;
Map with coordinate updates;
Authorization and roles;
Separation of companies and data;
Module for issuing and returning beacons;
Saving the history of "beacon → car → trip";
Reissuing a beacon to another car;
Completing a trip separately from returning the beacon;
Route history;
Parking report;
Geofences and notifications;
Mobile adaptation;
Excel/PDF reports;
Client data protection.
So, the scope of work is quite substantial, and the budget is unrealistic...
The most challenging part:
The most important thing here is not even the map. The hardest part is the rotation of beacons without losing history.
For example:
Beacon No. 12 was issued to car AA1234BX.
It completed the Kyiv - Lviv trip.
The trip was closed.
The beacon was returned to the warehouse.
The next day, this beacon was issued to car BC5678KM.
The system must understand that the old coordinates of beacon No. 12 belong to the first car, and the new ones belong to the second. You cannot simply change the beacon's name in Traccar from one car number to another, as then the history will become incorrect.
Main technical risk:
Before agreeing on the price, it is essential to obtain one genuine TKSTAR TK-905B and check:
if the specific version works with Traccar;
what protocol it uses;
if it is possible to change the server and port via SMS command;
if it is not blocked by the Chinese service;
how APN, IP, and port are configured;
if the device reliably transmits coordinates;
what identifier it sends — IMEI or another number.
The name TK-905B does not guarantee that all batches of devices are absolutely identical.
Therefore, the correct order is to first pilot one beacon, and only then fix the final price of the entire project.
Real timelines and costs:
My approximate estimate for one strong full-stack developer:
Pilot
VPS, Traccar, one beacon, checking coordinate reception, basic map:
5–10 working days.
This stage may still partially fit into a budget of about 27,000 UAH.
MVP
Map, logins, companies, roles, issuing and returning beacons, trips, history of bindings, basic parking report:
4–7 weeks.
Estimated cost range:
80,000–140,000 UAH.
Full version
Geofences, notifications, advanced reports, Excel/PDF, good mobile version, administration, documentation, testing, and support:
7–12 weeks.
Estimated range:
240,000–280,000 UAH, depending on the quality of design, reports, and reliability requirements.
Budget: 27000 UAH Deadline: 31 days
📌Hello.👋
⭐️My name is Andrey.
⭐️My work experience: 12 years+
• ➡️I can show works specifically on web platforms
• 🎨Portfolio: 
Freelancehunt
• ✅Work rating on Behance (over 600,000 views)
• 💼More works here: 
Dribbble
Budget: 27000 UAH Deadline: 5 days
Good day! 🧡
I am ready to take on the work and help complete everything efficiently and in a short time. I have experience in similar projects, and I have examples of work and reviews that I can show.
I can start soon. Please write the details - we will discuss the task, deadlines, and the best implementation option. I respond quickly 🙂
Budget: 27000 UAH Deadline: 25 days
Good day! I installed Traccar on a VPS for TK-905B trackers, and I'm familiar with redirecting beacons from the Chinese server via SMS commands — usually, this is the most tedious part at the start.
The key point in the description: in Traccar, the device is tightly bound to the user out of the box, while you have rotation — the same beacon goes to a different vehicle and factory for each trip. I will refine this logic with a separate layer on top so that the trip history and multi-tenancy do not get mixed up.
Please let me know — do you want a completely custom frontend from scratch, or can it be based on the Traccar web interface with customization for roles? This greatly affects the timeline.
Budget: 26900 UAH Deadline: 14 days
The most dangerous part of this technical specification is not Traccar or the map, but the rotation of beacons: if the device name is simply rewritten upon issuance, all old history will silently be reassigned to someone else's machines. Therefore, the unit of accounting should be the trip, not the device, and the entire architecture hinges on this.
Regarding your questions.
1) I haven't had the opportunity to deploy Traccar in production yet - I’m being honest, I won’t show any made-up cases. But it’s open-source with detailed documentation, a standard stack of Ubuntu plus Java plus PostgreSQL, and TK-905B is supported out of the box, so I don’t see any risk in the deployment itself. However, custom frontends on top of someone else's REST and WebSocket APIs are my regular work: accessibilityscanner.top is my SaaS with roles and multi-tenancy (admin, manager, client, each sees only their own), pinger.md is an aggregator with a live map, cards, filters, and mobile adaptation. I have been programming since 2013.
2) I suggest not complicating multi-tenancy and rotation on Traccar attributes (this quickly turns into a mess), but rather moving it to a thin layer: your own database with tables for companies, users with roles, devices, trips, where the trip stores device_id, vehicle number, company, dates, and status. Reissuing means closing the old trip and creating a new one, not rewriting the device, so tracks always remain with their vehicle. Traccar is only queried for raw coordinates by device_id, all visibility logic is in your own layer: filtering by company_id is straightforward and doesn’t break during Traccar updates.
3) MVP (live map, logins and roles, rotation module, parking report) - target is 60 percent of the budget, 9-10 days. The full version with geofences, notifications, and report export - the entire project budget, 14 days in total. I will finalize the exact figures in correspondence after clarifying details about geofences and export.
4) For 20-50 beacons with a 5-minute interval, the load is modest: these are rare short packets of coordinates, not a video stream. A VPS with 2 vCPU, 4 GB RAM, 40-80 GB SSD will suffice - Traccar, PostgreSQL, the rotation layer, and frontend on one machine, with a margin for growth of the fleet by 2-3 times without an upgrade.
I would like to emphasize separately: the layer above Traccar in your case is not an option at the discretion of the performer, but a mandatory condition - without it, the history of bindings is lost exactly as you described in the technical specification. I will create the map using Leaflet and OpenStreetMap: free, without keys and billing, Google Maps does not provide anything worth paying for here.
One question for accuracy: are notifications about entering and exiting geofences needed for the client factories, your managers, or both? This depends on...
Budget: 27000 UAH Deadline: 7 days
Hello, I worked on a GPS monitoring system for a fleet using Traccar — I deployed a server for 80 trackers, created a custom frontend in React with a live map (updating every 5 seconds) and reports on parking.
Questions about your project: when the manager reissues a beacon, should the old trip automatically close at the moment of entering the new vehicle number, or is separate confirmation from the manager needed? This is important for the correct logic of preserving the history of bindings.
One more thing: for multi-tenancy, is it better to use Traccar roles and groups or a separate service with its own database on top of the API? I lean towards the second option due to the complex rotation logic, but I want to hear your perspective.
I suggest we connect; I will provide you with free technical consultation and we can draft a development plan + I will tell you about my team!
Budget: 27000 UAH Deadline: 21 days
I understood the task: set up Traccar on a VPS to receive data from TK-905B beacons, restrict access by roles (admin/manager/client), and add a beacon rotation module between trips with a minimum number of fields for the issuance-receipt operation.
I will deploy Traccar myself on the VPS, configure it according to the load and the number of simultaneous devices, set up the reception of the TK-905B protocol, and help with transferring beacons from the Chinese server via SMS commands.
Multitenancy and the rotation module will be implemented as a separate service on top of the Traccar REST API, without touching its core, making it easier to update the platform later without conflicts. The Postgres database, roles, and data visibility (clients see only their trips and beacons) will be managed at the level of this service. For the issuance-receipt operation of the beacon, I will create a single window with a minimum number of fields: the beacon is identified by the short number from the sticker, the vehicle is mandatory, and the rest is optional; the point on the map will be immediately labeled with the vehicle number and trip, not the device ID.
The frontend for clients and managers will be a web interface with a real-time map, without unnecessary navigation, tailored to the tasks of each role separately.
In terms of timelines, I estimate 3 weeks for the first working version with deployment, multitenancy, the rotation module, and a basic frontend, but I am ready to clarify further after I see the complete technical specification regarding the number of simultaneous beacons and trips.
Budget: 27000 UAH Deadline: 14 days
Hello!
I have reviewed the project description. The key difficulty here is not with Traccar itself, but with the logic of working with beacons: their constant rotation between trips, maintaining the history of bindings, and differentiating access for different companies. This will determine how convenient the system will be for daily operations.
I would implement a separate module that works on top of the Traccar API. This will allow Traccar to remain responsible for obtaining GPS data, while all business logic is moved to a separate service. This approach significantly simplifies the further development and maintenance of the system.
I preliminarily estimate the implementation of the MVP at 2 weeks. After a brief discussion of the details and clarification of the business logic, I will be able to provide an exact timeline and implementation stages.
I would be happy to discuss the details and propose an optimal solution for your work scenario.
Budget: 27000 UAH Deadline: 21 days
Good day!
The project is completely clear and looks like the right architecture for building a proprietary GPS platform without reliance on third-party services. I have experience in developing complex web platforms, monitoring systems, mapping services, REST/WebSocket APIs, Docker, PostgreSQL, and integration with external devices.
Regarding the questions:
**1. Have you deployed Traccar?**
Yes. I have worked with deploying Traccar on a VPS, configuring the reception of GPS tracker data, integrating via REST API and WebSocket, as well as setting up the storage and processing of coordinates.
**2. Have you created a custom frontend on top of the Traccar API?**
Yes. I prefer not to modify the Traccar core but to build a separate service on top of its API. This approach significantly simplifies updating Traccar and developing proprietary business logic.
**3. How do I propose to implement multi-tenancy and rotation?**
Traccar will be used solely as a GPS server and telemetry source. All business logic (companies, users, roles, trips, beacon issuance history, statuses, and access rights) will be implemented in a separate backend service with its own database. Each beacon issuance creates a new "trip" object that links the device, vehicle, and client without altering the history. After the trip is completed, the record is closed, and the beacon returns to the pool of available devices. This fully preserves the history of all bindings and routes.
For the frontend, I propose:
* React + TypeScript;
* Leaflet + OpenStreetMap;
* WebSocket for updating coordinates almost in real-time;
* a fully responsive interface for PCs and mobile devices.
I will also implement:
* roles (Administrator / Manager / Client);
* issuance and return of beacons in a few clicks;
* search by vehicle number, beacon, and direction;
* route history;
* parking reports;
* automatic clearing of coordinates older than 6 months while preserving trip history;
* Docker deployment;
* database backup.
**Recommended VPS configuration (20–50 beacons):**
* 4 vCPU;
* 8 GB RAM;
* SSD NVMe 100–150 GB;
* Ubuntu 24.04 LTS;
* Docker + Docker Compose;
* PostgreSQL;
* Nginx with SSL.
This configuration is sufficient with a good margin for further scaling.
I will be able to provide an exact cost after discussing the details and approval.
Budget: 27000 UAH Deadline: 30 days
Hello.
I am a senior developer with ten years of experience.
Of these, 6 years in an online taxi project. Full life cycle from MVP to production. There I partially had experience with what you describe (GPS, dispatch, live map with cars in real time, navigation, taximeter).
I also worked in a transport company where we used Traccar.
Answers to questions
1. Have you deployed Traccar?
Yes. I deployed Traccar on Ubuntu under Docker. I configured PostgreSQL + GIS, HTTPS via Nginx + Let's Encrypt, database backup, updates without data loss. I connected GPS trackers via protocols, set up notifications/user rights.
2. Did you create a custom frontend on top of the Traccar API?
Yes. I used the Traccar REST API to create my own web interface. Authorization occurred through the Traccar API, data on trackers, positions, parking, and geofences were obtained directly through the API. The interface itself was written in Vue and contained only the necessary business functionality without the standard Traccar interface.
3. Projects are under NDA. Therefore, I cannot display them in any way.
4. How to implement multi-tenancy and a rotation module?
Each company will be a separate tenant with complete data isolation at the application level and access rights. All requests to the Traccar API go through a custom backend that filters devices and users for only its client. The rotation module is implemented with a separate equipment issuance history table: it records the device, employee, issuance and return dates, status, and responsible manager. This allows you to see the current owner of the beacon and the entire history of its movements between employees and companies.
5. Timeline and price
Example of a reasonable estimate.
MVP
- map;
- authorization;
- companies;
- users;
- issuance/return of beacons;
- parking.
Timeline: 4 weeks.
Cost: 4000 USD.
Full version MVP + additionally:
- geofences;
- notifications;
- reports;
- roles;
- filtering;
- export;
- action log.
Timeline: 8 weeks.
Cost: 8000 USD.
Timelines and costs are approximate. Exact details will be provided after drafting a complete technical specification for development (I will handle the design, I have experience).
Budget: 27000 UAH Deadline: 21 days
Hello! The project is great, technically transparent, and fully aligns with my stack. I am ready to implement a reliable platform without unnecessary workarounds.
Answers to your questions:
1. Yes, I have experience deploying, configuring, and optimizing Traccar on VPS, including managing data reception protocols and setting up old telemetry cleaning policies (Retention Policy).
2. Yes, I have worked with custom visualization on top of Traccar REST API and WebSocket.
3. Rotation architecture: we do not touch the Traccar core. We will set up our own backend service with a relational database. Traccar receives raw coordinates from the hardware via a unique beacon ID. Our service provides multitenancy, role management, and a rotation module: linking a short number/beacon to the vehicle's state number and creating a route while fully preserving the history of tracks over time intervals.
4. VPS configuration for 20-50 beacons: 2 vCPU, 4-8 GB RAM, 50 GB NVMe SSD (for example, DigitalOcean, Hetzner, or similar) - this will be sufficient for the fast operation of the database and the platform itself.
Regarding the stack:
- Backend: PHP (Laravel) or Node.js for processing business logic, rotation, and interaction with the Traccar API.
- Frontend: React or Vue.js + Leaflet / OpenStreetMap for an interactive map with smooth updates via WebSocket.
I am ready to discuss the implementation details (MVP and full version) in private messages. Message me, and we will discuss the architecture and get started!
Budget: 27000 UAH Deadline: 10 days
Hello! I will answer your questions.
I work with Traccar: I know its REST and WebSocket API, receiving from devices on the GT06 protocol (TK-905B is supported out of the box), redirecting Chinese beacons with SMS commands. A custom front end on top of the Traccar API can be done as standard; I can guide you through the architecture in correspondence based on examples.
Multitenancy and rotation are key here. Traccar itself does not store the history of beacon→vehicle bindings, so I implement rotation as a separate layer on top of its API: my own database, where each trip is a record (device_id, vehicle number, company, period). Reissuing closes the old trip and opens a new one; old tracks remain permanently associated with the vehicle that was active at that time, with no overwriting and loss of history. Multitenancy is on the same layer: I filter data before sending it to the front end, so the client only sees their active trips, while the pool and service data are hidden.
A VPS for 20-50 beacons with a 5-minute interval is a light load: 2 vCPUs, 4 GB RAM, 60-80 GB SSD for a six-month history, with automatic cleanup older than 6 months and retention of trip summaries.
Front end: React + Leaflet/OSM, live map via WebSocket, vehicle card, company panel, search, responsive for mobile.
By stages: MVP (map, logins, rotation, parking) in 2 weeks, full version with geofences, reports, and export in 3 weeks. I will clarify the price for each stage after a couple of details. I look forward to collaborating.
Budget: 27000 UAH Deadline: 45 days
Hello.
We can take on such a platform; the task is clear to us. It is important not just to have a map with trackers, but also the correct logic for beacon rotation, the history of flight bindings, data isolation by companies, and convenient work for managers at the loading point. We have logistics experience and an understanding of similar processes, so we understand how critical it is not to lose history here, to correctly separate the closure of a flight and the return of the beacon to the pool, as well as to make the system convenient for clients, dispatchers, and administrators.
Technically, this can be assembled as a reliable solution based on Traccar with a separate custom layer for your business logic, multi-tenancy, rotation, reports, and client interface. We can also think through the optimal architecture for storing history, retention policy, beacon statuses, real-time map functionality, and an adaptive mobile version, so that the platform is not just functional but truly convenient for daily use.
Please write to us in private messages for a detailed discussion of the project and to provide information on the timeline and cost of such a project.
Budget: 27000 UAH Deadline: 31 days
Good day!
I have experience in developing web platforms with mapping, GPS tracking, API integrations, and building scalable systems. Your project is well-suited for implementation based on Traccar with a custom business logic service, which will allow not to change the Traccar core and significantly simplify further development.
For the MVP, I propose the stack:
Backend: Node.js (NestJS), TypeScript;
GPS: Traccar + REST/WebSocket API;
Frontend: React + Leaflet (OpenStreetMap);
Database: PostgreSQL;
Authorization: JWT + roles (Administrator / Manager / Client).
I would implement the rotation module as a separate service on top of Traccar. Traccar is only responsible for receiving GPS coordinates, while all bindings of beacons to routes, vehicles, history, multitenancy, and access rights are stored in a custom database. This architecture allows for reusing any beacon in new routes without losing history.
In the MVP, we can implement:
* deployment of Traccar on your VPS;
* connection of TK-905B and device redirection;
* role system;
* beacon issuance/return module;
* real-time map;
* route history;
* parking report;
* responsive web interface.
In the second phase, we can add:
* geofences;
* Telegram/e-mail notifications;
* Excel/PDF export;
* advanced analytics;
* additional reports.
I will also assist with VPS recommendations (this will be more than enough for 20–50 beacons) and prepare documentation for system administration.
Estimated timelines:
MVP — 3–4 weeks.
Full version — 6–8 weeks.
After delivery, I will provide support, help with deployment, and transfer all source code, repository, and documentation. I would be happy to discuss the project details and propose an optimal architecture for your requirements.
Budget: 27000 UAH Deadline: 1 day
Good day, Serhiy.
The most dangerous part of this technical specification is not Traccar and not the map, but the rotation of beacons: if you overwrite the car number on the device, old tracks will quietly be signed by someone else's trucks. To avoid this, the car number must exist in a separate layer above Traccar: each issuance of a beacon creates a trip record linked to "device → car → company" with a time range, while Traccar remains just a gateway for coordinates. Then the client's map shows only their active trips with correct signatures, the history does not mix, and free beacons from the pool are hidden from the factories.
Options:
≈12 days: 12000–16000 UAH
Minimum viable product for launching tracking and basic rotation.
- Working Traccar server receiving data from TK-905B
- Basic rotation interface (linking beacon to car)
- Client access: viewing only their active vehicles on the map
- Route history playback function for a period
or
≈24 days: 22000–28000 UAH
Full-fledged platform with all management, reporting, and automation features.
- Complete rotation module with history of all links without data loss
- Geofencing system with automatic notifications in Telegram
- Detailed reports on parking and data export in Excel/PDF format
- Adaptive web interface for managers and clients (Mobile/Desktop)
- Configuration of old data cleaning policy for database stability
+additionally
≈10 days: 10000–12000 UAH
Maximum package with enhanced support and extended functionality.
- Priority support and assistance for 2 months after delivery
- Extended functionality of the admin panel for analytics across all companies
- Assistance in setting up and SMS commands for a large fleet of beacons
- Documentation and video instructions for each user level
Budget: 27000 UAH Deadline: 12 days
Hello! I will deploy Traccar on a VPS (I will recommend a configuration based on your number of beacons), set up the reception of TK-905B, and assist with SMS commands for redirecting beacons from the Chinese server. The key logic of rotation will be implemented as a separate layer on top of the Traccar API: the trip is linked to the actual issuance of the beacon, not to the vehicle, so the trip history remains accurate after the beacon returns to the pool. Multi-tenancy by roles: the factory only sees its active trips and history, the manager sees the issuance/receipt of beacons, and the admin sees everything. The frontend will be a real-time map with access segregation by companies.
Budget: 27000 UAH Deadline: 10 days
Good day!
I am a full-stack developer. Stack: Next.js, TypeScript, React, Node.js, Python, PostgreSQL/Prisma.
What I can do for you:
— websites and landing pages from Figma designs, responsive and SEO;
— online stores with integrations: CRM, Nova Poshta, online payments, product feeds;
— Telegram bots and Mini Apps (grammY, aiogram);
— AI integrations: chatbots, RAG agents based on your materials, Claude/OpenAI API;
— automation and parsing in Python (Playwright), working with APIs;
— WebGL / Three.js — interactive 3D scenes and shader animation;
— deployment and server setup: Docker, Nginx, SSL, backups, monitoring.
The code and access will be completely yours after completion. I work through Safe, in phases with clear deadlines and transparent communication. Languages: Ukrainian, Russian, English.
Please write the details of the task — I will provide an estimate and timeline and send examples of my work.
Budget: 27000 UAH Deadline: 10 days
Hello. I can take on the project and create a working platform based on your scheme with beacon rotation, so that the client sees not the device, but a specific route and vehicle, while the entire history of bindings is saved correctly. I will deploy Traccar on your VPS, configure the reception of TKSTAR TK-905B, assist with SMS reconfiguration of beacons, and create a separate logic layer for companies, roles, issuance, completion of routes, and returning beacons to the pool. I suggest implementing multitenancy not just through permissions in Traccar, but via a separate database and service over the Traccar API, so that clients only see their active routes and history, without access to free beacons and other people's data. I will create the frontend in React or Vue with a live map, search, vehicle card, route history, stops, and a convenient mobile interface for managers. For the MVP, I see the components as: logins, map, roles, rotation, route history, and report on stops. The full version will include geofences, notifications, report export, and advanced analytics. For 20-50 beacons, I would recommend a VPS with 2-4 CPU, 4-8 GB RAM, SSD from 80 GB, with extra space for storing tracks and backups. After delivery, I will provide all access, the repository, instructions for the admin and managers, and I can also take on support after launch.
Budget: 27000 UAH Deadline: 10 days
Hello! I will complete your task quickly and efficiently.
My recent works
https://indexfast.pro - fast website indexing
https://mono-bank.pp.ua - everything about Monobank
https://mamamia.pp.ua - online store
https://programist.pp.ua/ua/portfolio/ - portfolio of works
https://monitortest.pp.ua - monitor testing
https://keytest.pp.ua - keyboard testing
https://pctest.pp.ua - computer testing
https://devroman.dev/portfolio/ - portfolio
https://vseetut.matviy.pp.ua - layout
https://indexfast.pp.ua - fast website indexing
My portfolio: https://freelancehunt.com/ua/freelancer/romas6ka.html#portfolio
Write to me, I will start working today. I will be happy to collaborate with you!
Budget: 27000 UAH Deadline: 15 days
Good day
I am ready to implement this project and already have experience in similar cases. I can provide access to a demo of an already functioning SaaS, where this has been implemented by me. More details in private messages.
Feel free to write, we can discuss it, and I will be happy to collaborate!
Budget: 27000 UAH Deadline: 1 day
Hello!
I am ready to take on your project today.
I work quickly and accurately, bringing the result to the desired level.
I am open to discussing the details.
Portfolio: 
Behance
Budget: 27000 UAH Deadline: 1 day
Hello! I have experience in developing web platforms and integrating Traccar, working with Vue.js, React, and Leaflet. I would be happy to help you.
Budget: 27000 UAH Deadline: 14 days
I have over 5 years of commercial experience in web development. I work with React, TypeScript, Node.js, PostgreSQL, Docker, REST API, WebSocket, mapping services (Google Maps, Mapbox/MapLibre), and designing scalable web applications.
With Traccar, I am ready to quickly understand and build a custom service on top of its API without changing the core logic of the platform. I propose to implement the rotation module as a separate service with its own database, where the history of all trips, beacon attachments to cars, and companies will be stored. This approach will allow for safe updates to Traccar without losing our own business logic and maintaining complete history.
Budget: 27000 UAH Deadline: 16 days
Hello, Sergey! My name is Nikita, I am a programmer from VALFLOW. I will solve the task of beacon rotation so that there is no mess in the factory trip history.
We will set up Traccar as a reliable gateway for receiving coordinates from TK-905B, and all custom logic (“Beacon ➔ Car ➔ Trip ➔ Factory”) will be moved to a separate database on top of it. With this architecture, old tracks from previous clients will never intersect with new trips, even if the beacon changes drivers every day.
Answers to the questions from the technical specification:
Implementation: We will achieve multitenancy through filtering the Traccar API on the backend by company ID and timestamps of the active trip. Clients simply will not see free beacons from the pool.
VPS for 50 cars: A basic server with 2 vCPU / 4 GB RAM (Ubuntu) is sufficient. I will set up automatic cleanup of coordinates older than 6 months through a retention policy in Traccar, so the database does not bloat, but key reports on trips are preserved.
Timeline and cost:
MVP (live map, manager rotation logic, roles, parking): 10 days / 18,000 UAH.
Full version (+ geofences, notifications, export): another 6 days / + 9,000 UAH.
How do managers currently send SMS commands to the beacons (changing IP/port via admin123456)? We can automate this process directly from the admin panel. Let's discuss the details in the chat!
Budget: 27000 UAH Deadline: 30 days
Good day, we have been specializing in website development and promotion since 2018.
We have extensive experience working with various websites and online stores.
We perform high-quality technical SEO audits.
I suggest filling out the brief to create a commercial proposal for you.
Website development brief - https://lionex.com.ua/s/brief-na-rozrobku-saitu
Online store - https://lionex.com.ua/s/brief-na-internet-magazyn
Landing - https://lionex.com.ua/s/brief-na-lending
SEO - https://lionex.com.ua/s/brief-na-seo-audyt
We also offer a cool platform for quick text rewriting - https://textory.com.ua/go/kFoMHu3N
You can also check out our work on the website. If you have any questions, feel free to reach out, and we will gladly provide consultation.
Budget: 27000 UAH Deadline: 15 days
Good day.
I am familiar with Traccar; here is the system running on the server - http://178.20.156.94/
I have practical experience in developing React and Node.js platforms, working with REST API, WebSocket, PostgreSQL, Docker, Linux VPS, user roles, and server access segregation. I propose to use Traccar as a separate telematics service for receiving and storing coordinates.
Multitenancy and rotation will be implemented in a separate Node.js service with PostgreSQL. The database will store companies, users, devices, trips, and beacon statuses. Reissuing automatically closes the previous trip and creates a new one without changing the old history. The client frontend will not have direct access to Traccar, and the API will return only the trips for the user's company_id.
Completing a trip and returning a beacon will be separate operations. After the trip is completed, the client will no longer see the beacon's further route, but the administrator will see its status, for example, returning, in the pool, or charging.
I propose to implement the frontend in React with Leaflet and OpenStreetMap. Live coordinates will be obtained via Traccar WebSocket with backup polling. I will create a separate mobile screen for the manager, where the beacon is searched by a short number, and the issuance takes a few actions.
The report on stops will be calculated based on an agreed speed threshold, allowable deviation radius, and minimum duration. For the TK-905B interval of five minutes, the same time error must be considered in the reports.
Raw coordinates older than six months can be deleted automatically. Before cleaning, the system will retain trips, stops, time in geozones, and summary indicators so that old reports remain accessible.
For the start, I recommend an Ubuntu VPS with 4 vCPU, 8 GB RAM, and 80 GB NVMe. This is sufficient for 20–50 beacons with a margin for Traccar, PostgreSQL, API, frontend, backups, and report generation. You can minimally start with 2 vCPU and 4 GB RAM if quick scaling is anticipated.
MVP for 27,000 UAH, approximately 2 weeks. It will include Traccar on VPS, connecting a test TK-905B, roles, companies, rotation, live map, mobile manager interface, track history, basic stop report, and retention.
Budget: 27000 UAH Deadline: 30 days
Hello! I see that the key difficulty here is not Traccar itself, but the correct logic for beacon rotation and maintaining trip history without mixing tracks from different vehicles. I suggest keeping Traccar as the GPS core, and building a separate backend on Node.js/Express with PostgreSQL and a custom frontend on Next.js: multi-tenancy, roles, issuing/returning beacons, binding history, map, tracks, and reports will be separated at the level of our own business logic. I am ready to implement an MVP with a map, authorization, and rotation, and then expand the system with geofences and reports; after reviewing the details, I will propose exact timelines and costs by stages.
Budget: 27000 UAH Deadline: 23 days
I will respond point by point, honestly and directly:
**1-2. Experience with Traccar / custom frontend on top of it:** I haven't worked directly with Traccar, but I have relevant experience: consuming REST/WebSocket API in conjunction with Django/FastAPI backend, React on the frontend (I created live-updating interfaces for a desktop application), Docker/VPS deployment. Traccar is well-documented and built around REST API — the risk for me is minimal, but I speak honestly, not pretending.
**3. Multitenancy and rotation (architecture):**
Multitenancy is a separate layer on top of Traccar: its own database with Company/User/Role tables, and middleware/API gateway that filters Traccar device data by the company of the logged-in user before it reaches the frontend — the client never interacts with Traccar directly. Rotation is a separate Assignment table (device_id, car_number, driver, company_id, start_ts, end_ts=NULL while active). Issuing a new route to the same beacon = closing the current record (end_ts) + creating a new one. Historical tracks are linked to the car through a join by the time range of the assignment, not directly by device_id — this way, old points remain permanently associated with the car that was active at the time of their recording. The free pool = devices without an open assignment.
**4. Timelines and price:**
(a) MVP (map, logins, rotation, parking) — **15-17 working days, ~30,000-33,000 UAH**
(b) Full version (+ geofences, reports, export) — **+7-9 days, total ~44,000-48,000 UAH**
I note: the amount indicated on the card, 27,000 UAH, seems closer to the budget for the MVP part, while the full version is significantly larger in scope.
**5. VPS configuration for 20-50 beacons:** Traccar is lightweight, with updates every 5 minutes — this is very low load. 2 vCPU / 4GB RAM / 60-80GB SSD will be sufficient (with a margin for Postgres nearby and database growth). This level costs $20-24/month at Hetzner/DigitalOcean.
Budget: 27000 UAH Deadline: 14 days
The key complexity is rotation. In Traccar device, it is an entity with one name: if you overwrite the car number, the old tracks will be retroactively signed with the new one. Therefore, the car number cannot be kept on the device.
The solution is our own service and our own database on top of Traccar. The trips table: beacon, car, driver, direction, company, started_at, ended_at. Reissuing closes the current row and inserts a new one; no record is edited. The track of the trip is a slice of positions by device_id over an interval. The status of the beacon (in trip / returning / in pool) is a separate field, so closing the trip and returning to the warehouse remain different actions.
Multitenancy is also through our backend, and there is a technical reason for this: the Traccar websocket is authorized only with the JSESSIONID cookie; it does not accept the token in the header — connecting directly from the client’s browser will not work. My service maintains one admin session, listens to the Traccar socket, and distributes a filtered stream of car numbers instead of device IDs to each factory.
I am not writing parking and geofences from scratch — I take ready-made reports/stops and geofences from Traccar, with a filter by company on top. Retention is handled by an external cron script, in batches, skipping the last position of each beacon; trip summaries are aggregated upon closure, so old reports remain active.
Two things before purchasing a VPS. First: part of the TK-905B batches is locked to the TKSTAR server; the SMS adminip123456 goes through, but the data still goes to China — we need either firmware or a letter to the supplier. Second, and this directly affects the parking report: the TK905B has sleep mode based on the vibration sensor. The truck has stopped for unloading; after 5 minutes, the GPS is muted — and instead of "stopped for 49 hours," you see "no connection." The sleep mode needs to be switched to a timer and incorporated into the status logic.
VPS: 2 vCPU / 4 GB RAM / 60 GB NVMe, Ubuntu 24.04, PostgreSQL instead of the default H2.
I will not show a public case specifically on Traccar. I offer something more useful than screenshots: I will raise an instance on my end; you provide the IMEI of one beacon — and I will show a live map with working rotation, including reissuing and saved history.
Other details did not fit within the response limit — write to me privately, and we will discuss.
Budget: 27000 UAH Deadline: 18 days
Good day! I am interested in your project. I am a Full-stack developer and ready to implement a monitoring system based on Traccar. I propose an architecture where the Traccar server acts as the engine for processing GPS data, while a separate web service on Django handles the logic of beacon rotation, role management, and secure data separation between clients.
Technical implementation:
1. Backend: Python (Django) with integration through the Traccar API to obtain current coordinates and manage device states.
2. Database: PostgreSQL - for storing rotation history, beacon-to-vehicle bindings, and trip reports.
3. Frontend: React(js) - for creating a fast, responsive interface with an interactive map and real-time data updates.
Timelines and costs:
MVP (map, logins, rotation, parking reports): 20,000 UAH, implementation period 15–20 days.
Full version: functionality for geofences and extended reports will be discussed after the MVP launch.
We can discuss all the details in private messages - I would be happy to collaborate!
Budget: 27000 UAH Deadline: 15 days
I read the description carefully, the task is clear and interesting.
I have about 3.5 years of experience in fullstack development, with a stack of TypeScript, React, NestJS, PostgreSQL, which matches exactly what is needed here. I have worked with Traccar in the context of integrations via API, so figuring out the deployment on VPS and setting up the protocol for TK-905B is not a problem.
The key logic of beacon rotation, where the unit of account is the flight, not the device, is essentially a task for proper data modeling. The beacon is tied to the flight upon issuance, the flight is closed upon return, and the next issuance opens a new flight with the same device. I will implement multi-tenancy (each factory sees only its own data) at the middleware level and scope in the database, without workarounds.
The frontend on React with Leaflet and real-time updates via WebSocket or polling to the Traccar API will be clean and understandable for managers and clients.
I am ready to discuss the details, clarify the requirements for roles, and start with the backend architecture.
Budget: 27000 UAH Deadline: 25 days
Hello!
I have reviewed the full specifications - the task is clear.
1. Yes, I deployed Traccar on a VPS, configured data reception from beacons, and created a custom frontend on top of the Traccar API.
2. I will implement multi-tenancy as a separate service on top of Traccar with its own database. The rotation module will be a separate table of routes that stores the history of beacon-vehicle bindings without recording through Traccar attributes.
3. For 20-50 beacons, a VPS with 2 CPU, 4 GB RAM, and 50 GB SSD (Hetzner CX22 or equivalent) is sufficient.
I am ready for discussion.
Budget: 27000 UAH Deadline: 30 days
Good day.
I am ready to take on the web platform for tracking with the rotation of GPS beacons (TKSTAR TK-905B) on top of Traccar.
Portfolio: https://gooru-lab.github.io/portfolio/
How I see the solution:
• Traccar on your VPS — receiving coordinates from TK-905B, track history, WebSocket/REST.
• A separate layer (service + DB) on top of Traccar: companies, users, roles, beacon rotation, trips, map signatures (vehicle number / direction), reports on parking and geofences. Traccar will only handle the "hardware and points," while the business logic will be in our layer (to ensure that the history of bindings is never overwritten).
• Frontend: React + Leaflet/OSM, Ukrainian, responsive; the client sees only their active trips.
Answers to questions:
1) Have you deployed Traccar?
I do not claim a production case specifically for Traccar in my portfolio. I have experience with VPS/Docker, backend API, maps, and monitoring. I will deploy and configure Traccar for TK-905B (protocol out of the box) and assist with SMS forwarding from the Chinese server to yours.
2) Custom frontend on top of Traccar API?
Yes — React (or Vue) on REST + WebSocket/polling. Examples of UI/fullstack: https://gooru-lab.github.io/portfolio/ and live demo from the portfolio. I can show screenshots of the Traccar wrapper at the prototype stage of the map + login.
3) Multitenancy and rotation (briefly):
• Companies and users — in our DB; we only return device/trips of their company in the API to the client.
• The beacon has a short number (sticker) + id in Traccar; statuses: in the pool / issued / trip closed (returning) / charging, etc.
• Issuance = new Trip (beacon, vehicle, company, optionally driver/direction) + binding to Traccar device; on the map, a signature from Trip, not raw device id.
• Reissuance = close old Trip + open new; tracks are always read through the history of Trip→vehicle for the period (overwriting the number is prohibited).
• Completing the trip and returning to the pool — two actions; we do not show the return path to the client after close.
• Admin sees everything; manager — issuance/reception; client — only their active trips + their history.
4) Timeline:
(a) MVP (Traccar, logins/roles, rotation, live map, trip signatures, parking, track history, retention of 6 months for raw points / saving trip summaries): approximately 3–4 weeks.
(b) Full version (+ geofences, reports on zones, notifications in UI; Excel/PDF and e-mail/Telegram — by agreement): an additional 2–3 weeks.
Support for 2–4 weeks after delivery — separately / in a package, as we agree.
5) VPS for ~20–50 beacons (guideline):
• 2–4 vCPU, 4–8 GB RAM, 40–80 GB SSD NVMe, Ubuntu LTS.
• Docker: Traccar + PostgreSQL + our API + frontend (nginx).
• For starters, 2 vCPU / 4 GB / 40 is sufficient.
Budget: 27000 UAH Deadline: 27 days
Good day, I have been working in web programming for over 9 years. I work with REST APIs, frameworks, and CMS such as Django, Laravel, Yii2, WP, OpenCart, CodeIgniter, etc. I am ready to complete the task. Reviews: Freelancehunt
Budget: 27000 UAH Deadline: 1 day
Hello, I completed a similar project for Tbutech.
Feel free to message me privately.
I would be happy to help you!
Budget: 27000 UAH Deadline: 20 days
Hello ⭐️! I am a highly qualified web developer with over ✅ 7 years of experience in development and modern web technologies.
Recent projects:
✔️https://homenly.com
✔️https://confidence-tech.com
✔️https://homexcrm.com
✔️https://omgfirms.com
✔️https://skyhigh-lviv.com/
✔️https://sweet-sdpearls.de/
✔️https://novobudova.pro
✔️https://aquahub.org.ua
✔️https://boostylabs.com
✔️https://ol.zp.ua
✔️https://emporio-sports.cz
My stack includes:
✅ Frontend: HTML, CSS, JavaScript, React.js, Vue.js, Angular
✅ CMS: Wordpress(woo), OpenCart, Prestashop, Webflow
✅ Backend: PHP, Laravel, CodeIgniter, Python, Django, Flask, Node.js, Next.js
✅ Databases: MySQL, PostgreSQL
✅ Other skills: Git, API integration
Why choose me?
✔️ Fast and quality execution: Your tasks will be completed on time and with impeccable quality.
✔️ API integration: Need seamless integration of third-party APIs? I will take care of that.
✔️ Custom solutions: I take your ideas and turn them into successful web solutions tailored to your business needs.
Let's collaborate and create something amazing together!
Budget: 27000 UAH Deadline: 60 days
Hello! The project is clear, we are ready to implement it.
We do not have a direct public case on Traccar, but we have experience in developing monitoring systems, server integrations via REST/WebSocket, and custom web interfaces.
We suggest using Traccar only for receiving and storing GPS data, while companies, roles, flights, and rotation will be implemented as a separate service with PostgreSQL. Each issuance of a beacon creates a new binding with start and end dates — old flights are not overwritten. Multitenancy is ensured at the backend level: the client receives only the flights of their company and does not have direct access to Traccar.
Preliminary estimate:
— MVP: 6–8 weeks, $6,000–8,000;
— full version: 10–12 weeks, $10,000–14,000.
VPS: 4 vCPU, 8 GB RAM, 100 GB NVMe, Ubuntu LTS with automatic backups.
Examples of work: https://lvl1dev.com/projects
I suggest discussing the details and final estimate in private messages.
Budget: 26000 UAH Deadline: 15 days
The main challenge of this project is not the map or Traccar, but the logic of rotation: if we simply overwrite the car number on the device during issuance, old tracks will quietly be signed with foreign numbers. Therefore, the unit of accounting should be the trip, not the beacon itself — and this is the foundation of the entire architecture.
I see that your TKSTAR TK-905B beacons transmit coordinates every 5 minutes, operate on a pool scheme (issued → received → reissued), and client factories should only see their active trips. Free beacons are not shown on the client map — this is filtering by trip status, not by device.
Regarding your questions:
I deployed Traccar in production — standard stack Ubuntu + Java + PostgreSQL, the TK-905B protocol is supported out of the box. I will help with redirecting beacons via SMS commands to your server.
I have created a custom frontend on top of the Traccar API — React + Leaflet, WebSocket for live coordinates, multi-tenancy with roles. No fictional cases: I have specific experience.
I propose to separate multi-tenancy and rotation into a separate layer (Node.js + PostgreSQL) on top of the Traccar API. Tables for companies, users with roles, devices, trips. Reissuing = closing the old trip + creating a new one. Traccar is only called for raw coordinates by device_id — all visibility logic is in your layer.
Regarding the stages: MVP (Leaflet map + OpenStreetMap, logins and roles, rotation module, parking tracking) — about 60% of the budget. The full version with geofences, Excel/PDF reports, and track playback — the entire budget. I recommend a VPS with 4 CPU / 8GB RAM / 80GB SSD for 20–50 beacons — it will be more than enough.
After delivery, I won't disappear — I will remain available for edits, updates, and improvements without additional payment. I am currently completely free, starting today: first, I will deploy Traccar on your VPS and set up data reception from TK-905B, then I will prepare a prototype of the rotation module. Write to me — and I will outline the plan for the first stage.
Budget: 27000 UAH Deadline: 30 days
I am a NextJs, React, NestJs developer. I am ready to take on this task.
Budget: 27000 UAH Deadline: 7 days
Good day! I have reviewed the project description. The task is clear: it is necessary to deploy Traccar and build a separate web platform on top of it, where beacons can be quickly issued for new trips, and clients will only see their vehicles and route history.
Please write to me privately, and we can discuss in more detail.
Answers to your questions:
1. I have not worked with Traccar in production before, so I will not claim otherwise. At the same time, I have practical experience with GPS and geolocation, maps, WebSocket, multi-role systems, Docker, Linux servers, and full-stack platform development on Vue/Nuxt, React, Node.js/NestJS, Laravel, and PostgreSQL. Most commercial projects are under NDA; my profile is available at: m1davp.github.io.
2. I suggest using Traccar for receiving and storing coordinates, while companies, users, trips, statuses, and rotation can be implemented in a separate NestJS service with PostgreSQL. Each issuance of a beacon will create a new trip with its own binding period to the vehicle. Reissuing will automatically close the previous binding, so old routes will not lose the correct vehicle numbers.
3. The client frontend will receive only data from their company through a separate API, without direct access to Traccar. Coordinates older than 6 months can be automatically deleted while keeping trips, stops, and summary reports.
4. I propose to implement the frontend on Vue/Nuxt with Leaflet and OpenStreetMap. For 20-50 beacons, a VPS with 2 vCPU, 4 GB RAM, and 80-100 GB NVMe is sufficient. For additional capacity for reports and further scaling, I recommend 4 vCPU and 8 GB RAM.
Budget: 27000 UAH Deadline: 14 days
Hello 👋
I have reviewed the task 👀 It's an interesting project, and I am currently working on a somewhat similar project - tracking employees of a company (180 employees).
Please write to me, and we will discuss the project details because I am interested!
Example: https://sushi-drive.mk.ua
https://ealcoach.com
https://ms.mk.ua
----------------------------------
Website development in Wordpress / OpenCart and AI automation.
Budget: 27000 UAH Deadline: 1 day
Good day!
In general, the task is clear, but to provide an accurate response regarding the deadlines and price, I would like to clarify some questions that arose after analyzing your task.
Please write in private messages – we will discuss the details and your wishes.
Budget: 27000 UAH Deadline: 15 days
Worked with Traccar and custom frontends on React + Leaflet. For beacon rotation, it makes more sense to move the logic to a separate service with a database - this is easier to scale and won't break Traccar. Regarding the budget: 27k UAH will only cover the MVP with a map, logins, and basic rotation, without geofences and reports. What is the priority for functionality, and are you ready to discuss phased delivery?
Budget: 27000 UAH Deadline: 14 days
Sergey, I see the need for a system where the main challenge lies in the logic of reassigning trackers between different trucks and restricting access for clients. Since the beacons circulate between vehicles, it is important for us to automate the process of changing the object so that the factories see the current transport for a specific route. I will set up the server part of Traccar, assist with the selection of VPS configuration, and ensure data transfer from the Chinese server. In the end, you will receive a control panel with restricted rights and correct binding of trackers to current shipments. How do you plan to transmit information about which specific tracker is issued to the driver at a given moment so that the system automatically updates the data for the necessary factory?
