Set your own fee model
Users do not pay gas. The dapp sponsors execution and decides how it makes money, so onboarding is not blocked by a wallet prompt.
Use case: Dapps
The home of first-class dapps.
On Chromia, each dapp runs on its own blockchain. You pick the chain configuration and the fee model that fit the application, instead of living with whatever a generic L1 hands you.
Why dapps on Chromia
Build for the app, not the defaults.
A shared L1 makes every app fight for the same block space and pushes gas onto users. A dedicated chain per dapp removes both problems.
Everything lives on-chain
Program logic, metadata, and files all persist on the chain. There is no external database to run and nothing to keep in sync off-chain.
One chain per dapp
Each dapp gets its own chain, so speed stays consistent. Block space is never shared with an unrelated app having a busy day.
Real relational data
Rell gives you typed entities, foreign keys, and queries on-chain. Complex state is something you model directly, not work around.
A different model
Dream up dapps differently.
On most chains the user experience is expensive and awkward. People pay gas on every transaction, and the cost climbs as traffic grows. Chromia takes the way web apps are actually built and brings it onto a chain.
- →Relational schemas let a dapp work with complex data natively, no off-chain indexer required.
- →Sponsored fees mean a new user can start without holding a token first.
- →Performance holds up under load because no noisy neighbor shares your block space.
- →A full SDK and familiar patterns make building a dapp feel close to building a web app.
Community
Join the community.
270k users around the world are already part of the journey.
Community
Join the community.
270k users around the world are already part of the journey.