EU transport company bankruptcies in 2025 ran nearly 80% above the 2021 base year. This is a structural shake-out, not a blip.
Every move.Connected.
The people, agreements and evidence behind every journey. Connected from the first quotation to the last mile—and everything that follows.
One industry.
A shared operating frame.
One connected ecosystem: freight, visibility, trust, carbon and finance.
An entire industry.
Finally, in sync.
Freight moves across borders. Information should move with it. TrustedTrucks connects the people and processes behind European logistics in one permissioned network, from the first quotation to the final proof of delivery.
Freight, visibility, trust, carbon and finance, held in the same frame.
Explore the freight workflowA vast industry.
Unevenly connected.
Logistics moves the world’s goods, yet the people who physically move them hold the least information and the least leverage.
Enormous, and still fragmented.
Logistics is one of the largest industries on earth and it keeps growing. Its size has not made it coherent: the work is spread across a very long tail of independent providers and incompatible systems.
- $8.2tnprojected market size by 2034
- 7.2%compound annual growth cited for 2026
- €208.1bnfreight forwarding market, 2025
Market figures are taken from TrustedTrucks’ SENRA market analysis (June 2026). Forward-looking values are projections, not forecasts made by TrustedTrucks.
Built for the many.
Not only the largest.
Small and medium-sized operators are most of this industry. They create operational, data and environmental value, and today they capture very little of it.
For smaller carriers, reporting and compliance are a growing operating cost. Larger players spread that cost across scale; an SME carries it on far thinner margins.
Many operators still work manually, or run isolated tools that are incompatible with their partners’. The software meant to help adds administration instead.
Input costs keep climbing while spot rates are compressed by overcapacity and aggressive platform pricing. It is a classic margin squeeze.
They deliver the freight, but are price-takers.
They generate the data, but the platform keeps it.
They cut the emissions, but cannot account for them.
Seven outcomes.
Each one traced to lifecycle stages.
Move freight
Find work, quote on structured requests and execute against a clear agreement.
STAGES 11–25 · 28–32 · 36–52 · 56–65Get paid faster
Delivery acceptance flows into entitlement, invoice, approval and payment.
STAGES 64 · 67 · 71–72 · 83–97Access finance
A finalised receivable carries its own evidence for factoring and trade finance.
STAGES 9 · 16 · 18 · 24 · 70 · 85 · 89Manage carbon
Activity data and methodology stay attached, so a footprint can be accounted for.
STAGES 26–27 · 35 · 53–54 · 77–80 · 99–100Reduce risk
Exceptions, claims and disputes keep their own states and evidence.
STAGES 17 · 43–49 · 62 · 68 · 73 · 76 · 81–82Grow the business
A verifiable track record that belongs to the company that earned it.
STAGES 6–7 · 14 · 34–35 · 54–55 · 60 · 75 · 101Preserve independence
Data sovereignty and portability: export everything, leave with your record.
STAGES 0–8 · 98 · 102–104A design rule of the constitutional kernel: every mechanism must trace to at least one commercial outcome for an SME. If it cannot answer “how does this help an SME?”, it should not exist.
Many roads.
One network.
From a port in Rotterdam to a warehouse in Berlin. Bring the people, capacity and information behind every movement together.
Different roles.
Shared momentum.
Your freight. Your visibility.
Connect transport requirements, carrier quotations and delivery evidence. Keep a clearer view of your freight and its carbon footprint.
- Structured freight sourcing
- Shipment and delivery visibility
- Scope 3 carbon context
Why join
TrustedTrucks?
Because the network is built so that taking part does not mean giving up control of your freight, your data or your margin.
- 01
One record, quotation to payment
The request, the agreement, the journey, the proof of delivery and the invoice stay connected, so nobody re-keys the same shipment into five systems.
Everyone - 02
Your data stays yours
Information is shared by contract and purpose, not by default. You can export all of your data and take your record with you.
Data sovereignty - 03
Paid on evidence, not on chasing
Accepted delivery evidence feeds the entitlement and the invoice directly, which shortens the distance between arriving and being paid.
Carriers · Forwarders - 04
A fuller truck on the way home
Backhaul matching looks for freight that fits your vehicle and corridor, turning an empty return leg into a paid one.
Carriers - 05
Carbon you can actually account for
Emissions reporting follows ISO 14083 and the GLEC Framework, with the activity data and method kept beside the result.
Shippers · Carriers - 06
Finance that can see the freight
Factoring and trade finance providers work from a finalised invoice and its delivery evidence, within a scope you grant.
Capital - 07
A real say in the rules
Governance weight follows the square root of a holding, and SME carriers carry a higher multiplier, so scale alone cannot decide.
Governance - 08
The platform is not your competitor
The operator runs the infrastructure and nothing else. It does not ship freight, run trucks, broker loads or bid on requests.
Neutrality
The whole industry.
In the same frame.
More than shippers, carriers and forwarders. An ecosystem that connects the organisations, specialists and economic relationships behind the journey.
Business profiles describe participation. Company authority, personal identity and purpose-bound external access follow separate participant capacities.
Different capacities.
Clear responsibility.
A shared network works when everyone knows the capacity in which they are acting.
Keep scrollingA foundation.
Not a counterparty.
Infrastructure, key custody and platform governance sit in a separate operator capacity. Operating the network does not grant authority over a participant’s commercial agreements.
- Platform operation
- Governed changes
- Bounded protective controls
A business.
Its own boundary.
The legal entity is the company tenant. Corporate agreements, records, engagements and custody belong to that organisation and its scoped authority model.
- Legal-entity identity
- Corporate agreements
- Company custody
One identity.
Explicit capacity.
People act personally as PT2RU or for a company as PT2MU through a current engagement and authority chain. Each consequential action has one acting capacity.
- Personal identity
- Bounded delegation
- Separate engagements
A purpose.
A defined scope.
External audit, regulatory disclosure, investor reporting and ecosystem services use purpose-bound access. A title or token holding does not create default access to freight evidence.
- Explicit purpose
- Scoped resources
- Time-bound access
No role, title or token holding implies authority outside its tier.
One action. One acting capacity.Delivery is a moment.
The lifecycle is bigger.
Know the participants.
Identity, business verification and capability qualification create the starting context for a commercial relationship.
- KYC / KYB
- Beneficial ownership
- Carrier qualification
Agree the journey.
Freight requirements, bids and carrier verification lead into the agreement. Finance, insurance and document-sharing permissions are bound to that context.
- RFQ & bids
- Agreement execution
- Route & stop booking
Prepare every handover.
Plan the load, stage the warehouse and bring export documents, security requirements and the carbon baseline into view before departure.
- Load sequencing
- Export clearance
- Carbon baseline
Keep movement in context.
Pickup, transit, backhaul opportunities, border crossings and exceptions connect to the same journey. Observations inform the record; they do not automatically decide acceptance.
- Transit monitoring
- Route recovery
- MRV data collection
Arrival needs an answer.
Capture delivery evidence and let the authorised counterparty determine acceptance under the agreement. Rejection, redelivery and disputes keep their own states.
- Proof of delivery
- Counterparty review
- Dispute context
Resolve the obligations.
Evaluate what the contract required and what the evidence supports. Satisfaction, breach and consequence rules provide the basis for the next financial step.
- Obligation assessment
- Consequence rules
- Finance reconciliation
Establish the entitlement.
Bring base freight, detention, demurrage and accessorial adjustments into the commercial position. Carbon and claims branches activate only where applicable.
- Freight entitlement
- Economic adjustments
- Claims resolution
Construct the financial record.
Publish the entitlement ledger, construct and audit the invoice, then finalise the receivable. Assignment, factoring and netting sit downstream of that record.
- Invoice audit
- Receivable assignment
- Settlement instructions
Approve. Pay. Reconcile.
Validate the settlement, obtain the required corporate approval and reconcile execution. Payment instructions and confirmations remain distinct events.
- Settlement validation
- Corporate approval
- Payment reconciliation
Close with a record that lasts.
Finality, applicable carbon transfer, data export and the governance archive bring the lifecycle to a durable close, preserving the evidence behind it.
- Composite finality
- Data portability
- Immutable archive
From intent.
To arrival.
One journey. A connected record. Every step carries the context of the last.
Explore the freight workflowThe right capacity.
For the right cargo.
Define the route, load and vehicle requirements. Bring qualified carriers into a structured quotation process, with the details everyone needs to make a decision.
A clear agreement.
A connected journey.
Confirm the carrier and transport terms. Keep the shipment, assignment and execution milestones connected in one shared operational record.
See the journey.
Understand the exceptions.
Follow location and cargo conditions as the shipment moves. Keep operational context alongside the route, so teams can respond with a clearer picture.
Delivered in the world.
Recorded in the network.
Connect proof of delivery to the shipment it belongs to. Preserve the signatures, documents and evidence needed for verification and the next financial step.
to a traceable record.
Every mode.
One request.
A request for quotation describes the cargo, the route and the terms once. Carriers quote against the same structured record, whatever the mode.
Open the RFQ simulatorWhere the network is deepest.
Define the corridor, the stops, the cargo and the vehicle. Qualified carriers quote against the same request, and the award becomes the transport agreement.
Milk runs, multi-stop routes and backhaul return legs build on the same request.
Road freight is the most complete workflow today. Ocean, air, rail and courier are selectable modes of a request; container-level detail such as FCL / LCL selection, port and airport pairs and chargeable weight is on the product roadmap.
Evidence should travel
with the agreement.
Working documents, admitted evidence and cryptographic commitments serve different purposes. Preserve the connection between them.
Where the movement is.
Coordinates, heading and geofences provide location context for a shipment.
Asset & locationWhat the cargo experiences.
Temperature, humidity and shock observations put cargo conditions alongside the route.
Cargo & environmentHow the vehicle performs.
Fuel, distance and mechanical observations can support operational analysis and emissions inputs.
Vehicle telemetryWhat the people do.
Dispatch, handover, document submission and review events preserve the human side of execution.
Operational workflowWhat needs attention.
Tamper indicators, security events and clearance records preserve exception context.
Security & complianceHow the connection holds.
Service health, device state and ingestion context help distinguish a missing signal from a missing event.
System meta & healthA signal is an observation. Acceptance is a decision. Evidence admission and contractual effects require their own evaluation.
Respect the context.ILLUSTRATIVE HASH
Working record
Drafts and submissions can evolve.
Authorised promotion
Admissibility and scope are evaluated.
Retained evidence
History and cryptographic commitments are preserved.
“Delivered” doesn’t
answer everything.
Evidence, review, acceptance, dispute, settlement hold and anchoring must not collapse into one flag. A challenge can coexist with acceptance.
Simplified architecture example.Delivered is not paid.
Close the loop.
The invoice follows from the entitlement, the entitlement from the agreement and the accepted delivery. Each financial step keeps that chain attached.
Open the payment simulatorWhat is owed?
Start with the agreement, the obligation outcome and the applicable commercial adjustments such as detention and demurrage.
Built from the record,
not re-typed.
Base freight, detention, demurrage and accessorial adjustments form the commercial position. The invoice is constructed and audited against it before it is finalised.
Two signatures
before funds move.
A payment release follows the company’s own signing route, for example an operating officer and a finance officer, with the approval recorded against the settlement.
A receivable
with its history.
Once an invoice is finalised, a finance provider can see the delivery acceptance and agreement behind it, within the scope granted for that purpose.
“Settled” is
too vague a word.
- 01Payment execution
An instruction is released through the bank.
- 02Funds movement
Money leaves one account and arrives in another.
- 03Funds finality
The transfer can no longer be recalled or reversed.
- 04Reconciliation
The books of both parties agree with what happened.
Freight is invoiced and paid in currency through banking rails. TTRUX meters platform usage; it is not a settlement instrument. The flows shown are architecture descriptions and simulator behaviour, not a statement of live payment volumes.
Two tokens.
Two different jobs.
One pays for the work the network performs. The other carries a say in how the rules change. The architecture keeps them apart.
Pays for the work
the network performs.
Platform services are metered and debited in TTRUX from the company treasury wallet. It stays an operating instrument, separate from freight invoices and from any say over the rules.
- Micro-metered service debits
- Held in corporate custody
- Supply bounded by protocol rule
Carries a say
in how the rules change.
Voting weight follows the square root of a holding, so scale alone cannot decide an outcome. Verified operations create eligibility for stewardship grants, released on a vesting cliff.
- Voting weight = √ holding × multiplier
- 5,000 GOTTT to bring a proposal
- 2-day timelock delay before an approved change executes
Spend ≠ governance. Spending euros or TTRUX never buys voting power.
Scale alone
cannot decide.
Drag the holding. Weight grows with its square root, so a holding four times larger carries only twice the weight. A proposal also needs breadth across independent entities, not one large vote.
- Holding
- 250,000 GOTTT
- Voting weight
- 500
Corporate custody.
Company obligations, commercial funds and corporate signing policy belong to the organisational custody path.
Personal identity.
Personal rewards, permitted governance and portable identity remain separate from corporate liabilities and binding authority.
Capital in context.
Trade finance, factoring and insurance connect to the invoice, the entitlement and the evidence behind them.
This section describes the governed token architecture. It is not an offer, a solicitation or investment advice, and it makes no statement about value.
Every kilometre
should count.
An empty return is a missed connection. Backhaul matching brings available capacity and freight together, making better use of the journeys already happening.
Explore the concept. Illustrative capacity, not an emissions calculation.- 01
Corridor scanning
As a vehicle approaches its delivery point, open requests nearby are checked against its equipment profile.
- 02
Triangulation
Where no direct return exists, a three-point itinerary is considered, within EU driver rest-time rules.
- 03
Avoided empty kilometres
The difference between two separate journeys and the combined one is quantified on a GLEC Framework basis.
Direct match
The carrier or forwarder already knows the return load and declares it against the forward order.
Platform match needed
The return capacity is published and the network looks for freight that fits the vehicle and the corridor.
Start with the activity.
Fuel, distance, cargo and transport-chain context provide the input basis under ISO 14083:2023 and GLEC Framework v3.2. Data quality and methodology must remain visible.
Architectural methodology references describe the reporting workflow. They are not a claim of external certification or guaranteed emissions savings.
Complexity underneath.
Continuity above.
- 01 / ExperienceCommercial workflows
Freight, participants, evidence and finance.
- 02 / ServicesContext & decisions
Identity, agreements, permissions and business rules.
- 03 / EventsOrdered information
Domain event streams, schema validation and replay context.
- 04 / RecordsOperational memory
PostgreSQL records and off-chain document storage.
- 05 / CommitmentsPermissioned ledger
Cryptographic commitments and governed contract execution.
Trust isn’t a promise.
It’s a shared record.
Commercial entities have ledger representations. Cryptographic commitments connect digital records to their evidence, while legal authority and contractual acceptance remain separately evaluated.
Inside the infrastructureRules that give
the network its shape.
The architecture is guided by governance, sovereignty, anti-extraction, due process and portability.
- 01Governance
Consequential changes need an accountable route.
Decisions retain their source, rule version and the evidence supporting them.
- 02Sovereignty
A shared network preserves individual boundaries.
Contract participants and delegates receive the information necessary for their scoped purpose.
- 03Anti-extraction
Participation should not surrender control.
Commercial data and economic participation remain subject to explicit rights and boundaries.
- 04Due process
Exceptions deserve an answer, not a hidden overwrite.
Challenges, reviews and historical evidence remain visible within the authorised record.
- 05Portability
The record should be able to move with you.
Data export and replayable context are part of the lifecycle architecture.
These are design commitments. A deployed capability requires its own scoped tests and retained evidence.
The details
matter.
01Is TrustedTrucks just a freight marketplace?
The platform context extends beyond freight discovery to participant scope, execution, evidence, financial construction, carbon reporting and governed records.
02Are all 17 profiles the same type of participant?
No. Business profiles describe the ecosystem. PT-1 companies, PT-2 people and purpose-bound PT-3 capacities have separate boundaries. Investor and token participation do not automatically grant commercial authority.
03Does telemetry automatically approve a delivery?
No. An observation can support evidence. Evidence admission, delivery acceptance, dispute, settlement hold and anchoring are separately governed states.
04Does holding a token give access to freight data?
No. Spending euros or TTRUX does not buy governance weight, and a GOTTT holding does not create commercial authority, signing rights or access to another participant’s records.
05Does blockchain replace the transport agreement?
No. The agreement and its applicable authority remain the commercial context. Ledger commitments preserve digital records; they do not independently create legal standing.
06Are the visual examples live operational data?
No. The map, routes, instruments, state previews, curves and hashes on this page are illustrative explanations of the architecture.
Bring your freight, your fleet, or your network.
There’s a place for you here.