Skip to main content
OpenSourceAlternatives

Cap

Open source · OSI-approvedStatus: unknownNew

Self-hosted CAPTCHA that verifies visitors without puzzles

Alternative to reCAPTCHA

Cap (Cap.js) is an open-source, self-hosted CAPTCHA designed to replace hosted challenges such as reCAPTCHA. Instead of asking visitors to click traffic lights, it verifies them invisibly with proof-of-work puzzles and server-side browser checks, and it keeps every byte of that process on infrastructure its operator controls. It serves teams that already run their own servers and want bot protection without feeding visitor data to a third-party tracker.[1][2]

Quick verdict

Cap suits small-to-mid product and engineering teams that self-host their stack and want to drop reCAPTCHA's tracking for a private, invisible check. Its strength is the combination of SHA-256 proof-of-work with server-side validation and instrumentation challenges, delivered through a roughly 20 kB cookie-free widget with a reCAPTCHA-compatible verify endpoint for migration. The material constraint is operational: there is no generally available hosted version, since Cap.js Cloud remains a waitlisted private beta, so somebody on the team must run the Docker or Node server. If the team can self-host, Cap is a strong privacy-first choice; if it needs zero-operations managed protection, it should use the CAPTCHA bundled with its auth or hosting platform instead.[1][2][3]

Key features

  • Invisible proof-of-work challenges Challenges solve silently in the browser using SHA-256 computation, so genuine visitors pass without clicking anything while bulk attackers pay compute for every attempt.[1][2]

  • Server-side validation and instrumentation checks Solutions are verified and the browser environment is probed on the operator's own server, adding a second layer behind the puzzle itself.[1][2]

  • Optional WASM time-lock puzzles Operators can trade a heavier client check (around 690 kB) for stronger resistance where abuse pressure justifies it.[1][2]

  • reCAPTCHA-compatible verify endpoint A siteverify-style endpoint makes migrating an existing reCAPTCHA integration a configuration change rather than a rewrite.[1]

  • Three deploy shapes Deploy as a standalone all-in-one Docker image, install the server package into an existing Node application, or join the waitlist for the managed Cap.js Cloud.[1][2]

  • Tiny default footprint The standard widget is near 20 kB with zero third-party requests, and the server ships as a 22 MB Docker image.[1][2]

  • Events, webhooks, and admin dashboard Verification activity is exposed through events and webhooks, with multiple site keys managed from a dashboard and custom branding for visible widget states.[1]

  • Privacy-first data posture No cookies and no tracking, verification stays inside the operator's infrastructure, and the project presents this as GDPR and CCPA compliant. Compliance wording is the project's presentation, not a legal determination.[1][2]

Who will love it

  • Privacy-regulated teams replacing reCAPTCHA get an Apache-2.0 codebase with no cookies, no cross-site profiling, and verification data that never leaves their own servers.[1][2]

  • Self-hosting shops already running Docker or Node can add the standalone image or the server package to existing infrastructure and manage keys from the included dashboard.[1][2]

  • Login and signup flows sensitive to friction benefit from a check most visitors never notice, replacing puzzle abandonment with a silent background computation.[1]

Who should avoid it

  • Teams with nobody to run a server should not adopt infrastructure they cannot operate; with Cap.js Cloud still in private beta, there is no managed fallback today.[1]

  • A managed WAF, native mobile SDKs, and a WordPress plugin are listed as coming soon, so high-abuse targets needing them today fit a mature hosted mitigation better.[1]

  • Performance-critical pages on weak devices should measure the heavier challenge modes first, since the strongest puzzles cost hundreds of kilobytes the default widget avoids.[1]

How people experience it

Indirect public reception sample only: repository stars and forks, AlternativeTo listing rank and likes, named production sponsors, and Logto v1.44.0 provider adoption. No original Reddit or G2 user reports were located within budget, so no verbatim testimonials are included.

2 cited community sources. Adoption proxies are not satisfaction scores. No independent measurements of bypass rates, solve latency, or accessibility outcomes were found. A further search beyond the research budget might locate user reports.

Public reception is indirect but strong: roughly 8,000 stars and 700-plus forks, a top-10 AlternativeTo reCAPTCHA-alternative ranking, named production sponsors, and first-class adoption in Logto v1.44.0. These are adoption proxies, not satisfaction scores.[1][2][3]

No original Reddit or G2 user reports were located within the research budget, so no verbatim testimonials are included and the effectiveness case rests on project reasoning plus adoption rather than third-party test results.[1]

Migration and platform fit

Migration from reCAPTCHA runs through the compatible siteverify endpoint, keeping existing server-side verification flows intact.[1]

Logto v1.44.0 ships Cap beside reCAPTCHA, Turnstile, and hCaptcha; Logto Cloud configures it in Console while open-source self-hosters run their own Cap instance.[1]

Questions worth asking

What is the best Cap alternative for non-technical users?

A managed CAPTCHA bundled with a platform the team already uses, such as the built-in providers (reCAPTCHA, Turnstile, hCaptcha, or Cap itself) in Logto Cloud, since these need configuration rather than a self-hosted server.[1][2]

Is Cap really no-code?

No. Embedding the widget, deploying the Docker image or Node server, and wiring server-side verification are developer tasks documented in the official quickstart.[1]

How much does Cap cost per month?

The license costs nothing: Cap is Apache-2.0 software with no published per-seat or usage price as checked in October 2026. The real cost is the operator's own server infrastructure, and managed Cap.js Cloud pricing is unpublished while it remains a waitlisted private beta.[1][2]

Can you self-host Cap?

Yes. Cap is entirely self-hostable through the standalone Docker image or the server package inside an existing Node application, with no third-party requests and verification data staying on the operator's infrastructure.[1][2]

Sources and editorial review

Source research. Reviewed on October 9, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.

We have not run or tested this product.

Indirect public reception sample only: repository stars and forks, AlternativeTo listing rank and likes, named production sponsors, and Logto v1.44.0 provider adoption. No original Reddit or G2 user reports were located within budget, so no verbatim testimonials are included. Adoption proxies are not satisfaction scores. No independent measurements of bypass rates, solve latency, or accessibility outcomes were found. A further search beyond the research budget might locate user reports.

  1. Cap homepage

    official · Observed October 9, 2026

    Official homepage: mechanism, privacy posture, footprint, deploy shapes, managed-cloud beta state, production sponsors, roadmap.

  2. Cap quickstart guide

    official · Observed October 9, 2026

    Official quickstart: npm packages, createServer config, Express middleware, standalone Docker image, challenge modes, token expiry.

  3. tiagozip/cap repository

    official · Observed October 9, 2026

    Repository README: stars and forks, Apache-2.0 license, invisible PoW plus WASM puzzles, widget and image sizes, sponsors.

  4. Cap effectiveness guide (fork mirror of official docs)

    community · Observed October 9, 2026

    Unofficial fork mirror of the official effectiveness guide; project-authored economic reasoning, not an independent measurement.

  5. AlternativeTo Cap page

    community · Observed October 9, 2026

    Third-party listing: free and open-source, top-10 reCAPTCHA alternative with 28 likes at observation; like count is a reception signal, not a satisfaction score.

  6. Logto v1.44.0 release notes

    official · Observed October 9, 2026

    Logto v1.44.0 release notes from early October 2026: Cap joins the supported CAPTCHA providers; OSS self-hosters run their own instance.

Compared with these products

Similar projects

Related projects with shared categories, technologies, or licensing.

Procaptcha

ProcaptchaOpen

Privacy-focused CAPTCHA that replaces reCAPTCHA and hCaptcha

Stars302
Commitjust now
LicenseApache-2.0

Procaptcha is a privacy-focused CAPTCHA that drops into any form as a reCAPTCHA or hCaptcha replacement, passing real humans invisibly and challenging suspected bots.

mCaptcha

mCaptchaOpen

Privacy-focused proof-of-work CAPTCHA with no tracking or puzzles

Stars2,492
Commit11mo ago
LicenseAGPL-3.0

mCaptcha is a free, self-hosted CAPTCHA that protects websites and forms with proof-of-work challenges instead of image puzzles or visitor tracking.

Private Captcha

Private Captcha

Privacy-first proof-of-work CAPTCHA with invisible checks

Stars197
Commitjust now
LicensePolyForm-Noncommercial-1.0.0

Private Captcha is a privacy-first proof-of-work CAPTCHA that blocks bots with invisible cryptographic checks instead of puzzles, tracking, or cookies.

RustDesk

RustDeskOpen

Remote desktop you can point at your own relay server

Stars122.3K
Commit11h ago
LicenseAGPL-3.0

RustDesk is remote desktop software where the relay server is a binary you can run yourself. That is the whole argument: the same convenience as the commercial tools, without your screen sessions transiting a vendor's infrastructure.

Shelve

ShelveOpen

Open-source secret and environment variable manager

Stars458
Commitjust now
LicenseApache-2.0

Shelve is an open-source secret and environment manager that stores variables per project and environment, with a CLI and GitHub sync for teams.

Infisical

InfisicalOpen

Secret management for applications and infrastructure

Stars21.8K
Commit8h ago
LicenseMIT

Infisical stores application secrets, syncs them into the platforms that need them, and rotates the ones that support rotation. Environments and folders keep development and production credentials properly separated.