# Introduction By using the Orbis SDK, developers can build their own decentralized social apps or add a decentralized social layer to their existing application in a very easy and performant way. ### Why you should build on Orbis Orbis offers many advantages to developers interested in building decentralized social applications: * No transaction fees * Users don’t have to sign a message for each action they take * Write times are very fast which offers a user experience similar to web2 * Every piece of content shared on Orbis is decentralized on the Ceramic network and anyone can access it * There is a full composability between apps built on the Orbis ecosystem * Our SDK makes it extremely easy ti get started * *(Coming soon)* Multi-chain: Users can join Orbis using additional chains such as Cosmos or Solana and interact together in the same digital space ### Use cases Here are some examples of applications that could be built on top of Orbis: * Full social apps like [orbis.club](http://localhost:3001/) * Decentralized & encrypted messaging system * Fully customizable & embedded group chat servers * Decentralized Discourse governance forums * Decentralized support system (similar to Intercom) * Decentralized version of Slack * Decentralized commenting features * And many other things... ### Next steps Let's get started now! For the next steps we recommend exploring our Github repositories to learn more about Orbis' architecture or directly get started by installing the Orbis SDK. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.orbis.club/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.