DAT Load Board Clone Features: The Board Is Only the Entry Point
A listing site ends when the load is booked. This one starts there: the won load dispatches to a vehicle and a driver, tracks on GPS, collects a proof of delivery and raises an invoice against the same record. Underneath sits a real carrier TMS and broker-side intelligence, on 74 PostgreSQL tables and over 280 REST endpoints. Here is what ships, grouped by who touches it.
Request a Live Demo →See PricingFeature Set by Role
Four parties touch a load and each gets a surface built for what they actually do with it, all against one API and one record.
The Shipper
Posts a load with equipment, weight, commodity, distance and target rate, and attaches pickup and delivery legs as child records carrying sequence, dates, times, contacts and instructions. Multi-stop is a shape in the schema rather than a note in a comments field, and bulk upload from file covers a high-volume desk.
The Carrier
Searches and filters the live board by lane, date, equipment and distance, submits bids, runs counter-offers, bookmarks loads and sees bid statistics. Rate history and hot lane context sit at the point of decision rather than behind a separate subscription, which is where a carrier decides whether a rate is worth taking.
The Dispatcher
Assigns the won load to a vehicle and a driver, creates the route, and follows GPS positions with geofence alerts firing on arrival and departure. A public tracking link can be generated for a shipper or a consignee who has no account, which is what stops the where-is-my-freight call.
The Fleet Manager
Vehicles and drivers with hours-of-service logs, DOT compliance records, fuel purchases with IFTA reporting, maintenance scheduling, geofence alerts and speed violations. This is an operational backbone rather than a bolt-on, which is the difference between a load board and a system a carrier runs their week on.
The Broker
Carrier intelligence at the point of tender: fleet visibility, company verification, ratings and reviews, broker credit scores, rate history and hot lanes. The evidence needed to decide whether to route freight to a carrier sits next to the load rather than in another product.
The Operator
User lifecycle and role management, load intervention, KYC review queues, compliance records, financial overview with invoice ageing, platform analytics, module toggles, pricing plans and SEO surfaces, with audit and activity logs behind every admin action.
Members use a React web application and a 126-screen Flutter build; operators run the admin control plane. All three go through the same 280-plus REST endpoints.
DAT vs Miracuves Clone vs Building From Scratch
What each route gives you on the parts that decide whether freight actually moves through the system.
| What decides it | Miracuves DAT Load Board Clone | Building from scratch |
|---|---|---|
| Time to a working platform | Six working days | A multi-year programme with a senior team |
| After the load is booked | Dispatch, GPS, POD and invoice on the same record | Where most builds stop, and the reason they stay listing sites |
| Multi-stop lanes | Pickup and delivery child tables with sequence and contacts | Usually one origin and one destination, rebuilt later |
| Negotiation | Multi-round counter-offers with lost reasons, on the load | A phone call and a note somebody may have written down |
| Carrier TMS | HOS, DOT, fuel with IFTA, maintenance, geofencing | A separate product a carrier pays for elsewhere |
| Broker intelligence | Verification, ratings, credit scores, rate history, hot lanes | Another subscription, in another tab |
| Provider lock-in | Adapters with mock fallbacks, swapped by environment variable | Whatever was wired in first, permanently |
| Source code | Full source across web, Flutter and admin, yours | Yours, at the cost of building all of it |
DAT itself is the reference for what this category looks like at scale; it is not a product you can buy or self-host. The comparison that matters commercially is the second column against the third.
How It Works, End to End
One load, traced from posting through to an invoice, with every offer, position and document written down against the same record.
The load is posted with its real shape
Equipment, weight, commodity, distance and target rate on the load, with pickup and delivery locations as child tables carrying sequence ordering, dates, times, contacts and instructions. A three-stop lane is modelled as three stops rather than described in free text that nobody can filter or dispatch against.
Carriers find it by the terms that matter
The board filters by lane, date, equipment and distance. Rate history and hot lane context are available at the point of decision, so a carrier is judging a rate against what the lane has actually paid rather than against instinct.
The negotiation leaves a record
Standard bids plus multi-round counter-offers, with bid statistics, bookmarking and lost reasons. What was offered, by whom, and why it was refused stays attached to the load. On a brokerage desk that record is the difference between knowing your coverage costs and guessing at them.
The broker checks the carrier before tendering
Fleet visibility, company verification, ratings and reviews, and broker credit scores sit beside the load. Vetting from memory is how a brokerage ends up with a claim it cannot defend, and the evidence being one click from the tender is what changes that behaviour.
Won freight dispatches rather than disappearing
The load moves from posted to assigned, a vehicle and driver are attached, and a route is created. The status machine runs across posted, assigned, in transit, delivered and cancelled, so the state of a load is a field rather than a spreadsheet somebody updates when they remember.
It tracks, and outsiders can see it
GPS positions follow on the map with geofence alerts firing on arrival, and speed violations recorded against the driver. A public tracking link can be generated for a shipper or consignee without an account, which removes the calls that otherwise consume a dispatcher's afternoon.
Delivery closes the financial loop
Proof of delivery is uploaded and validated by MIME type and magic bytes rather than trusting the file extension, and an invoice is raised against the same load. Invoice ageing appears in the operator financial overview, so what is owed and how long it has been owed are one query rather than a reconciliation.
Every Feature Earns Its Place
Each module below exists because a freight platform stops working without it, not because a competitor lists it.
| Module | Why it is in the base build |
|---|---|
| Multi-stop child tables | Real lanes have more than two points. A schema that assumes one origin and one destination cannot dispatch, sequence or invoice a three-stop run. |
| Multi-round counter-offers | Freight is negotiated, not listed. Without rounds recorded on the load, the price history of your own coverage lives in people's memories. |
| Lost reasons | Knowing why a carrier refused is how a desk learns its lanes. A blank refusal teaches nothing and repeats next week. |
| Hours-of-service logs | A carrier cannot legally dispatch without them, and a platform that ignores HOS is a platform a carrier keeps a second system beside. |
| IFTA fuel reporting | Fuel tax reporting is a quarterly obligation. Capturing purchases as they happen is the only way it is not a week of reconstruction. |
| Geofence alerts | Arrival and departure detected automatically is what makes tracking useful rather than a dot somebody has to watch. |
| Public tracking links | The people who most want to know where the freight is are the ones least likely to have an account. |
| Magic-byte validation | A proof of delivery is a legal document. Trusting a file extension on a document that settles a payment dispute is not acceptable. |
| Broker credit scores | Carriers refuse loads from brokers who pay slowly. Surfacing that at tender is what keeps good carriers on your board. |
Company verification, ratings and reviews, KYC review queues and compliance records ship alongside these in the operator console.
The Technology Behind the Features
What the platform is actually built on, and what that means for the team who inherits it.
Why the adapter layer is the number that matters
Freight software is where integrations go to become permanent. A telematics provider, a rate index, a payment processor or a compliance feed wired directly into domain code becomes a dependency you cannot leave without a rewrite, and in this industry those contracts get renegotiated. Every external surface here sits behind an adapter with a mock fallback, which means the platform runs and demonstrates without any of them, and swapping one is configuration rather than a project.
The mock fallbacks are why the demo runs end to end without a single third-party account configured, and why your first deployment is not blocked on a vendor contract.
What Is Not Included in the Base Package
Named here rather than discovered after the invoice.
What needs your account, and what is a deployment decision
Every external provider is your own account. Payments, calls and SMS, voice transcription, inbound and outbound email, market rate data and regional compliance feeds all run on credentials you hold. The adapters and their mock fallbacks are built, so the platform works without them; live data does not arrive until you contract with the provider.
Market rate data is a subscription you buy. Rate history and hot lanes are modelled and surfaced at the point of decision. The underlying market rate feed is a commercial agreement with a data provider, and it is the one most likely to be assumed as included.
Telematics and ELD integration. HOS logs, geofencing and GPS positions are modelled in the platform. Connecting a specific ELD or telematics vendor is an adapter implementation scoped against that vendor's API rather than something already wired.
Regional compliance beyond the records. DOT compliance records, KYC review queues and IFTA fuel reporting are built as records and workflows. Filing to a specific authority, or a jurisdiction with its own submission format, is scoped work.
iOS. The Flutter build covers 126 screens. A native iOS release with its developer account, signing and review cycle is quoted separately.
The controls that are built are real: Passport with bcrypt on session auth, JWT bearer for the API, route-level role middleware, object-level ownership checks on every load, bid, message and document, and MIME with magic-byte validation on uploads.
See how Miracuves compares to agencies and freelancers
The deployment process, a modelled reference deployment for a mid-market brokerage, and what to check on the load model and the adapter layer before you hire anyone - on the Development Company page.
Frequently Asked Questions
Is this a load board or a TMS?
How are multi-stop lanes handled?
Do I need a market rate data subscription?
What stops one carrier seeing another's freight?
Can I change payment or SMS providers later?
Does the proof of delivery hold up in a dispute?
See a load go from posted to invoiced, live
Ask for the demo and we will post a multi-stop load, run a counter-offer round, dispatch it to a driver, fire a geofence alert and raise the invoice in front of you.
Explore the DAT Load Board Clone
Ready to run a freight platform you actually own?
Deploy in six working days with the board, the carrier TMS, broker intelligence and the operator console included, your adapters pointed at your own providers, and the full source on infrastructure you own.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by DAT Load Board.
“DAT Load Board Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to DAT Load Board, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the DAT Load Board website or applications.
DAT Load Board and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
