Talk to us

Developer platform

By invitation

Third-party quests, with the security model of an app store

Verified companies build quests and HTML5 minigames with our SDK, and players open them inside the Seekprotocol app. Every build is signed, checked, reviewed and sandboxed before it reaches a single player.

Deployed on 7 November 2026 and switched off for the public. Every component is running, and only tester accounts can see maker content while the first companies are onboarded.

7
Edge workers, deployed by CI
1
Sandboxed host per game
2
Signatures on every build
30 s
To stop any quest, everywhere

Principles

Four principles

01

No maker code runs with value attached

A quest is data produced by our compiler and run by our own engine. Minigame code only runs in a sandbox, and its score counts only through a one-time ticket the server issued.

02

One place decides, the edge delivers

Progress, rewards, risk and payouts are decided in one database. The edge workers accept, test, store and serve builds. They can refuse things. They can never grant anything.

03

Signed, reviewed, then served

Every build is signed with the maker's own key, checked automatically, reviewed by a person where anything is new, and then signed by Seek. The app verifies that signature before it runs anything.

04

Dark until launch

Players are gated by a platform switch and a tester list. The console sits behind a second access layer with an allow list, on top of its own login and a second factor for staff.

Architecture

How it fits together

Makers and Seek staff work in Store Connect. The edge accepts, checks, stores, signs and serves builds. The core holds every decision and runs quests for players. Players reach maker content only through the app.

People

  • MakersVerified companies, SDK and CLI
  • Seek staffReviewers, second factor required
  • PlayersThe app, one locked WebView per game

Edge

  • Store ConnectConsole, simulator, API
  • Review workerAutomatic checks and moderation
  • Signer workerSole holder of Seek's signing key
  • Game hostsOne sandboxed host per game
  • Game proxyThe only endpoint a game may call

Core

  • Decisions databaseRow level security, no client access
  • Quest engineRuns every quest on the server
  • Transparency logAppend only hash chain
  • Kill switchesQuest, maker and global

On Solana

  • MembershipUSDC or SOL, verified on chain
  • Log anchorDaily. Built, not yet switched on
Simplified from the platform's architecture and security document, version 1.0 of 7 November 2026.

Release

From build to release

  1. Build and signThe maker's key never leaves their machine.
  2. QuarantineUploads are verified file by file and held unserved.
  3. Automatic checksBundle, capabilities, changes, texts, limits, game code, moderation.
  4. Human reviewA person plays anything new. Nobody reviews their own company.
  5. Seek signsOnly what the core reports approved, logged in the same transaction.
  6. Staged release1, 10, 50, then 100 percent, with an automatic pause.

At play time

What happens when a player opens a game

  1. The app asks the serverThe same door as our own quests: ban list, login, device attestation.
  2. A one-time ticketPlus a launch token that lives ten minutes and names one game and one run.
  3. Pinned to a hashThe game loads only the exact approved build.
  4. One way outThe game can call its own files and the proxy. Nothing else.
  5. The score counts onceAdvisory until the server accepts it against that ticket.

Isolation

Five layers around every game

We assume a minigame could be malicious. So five independent controls sit around it.

  1. 01

    Its own host

    A separate subdomain per game. Two makers never share a hostname or a player id.

  2. 02

    A sandbox with an opaque origin

    Scripts and nothing else: no cookies, no storage, no pop-ups, no navigation.

  3. 03

    Locked response headers

    Camera, microphone, location and payment are switched off.

  4. 04

    Only approved bytes

    Every file is pinned by hash. Anything else is a 404.

  5. 05

    Proxy rules

    A valid launch token is required. An origin alone is never trusted.

Privacy

What a game learns about a player

Shared with a game

  • A pseudonymous id, different for every game and not reversible
  • The player's language
  • A random seed for this run
  • Device class, OS and app version
  • Its own saved data for that player, up to 64 KB

Kept from a game

  • The account, name or e-mail
  • The player's position
  • Camera, microphone, files or contacts
  • Wallets, balances or session tokens
  • Anything belonging to another game

Statistics for makers are aggregated. Any group smaller than five players is shown as fewer than five.

Operations

Stepping in fast

30 seconds

Three kill switches

Staff can stop one quest, one maker or every maker quest. Caches expire within 30 seconds.

Every 10 minutes

A guard on every rollout

A job compares a new release with the one before, and pauses it if players are refused far more often.

Kept 30 days

Crash reports without personal data

Crashes and logs per game and version, scrubbed twice before they are stored.

Before it opens

What is left to do

01

Enrollment

In progress

Company enrollment modelled on an app store's developer program, with a second factor for every maker account.

02

Maker Agreement

Open

The agreement is a draft. The lawyer-reviewed version replaces it before makers are let in.

03

Log anchoring

Decision

The worker that writes the transparency log head to Solana is built. Switching it on is a decision still to be made.

04

Switching on

Two steps

First the platform, then rewards for maker quests, as two separate decisions.

Build with us

Bring your own quest to the network

We are onboarding the first companies by invitation. Tell us what you want to build.