Skip to main content
Use this page while completing /launch. The guided flow creates the repository, connects the required services, and deploys a working site to Vercel.
Guided launch flow from project details through connected services to a deployed prediction market

​
Before you start

Admin wallet

The wallet that will sign the setup request and become the first site admin.

GitHub account

The account or organization that will own the generated repository.

Vercel token

A token with access to the account or team that will host the project.

Reown project

A project ID used to enable wallet connections on the deployed site.

Step 1: Site + Wallet

Define the site and create its Kuest credentials.

Step 2: Connections

Connect the services used to build and host it.

Step 3: Deploy

Start the deployment and verify the result.

​
Step 1: Site + Wallet

Site name

Use the public name users should see on the site.
Connect the wallet that should become the first admin. One signature creates the Kuest credentials used by the site.
Add it only if you want a contact email saved with the generated API key.
Keep 0 unless support tells you to change it.
This signature does not move funds and the wallet does not need a balance. The connected address becomes the first admin wallet.

​
Step 2: Connections

GitHub

Connect the account or organization where the project repository should live.
Paste a Vercel token and let the form verify it. Get it from vercel.com/account/tokens.
If prompted, allow Vercel to import the repository from your GitHub account.
Paste the project ID used for wallet login. Get it from cloud.reown.com.
Choose Create new for an isolated production database. Reuse an existing project only when the environments are intentionally shared.

​
Advanced options

Use it only if you want a different project slug or final URL name.
Use the owner/repo format. This is usually filled automatically after GitHub is connected.
Keep main unless your production branch uses a different name.
Leave it empty for a personal Vercel account. Fill it only for team-owned projects.
Usually the default is fine. Change it only if you want a different region.
You can leave it empty and let the setup generate one automatically.
You can leave it empty and let the setup generate one automatically.
Fill it only if you already know the final public URL you want to use.
Use one KEY=value per line for optional services or runtime overrides.
Helpful pages: Environment Variables and Vercel + Supabase.

​
Step 3: Deploy

Deploy button

Starts the launch with your site name, repository, branch, database choice, and environment values.
Follow credential validation, repository setup, database connection, and deployment progress. If a stage fails, open its logs before retrying.
Shows the project URL, Vercel dashboard, Supabase dashboard, duration, and logs.
After install, go to General to set your brand, support link, fee wallet, and core settings.

​
Verify the launch

1

Open the project URL

Confirm the home page loads from the URL shown in the result panel.
2

Connect the admin wallet

Sign in with the wallet from Step 1 and confirm the admin dashboard is available.
3

Complete the operator setup

Configure General settings, Integrations, and your Custom Domain before sending traffic to the site.