# Build with Domino (/docs/overview)



Domino runs the rules of your community program. It checks that members did what you asked, counts it once, and hands out the points and rewards they earned. You decide what the app looks like and what people do in it. For example:

* A referral race with a weekly leaderboard
* A launch quiz with prizes
* A selfie at your booth
* Posts about you on X
* Discord roles for your regulars

You can build it in Console, hand it to your developer, or work with a coding agent in your editor.

## Choose your starting point [#choose-your-starting-point]

- [Try it with your agent](/docs/start/agent) — Paste one prompt into Claude, ChatGPT, or Gemini and get a campaign on staging.
- [Create a new app](/docs/start/new-app) — Start with a private repository, a working app, and instructions for your agent.
- [Connect an existing app](/docs/start/existing-app) — Keep your code, login, and hosting. Add Domino where you need it.
- [Start from Scaffold-ETH 2](/docs/start/scaffold-eth) — Create an Ethereum dApp with quests, points and a leaderboard, and a quest that checks your contract.
- [Manage a project](/docs/use/projects) — Learn what you can change in Console.
- [Build as an agent](/docs/agents) — Discover the tools, supported features, and verification steps.

## Understand the core concepts [#understand-the-core-concepts]

Start with quests and members, then add the pieces your campaign needs.

| Concept                                      | What it's for                                                                          |
| -------------------------------------------- | -------------------------------------------------------------------------------------- |
| [Quests](/docs/concepts/quests)              | The things members do: answer a quiz, post on X, upload a photo.                       |
| [Members](/docs/concepts/participants)       | The people taking part, the accounts they proved are theirs, and their progress.       |
| [Marketing consent](/docs/concepts/consent)  | Whether each member agreed to marketing email, when, and the words they saw.           |
| [Points](/docs/concepts/points)              | What members earn and spend. A project can run more than one kind.                     |
| [Rewards](/docs/concepts/rewards)            | What members receive, from badges to Discord roles and merch.                          |
| [Leaderboards](/docs/concepts/leaderboards)  | Rank members by their points, and hand out prizes.                                     |
| [Referrals](/docs/concepts/referrals)        | Reward members for inviting friends.                                                   |
| [Campaigns](/docs/concepts/campaigns)        | Set dates, sign-up and who can take part for a group of quests.                        |
| [Groups](/docs/concepts/groups)              | Name a set of members, such as your VIPs, for quests, rankings and referrals.          |
| [Collections](/docs/concepts/collections)    | Put quests in order on a page of your app.                                             |
| [Trackers](/docs/concepts/trackers)          | Collect activity from outside your app, such as X posts and Discord messages.          |
| [UGC programs](/docs/concepts/ugc)           | Reward creators for their content and how well it performs.                            |
| [Analytics](/docs/concepts/analytics)        | Count your program's activity per day or week.                                         |
| [Project calendar](/docs/concepts/calendar)  | Set where days, weeks and months begin.                                                |
| [Test and live](/docs/concepts/environments) | The two copies of a project: one to try things, one for your members.                  |
| [Promotion](/docs/concepts/promotion)        | How what you built in test reaches live, reviewed by a person.                         |
| [Access](/docs/concepts/access)              | Who can do what: organization admins, project roles, and the keys apps and agents use. |
| [Hosted apps](/docs/concepts/hosting)        | Where Domino runs your app: previews, staging, and your live address.                  |

[Compose a campaign](/docs/composition) connects these pieces in a working welcome, referral, and weekly-ranking example. To start with one activity, [write your first quest](/docs/build/first-quest).

## What belongs where [#what-belongs-where]

| Owner    | Owns                                                                                             |
| -------- | ------------------------------------------------------------------------------------------------ |
| Your app | Its pages and how people interact with them.                                                     |
| Domino   | The recorded result: whether a quest is complete, what a member earned, and which rules applied. |

A project has separate **test** and **live** environments. Quests, their settings and other definitions change in test, where you build and try them. Live accepts operations, such as pausing a quest or awarding points, and [promotions](/docs/concepts/promotion) of test that a person approves. See [test and live](/docs/concepts/environments).

## Check the fit before you build [#check-the-fit-before-you-build]

[The capability map](/docs/reference/capabilities) lists what Domino supports, what you can compose, and what needs your own backend. For example, Domino can reward the person completing a quest and add a selective bonus for their inviter through a [referral program](/docs/build/referrals).

> [!NOTE] Looking for the automation builder?
> These guides cover the current Relay-based Domino product. The [legacy documentation](https://docs.domino.run/docs) describes the earlier automation builder.

[Outbound webhooks](/docs/concepts/webhooks) tell your own systems about member activity, such as a completed quest, through signed requests with retries and replay.