Developer documentation
Build on SecKav
SecKav protects your apps, APIs, and private resources from one platform — an India-first, DPDP-native security cloud. This is the developer's guide to the three products and how to wire them into your stack.
How SecKav connects to your stack
SecKav is a transparent reverse proxy: you point your domain's DNS at the SecKav edge, and every request flows through our security pipeline before reaching your origin. No SDK is required for WAF, bot, DDoS, or DLP — it works at the edge. The optional @seckav/sdk adds client-side consent, telemetry, and server-side object-ownership signals on top.
dns; Point your domain at the SecKav edge (example) app.acme.com. CNAME edge.seckav.tech.
Onboard in the dashboard under Coverage → Add domain. SecKav verifies the DNS/edge wiring and pins your origin automatically.
Authentication
Two key types. A publishable key (pk_live_…) is browser-safe and write-scoped — use it in the SDK. A secret key (sk_live_…) is server-only and full-scoped — never ship it to a browser.
httpAuthorization: Bearer sk_live_… # dashboard / server APIs x-api-key: pk_live_… # SDK (browser)
The three products
WAF & Edge Security →
WAF, Bot Management, L7 DDoS, and India DLP — configured from the dashboard, enforced at the edge. No code changes.
AI Security →
Protect AI agents and APIs: MCP firewall, AI-crawler control, prompt-injection and BOLA defenses, self-learning object authorization.
NEXUS Connect →
Zero-trust access to private resources: device posture, hybrid post-quantum handshake, least-privilege scoping, instant revocation, M2M.