Detect Unauthorized Access.
Before Damage Is Done.

A protected request is any API call that passes through Beezifi Security for inspection and policy enforcement. Each call to your /check endpoint consumes one request from your balance — whether it's blocked, allowed, or ghost-responded. This model is simple, predictable, and aligned with how you actually use the platform.

When Beezifi Security detects a request that matches a Ghost Response rule, instead of returning a standard block (which tells the attacker they've been caught), it serves whatever you've configured — a custom HTML page, a text response, or a redirect to any URL. Your integration returns that content to the client (with whatever status code you choose), and the request never reaches your real handler.

When your request balance reaches zero, the enforcement layer will block new requests until you top up. You can purchase additional request packages at any time from the Billing section of your dashboard. Your rules, API keys, and configuration are preserved — only enforcement is paused until balance is restored.

No. All accounts share one database, and every record carries its account ID. Every query is filtered by the account in your signed session — never by an ID sent from the browser — and objects such as rules, keys and firewall targets are looked up by both their own ID and your account ID. Tenant scoping applies on every plan.

Integration is a single HTTP call to our /api/v1/check endpoint from your API gateway or middleware. Send the request attributes (IP, country, API key, etc.), receive a decision (allow / block / ghost) and act accordingly. No SDK required — any language or framework that can make an HTTP POST can integrate in minutes.

Yes. Every pack — from 1 million to 100 million requests — includes the full platform: rule-based decisions, geofencing, IP restrictions, Ghost Response, threat analytics, API key management, firewall auto-blocking and dashboards. You're only paying for the volume of requests you protect. No feature gating, ever.

Every new account starts with 10,000 free protected requests — no credit card required. These are credited immediately on signup so you can explore the full platform and run real requests through the security layer before purchasing. We also issue promo codes periodically that can be redeemed from the Billing section of your dashboard for additional free requests.

No. Beezifi is a decision API, not a CDN or proxy — your traffic never flows through us, only the request attributes your backend sends. You pay per decision, not per byte.

When Beezifi Security issues a BLOCK decision for a real IP address, it simultaneously pushes a deny rule to every server you've linked to that API key, through a small agent installed on each server — UFW on Linux or Windows Defender Firewall on Windows. This happens automatically, in the background, without any action on your part. The result: a blocked IP is denied at the OS firewall layer too — not just at the application layer. You register each server on the Firewall page, which gives you a per-server agent secret and install command. The agent is deny-only by default: it can add and remove its own block rules but cannot open ports or change your existing rules. Downloads and step-by-step instructions are on the Firewall Agents page.

Yes. Each account can have up to 10 active API keys, each with its own rules and default policy; the number of rules is not limited. Build rule sets for geofencing, IP restrictions, and Ghost Response with fine-grained ordering and priority. Rules are evaluated in order — you have complete control over enforcement logic.