What is DIMO
Last updated
Last updated
DIMO (pronounced "Dee-Moe") makes every car on earth smart and programmable. It's an open platform, providing the easiest and most trusted way to connect. It opens access to vehicle data (e.g, speed, location, fuel, engine), connectivity (e.g., lock/unlock, ignition), and commerce (e.g., payments, titles, registrations).
Drivers and fleets access innovative apps, services, and rewards for their cars. Car that are 2008 or newer in a supported region can connect today here.
Developers and enterprises build next gen mobility products with unmatched connectivity, distribution, and control. Developer docs are here.
You may be asking, "what does a smart and programmable car do?" Well, what if buying a new car were as easy as booking an Uber? What if your insurance premium was as data driven as your Instagram algorithm? When cars have universal digital identity and are accessible and secure online, we'll see: an AI car mechanic in your pocket; a smart parking garage that sends directions to your car to park autonomously and pay for itself; a fully automated and onchain DMV; and so much more.
Recently made possible by advances in cryptography, blockchain, cellular networks, and automotive tech, DIMO enables any business to build and integrate with the next generation of mobility applications without typical SaaS platform risk.
DIMO uses the the Ethereum Virtual Machine (aka blockchain), cryptography, open source software and hardware to establish vehicle identity, permissions to access data and controls, rewards, and more. The blockchain allows DIMO to offer openness, privacy, security, and performance guarantees that were previously impossible.
Nodes connect to cars, store offchain data, and validate that data to ensure accurate data is kept secure and only shared with those the user authorizes.
Apps and services pay nodes to access vehicles that have been shared with them, allowing them to build novel products.
For more technical details on the protocol, check out . For developer documentation, see .