# Communities

Clusters is the best way to issue usernames to your community. A community like *treasure/* can issue thousands or even hundreds of thousands or free and paid usernames like *treasure/karel*, *treasure/yuri*, *treasure/foobar*. There are three key advantages:

<figure><img src="/files/dJPfUsMFN5KXycDR6xVF" alt=""><figcaption></figcaption></figure>

* **Brand Awareness -** cluster names are visible across leading block explorers like Etherscan, wallets like Metamask, and bridges like LayerZero
* **Clean Aesthetics** - it looks way cleaner to have *treasure/karel* than karel.treasure.eth.
* **Make Money -** communities can combine a free or a paid approach and earn from both community name signups and upgrades to personal clusters
* **Fastest Launch** - no need to develop or deploy your own smart contracts, we take care of it all with a white-label solution

**Community Cluster**

<div align="center"><figure><img src="/files/E2C5X6B0bW44IX4wNvQ8" alt="" width="563"><figcaption></figcaption></figure></div>

**How do I set it up?**

We provide a flexible settings panel where you can choose community images, names, payment currency, pricing, and more. We provide a simple default interface that users can register on our site but expect to work with partners to set up a seamless experience on their community website.

<div align="center"><figure><img src="/files/8X5oTFGrqx29fyaeoHLH" alt="" width="563"><figcaption></figcaption></figure></div>

**What's the technical architecture?**

Clusters takes an appchain approach for both decentralization and scalability. Cluster names are decentralized digital assets, and full cluster configuration is replicated onto a data availability layer (currently Arweave) so that full protocol state can be permissionlessly indexed and replicated by anyone. However most integrators and community partners interact solely with our REST/JavaScript APIs for simplicity. Community name registration can be done either offchain via API (for free names) or onchain via smart contract call (for paid names).


---

# 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://docs.clusters.xyz/introduction/features/communities.md?ask=<question>
```

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.