Questions,answered.

TrustedTrucks is the digital infrastructure for European freight: one permissioned network where shippers, carriers and forwarders work from the first quotation to the final proof of delivery and payment, with shared visibility, verified evidence, invoicing and carbon accounting.

TrustedTrucks is operated by Konfid.io GmbH, Schlüterstraße 55, 10629 Berlin, Germany. The operator runs the infrastructure and nothing else: it does not ship freight, run trucks, broker loads or bid on requests, so the platform is not your competitor.

Shippers, carriers, forwarders and the wider freight ecosystem. The network describes 17 business profiles, including logistics agencies, importers and exporters, trade finance, leasing and factoring providers, insurers and customs brokers. It is built for SMEs: owner-operators, small fleets and regional forwarders, not only the largest players.

No. It is a permissioned network that keeps the request, the agreement, the journey, the proof of delivery and the invoice of a shipment in one connected record, so nobody re-keys the same shipment into five systems.

Yes. TrustedTrucks for Android is on Google Play for forwarders and carriers: post loads, compare and send quotes, accept orders, approve proof of delivery, confirm invoices and follow every shipment.

Road freight (FTL, LTL, part truckload and groupage) is the most complete today. Ocean, air, rail, intermodal and courier and express can be selected in the same request format; the ocean and air detail is on the roadmap.

You do. Information is shared by contract and purpose, not by default. You can export all of your data and take your record with you.

Accepted delivery evidence feeds the entitlement and the invoice directly. The invoice is constructed and audited against the entitlement, approved through the company's signing route, and payment execution, bank confirmation and reconciliation are kept as distinct events.

As a vehicle approaches its delivery point, open requests nearby are checked against its equipment profile. Where no direct return exists, a three-point itinerary is considered within EU driver rest-time rules, and the empty kilometres avoided are quantified on a GLEC Framework basis.

Emissions reporting follows ISO 14083 and the GLEC Framework, with the activity data and the method kept beside the result, so a footprint can be accounted for from the order estimate to the proof-of-delivery actuals.

Yes. A finalised invoice carries its delivery evidence, so factoring and trade finance providers can work from it within a scope the participant grants.

They are the participant tiers. PT-0 is the internal platform tier, PT-1 an organisation, PT-2 a person working through an explicit engagement and role, and PT-3 purpose-bound specialist access. No role, title or token holding implies authority outside its tier.

No. The simulators show quotations, track and trace, payments, carbon audits, backhaul matching, fleet planning and business networking on synthetic data.

Register your organisation from the join link on any page. For help, open a request on the support page or write to support@trustedtrucks.com.

The platform context extends beyond freight discovery to participant scope, execution, evidence, financial construction, carbon reporting and governed records.

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.

No. An observation can support evidence. Evidence admission, delivery acceptance, dispute, settlement hold and anchoring are separately governed states.

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.

No. The agreement and its applicable authority remain the commercial context. Ledger commitments preserve digital records; they do not independently create legal standing.

No. The map, routes, instruments, state previews, curves and hashes on this page are illustrative explanations of the architecture.

The network has different command centres for different responsibilities. Companies oversee their commercial operations; individuals work in personal or delegated capacities; connected services operate within an assigned remit. The internal platform command centre supports the foundation beneath them.

PT0 is the internal platform tier: infrastructure, security, key custody and platform governance. It supports the network’s operation and is separate from the participant command centres. It is not a commercial workspace or a public board-member offering.

A PT1 company holds organisation-level authority. A PT2 person performs company work through an explicit engagement and role. Personal participation alone does not grant the authority to create freight commitments or approve company payments.

PT3 surfaces bring connected field-system context and specialist ecosystem work into view, including technical services, data stewardship, carbon evidence and assurance. The information and actions available depend on the service’s assigned scope.

Authorised participants can contribute to a shared commercial context while retaining separate responsibilities. Sharing a record does not mean every participant can see all data or perform every action.