Skip to content
orangecheck
Get started

Why orangecheck

A sign-in your users earn sats from.

The option beside Google, Apple and email, with one difference: every event your app pays for credits sats to the person who earned it, with a receipt anyone can check.

Start a projectQuickstart

Why bitcoin

Swap bitcoin for a keypair and the product stops existing.

Any key can be an identity. What carries the weight here is the payout and the bond beneath it. Replace bitcoin with an Ed25519 key and a card processor, and five things disappear.

  1. 01

    A bearer-asset payout

    The payout is bitcoin: something a person can hold outright, not a balance in an account they must pass KYC to open.
  2. 02

    Final settlement

    Lightning settlement can't be reversed. Card payments can be, for months.
  3. 03

    A real exit

    A Bitcoin address and BIP-322 let a person leave with their identity and signing key. orangecheck never sees key material. Moving accrued sats into those keys is the designed exit. It is not live yet.
  4. 04

    A bond time can't fake

    Resistance to fake accounts is priced on the value and age of unspent bitcoin. Capital can buy it but can't backdate it. A keypair is free to mint by the million.
  5. 05

    Receipts that outlive us

    Every event is anchored to a Bitcoin block, so it checks after orangecheck is gone. A bare signature proves who, not when, and needs our server alive.

Everything else, the button, the dashboard, the SDK, is convenience over that rail. The mechanics

For apps

Your sign-in provider doesn't pay your users. This one does.

Every other provider is paid by someone else: advertisers, license fees, token velocity. None passes the fee back to the person, and none checks offline if the provider goes dark.

  • Pays the user
    orangecheckYes, in bitcoin. Paid once the rail settles.
    Sign in with Google
    No
    Sign in with Apple
    No
    Auth0, Clerk, WorkOS
    No
    World ID
    A token grant, not sats
  • What you pay for
    orangecheckSessions and actions, never clicks
    Sign in with Google
    Page-view advertising
    Sign in with Apple
    An Apple developer account
    Auth0, Clerk, WorkOS
    Monthly active users
    World ID
    Verification and a token
  • Builds a graph of you across sites
    orangecheckNo. Sites check locally
    Sign in with Google
    Yes
    Sign in with Apple
    Partly
    Auth0, Clerk, WorkOS
    Yes, per tenant
    World ID
    No
  • Resists fake accounts
    orangecheckAn attest tier, bonded by bitcoin
    Sign in with Google
    No
    Sign in with Apple
    No
    Auth0, Clerk, WorkOS
    A paid add-on
    World ID
    Biometric
  • Works with the provider offline
    orangecheckYes. Receipts check offline
    Sign in with Google
    No
    Sign in with Apple
    No
    Auth0, Clerk, WorkOS
    No
    World ID
    No
  • A way out to self-custody
    orangecheckDesigned. It is not live yet: no federation is bound.
    Sign in with Google
    —
    Sign in with Apple
    —
    Auth0, Clerk, WorkOS
    —
    World ID
    —
  • An open spec your team can run
    orangecheckYes, in full
    Sign in with Google
    No
    Sign in with Apple
    No
    Auth0, Clerk, WorkOS
    No
    World ID
    Partly
  • What it costs to start
    orangecheckPay per event, no minimum
    Sign in with Google
    Free, with ad lock-in
    Sign in with Apple
    $99 a year
    Auth0, Clerk, WorkOS
    $240 a month, 7,000 MAU
    World ID
    Free, with token velocity

From cold to shipped

Five steps.

  1. 01

    Create your account

    Sign in with email or a Bitcoin wallet. It is also your developer account: there is no separate signup.
  2. 02

    Verify your domain

    A DNS TXT record or a meta tag. It gates live billing only.
  3. 03

    Drop in the code

    Each project gives you code for your stack: Next.js, React, Vue, Svelte, Express, Fastify, Hono or plain HTML.
  4. 04

    Smoke-test the loop

    Fire a real event from the console and watch it land within seconds. Test a webhook with one click.
  5. 05

    Go live

    Set your prices and your users' share. orangecheck keeps 20%. The rest is yours and your users'.

The lowest price is 1 sat, the smallest unit there is, not a spam control: your own floor is yours to set. orangecheck keeps 20% of what each event costs you, as ratified in the charter. The other 80% splits between your rebate and your users however you set it.

Start a projectQuickstartSandboxSee a demo app

What every app inherits

Same charter. Same chain. Same offline check.

What makes this safe to build on is something you can test on your own machines, not a promise.

No token, no lock-in, no fork

The charter binds every product: no token, no closed protocol, no lock-in. Custody is the clause that names its exception instead of promising it away. OrangeCheck holds the sats your users earn during bring-up, until federation custody and graduation to their own keys replace it.

The charter

Every event anchored to Bitcoin

Every receipt and every charter acceptance gets an OpenTimestamps proof in a Bitcoin block. If orangecheck disappeared tomorrow, every receipt ever issued would still check against the chain.

The mechanics

Checks without calling us

Sites check signed sessions locally against the published key. Activity attestations check in five steps. The checker runs in a browser, at the edge, or offline.

Check a receipt

Ship a sign-in your users earn from.

Five steps from sign-up to live billing. No env vars, no key ceremony.

Start a projectAsk us something