We’re (3Box Labs) releasing the beta of ComposeDB on Ceramic: a decentralized graph database that combines GraphQL, reusable data models, and decentralized event streaming. You can find the docs at [<a href="https://composedb.js.org/docs/0.4.x/introduction](https://composedb.js.org/docs/0.4.x/introduction)" rel="nofollow">https://composedb.js.org/docs/0.4.x/introduction](https://co...</a>, or learn more at [<a href="https://blog.ceramic.network/composedb-is-live-on-ceramic-mainnet/](https://blog.ceramic.network/composedb-is-live-on-ceramic-mainnet/)" rel="nofollow">https://blog.ceramic.network/composedb-is-live-on-ceramic-ma...</a>.<p>In its current state, ComposeDB is focused on letting Web3 developers build fully composable applications: apps that share data models and data so they can scale together and deliver user experiences across platforms that aren’t possible with siloed databases. For example, building DMs that persist across multiple apps, reputation that aggregates across platforms, and content collaboration from multiple different interfaces.<p>For my involvement, I’ve joined the 3Box Labs team recently. 3Box Labs is responsible for creating Composedb and Ceramic, which is the protocol that ComposeDB leverages to deliver its functionality. I’ve been lucky enough to work on both parts in my time with the company. Previously, I was in the network security and web2 space, and started looking for something which can help move us to a decentralized internet, and hopefully to a place where users own their data. Bonus points, if whatever we build is more secure, and less prone to having my data leaked constantly.<p>Ceramic and composedb will hopefully provide the building blocks which allow dApps to be more easily built in Web3. Would love to know if you find the project interesting, what things you might want to build, or issues you have using the project.