Fingerprint — Rules Engine (no-code protection)

Maps to the dashboard "Build your first rule" Get Started step. The Rules Engine lets you block or allow requests based on Smart Signals in the dashboard, without writing the decision logic yourself. It's the fastest way to get automatic protection live, and it complements (doesn't replace) server-side verification for your most sensitive actions.

When to use this vs. coding the checks yourself

• Rules Engine — broad, policy-level protection you can change without a deploy (e.g. "block bad bots and IP-blocklisted requests on this key"). Good default for most traffic.
• Server-side checks (fingerprint-smart-signals) — fine-grained, per-action logic tied to your business state (e.g. step-up auth only for first-time-device logins). Keep these for high-risk flows.
• Most teams use both: a ruleset for the baseline, code for the nuanced cases.

Rules Engine is in beta and requires Server API v4. Docs: https://docs.fingerprint.com/docs/rules-engine.