Glossary

Fail-open

Fail-open is the rule that a signup goes through when the check that would refuse it is slow or down, so an outage on the checking side costs you no signups.

Also called allow on error.

An example

Your signup handler calls SignupBouncer with a 1.5-second limit. Say our server is unreachable for an afternoon. The call times out, your code treats the timeout as allow, and the person gets their account as if the check had never been there. The opposite, fail-closed, would refuse every signup until we're back.

Why it matters to an app with a free tier

Your signup form is where new customers arrive, so you have to decide what happens when the check on it fails. Fail-open means a few unchecked signups during an outage. Fail-closed means nobody can sign up to your app while our server is down.

What SignupBouncer does

Our docs' code and our hooks let the signup through when we're slow or down. With the REST API, you give the call a 1.5-second limit and let the signup through when it fails, as every code example in our docs does. With the Supabase and Ory hooks, a Cloudflare Worker sits in front of our server and answers allow when our server hits an error, is down or takes longer than 1.5 seconds. The Keycloak step lets signups through after 1.5 seconds too, and the Better Auth plugin does the same after 1.5 seconds by default (timeoutMs, up to 10 seconds).

With the hooks in enforce mode, a signup we answered too late shows in your Checks tab as "Let through, answer too late", and a signup during an outage shows nothing.

Read more

All terms in the glossary

Start on the Free plan

1 app and 1,000 checks a month, with no card.