Bring your existing web or Unity game, or start something new. Add player sign-in, cloud saves, profiles, leaderboards, token access and controlled rewards without building every service yourself.
No invitation or existing API key required. One account; every game stays isolated.
blockmaker.polaris.city/…/ai-guide?gameId=your-game“Add player sign-in and a small cloud-save test.”
Made for the game you already have
Every feature uses the same game-specific setup. Choose one, test it end to end, then add more.
Let players use supported blockchain wallets—including EVM wallets—or optional email sign-in.
Save progress and settings inside your game’s separately scoped data space.
Add player profiles, scores and rankings without operating another backend.
Unlock levels, items or experiences using current on-chain ownership.
Give new players a clear Get ALGO guide for Pera or an existing exchange. Blockmaker shows their exact game wallet without handling card details.
Use a dedicated game wallet, explicit spending limits and guarded payouts when you are ready.
Each game gets a public integration guide with its supported SDKs, public setup details and security rules. Paste that URL into the coding agent that can edit your game.
Safe to paste: the public guide URL.
Never paste: a server key, wallet recovery phrase or .env file.
“Add Blockmaker player sign-in and a small cloud-save test to this web game. Read the public game guide first, and keep private credentials out of client code.”
Blockmaker handles the setup in four clear steps. Start small and keep control of the account and credentials.
See the guided setupBring an existing game or a new one. Blockmaker takes you straight to the guided first-game setup in the secure admin.
The wallet owns your reusable account. Add the game details and approve a zero-ALGO ownership proof that is not submitted to the blockchain.
It is shown once. Store it in a private backend or secret manager—never browser code, a Unity build or AI chat.
Give the safe-to-share URL to your coding agent, ask for one feature and test it before adding the next.
Blockmaker makes the public and private parts explicit so you—and your coding agent—know what belongs where.
One wallet owns the reusable Blockmaker account. That account can contain multiple games.
Configuration, credentials, allowed origins and player data are separately scoped for every game.
The game ID and AI guide can be shared. The server key belongs only in a trusted backend.
Rewards need a dedicated game wallet and deliberate limits before they are enabled.
Blockmaker uses logical game isolation within shared infrastructure; it does not claim that every game runs on separate physical hardware.
Player sign-in and one cloud save make a good first test. No invitation or existing API key required.