All features
Game ecosystem

Real games. Open catalog. Your brand on top.

The challenge layer is a small game the visitor plays for a few seconds. Browse the catalog, write your own against a tiny SDK, and skin the whole thing so it looks like part of your site, not part of ours.

Marketplace
Every plan

An open catalog of games.

Browse what's there, add your own. Any public repository with a manifest can publish to the catalog.

Official games
Browse the catalog
First-party games published by Caputchin. The full marketplace adds games the community publishes from any public repository.
Game SDK
Every plan

Write your own. It's a few lines.

The SDK is one helper and a small contract. You render whatever you want into the container, push the result when the visitor passes. Anything you can build with HTML and JavaScript can be a challenge.

my-game.js
@caputchin/game-sdk
import { register } from '@caputchin/game-sdk';

register((container, bridge) => {
  // render whatever you want into the container
  container.append(/* your game ui */);

  // when the visitor wins, push the result
  bridge.pass({ score: 847, durationMs: 4200 });
});
Custom game skins
Alpha tier

Looks like your brand, not like ours.

Customize colors, fonts, and assets per site key. White-label the widget entirely on Apex when even our mark would clash.

Booting the leaf game...

DefaultThe skin the game ships with.

Booting the leaf game...

PersimmonA warm brand palette, passed inline.

Booting the leaf game...

MidnightA dark brand palette, passed inline.

Three live leaf-memory games running game-only in your browser, no account, no tracking. Two carry a custom skin passed inline, the same way a site key drives skins in production.

Build and distribute

Author games against a stable SDK, distribute them three ways, publish to a catalog open to anyone with a public repo.

Every plan

Game SDK

One register() call. Render whatever you want into the container, push pass() when the visitor succeeds. The package is tiny, the contract is versioned, and first-party games use the same public API you do.

Where it fits

Build a game once, ship it forever. The SDK contract is stable; we don't break authors.

Every plan

Three distribution paths

Install your game from our marketplace via a CDN, self-host the bundle on your own infrastructure, or bundle it directly into your app. Same SDK, three deployment shapes.

Where it fits

Pick whichever fits your stack and your trust model. Marketplace for speed, self-host for control, bundled for offline.

Every plan

Marketplace

Community-published games indexed from public repos. Browse by support tag, locale, mobile-readiness. Publishing is open to any public repository with a manifest.

Where it fits

Discover games other teams have built. Publish your own when you want to share it. The catalog grows because anyone can contribute.

Brand and customize

Tune game-specific runtime params on Solo, reach more visitors in their language, make the challenge look like your brand, white-label the widget entirely on Apex.

Every plan

Custom game configurations

Pass per-game runtime options (difficulty, asset slots, game-specific params) from your site key. The game reads them at boot and adapts without a fork.

Where it fits

Tune the same game differently on a public sign-up versus an internal admin form, all from one site key.

Alpha tier

Extended game locales

First-party games ship in a small core set on Solo. Alpha and above unlocks the full locale pack so visitors play in their native language, not just yours.

Where it fits

Sign-up forms or contact flows where a non-English visitor would otherwise bounce at a CAPTCHA they can't read.

Alpha tier

Custom game skins

Override colors, fonts, and asset slots per site key. The widget and the game canvas pick up your brand without needing to fork the game.

Where it fits

When the default challenge looks visually foreign on your site. Skin it once per site key; the games inherit.

Apex tier

White labeling

Remove every Caputchin mark from the widget. Apex customers ship the challenge as their own surface, with no third-party branding visible to visitors.

Where it fits

Brand-sensitive surfaces where any third-party logo dilutes the experience. The challenge becomes invisibly yours.

Common questions

Playing, building, and branding the challenge games.

What are the Caputchin challenge games?
Small games a visitor plays for a few seconds to prove they are human. You browse an open catalog, write your own against the SDK, and skin them so they match your site.
Can I build my own game?
Yes. The Game SDK is one register() call and a small versioned contract. Render whatever you want into the container and call pass() when the visitor succeeds. First-party games use the same public API you do.
How are games distributed?
Three ways: install from the marketplace over a CDN, self-host the bundle on your own infrastructure, or bundle it directly into your app. Same SDK, three deployment shapes.
Who can publish a game to the marketplace?
Any public repository with a manifest. The catalog is open, and games are indexed from public repos.
Can I make the game match my brand?
Yes. Override colors, fonts, and assets per site key. On the Apex plan you can white-label the widget entirely, so no Caputchin mark shows at all.

Ship the catalog. Or ship your own game.

Sign up, pick a game from the catalog, drop the widget on one form. Author your own game later when you want one that fits your brand exactly.

Start free