API SECURITY / EARLY ACCESS · Every identity. Every route. A clear decision.
Tucana Shield
Explore the demo
◈ TUCANA SHIELD / API DEFENSE

API SECURITY / MISSION CONTROL

open-appsec
Inline request inspection.

The isolated NGINX lab verified basic-model prevention: SQL injection, cross-site scripting and shell-injection probes returned 403 before the origin. The nine-check lab was removed after testing. Customer production prevention is staged; authentication and object authorization remain application decisions.

API-FIRSTHUMAN AUTHORITYDEFINED BOUNDARIES
THE API MISSIONILLUSTRATIVE MISSION DISPLAY
TUCANA / CONTROL ROOM
CONTEXT → DECISION → EVIDENCE
Clear scope / visible evidenceOne connected view. A specific scope for every control.
MISSION CONSOLE / OVERVIEWExplore a sample ↗
LIVE CONNECTION STATUSREAL SERVICE CHECKS · NO CUSTOMER RECORDS
CONNECTING

Current service health

Loading the latest read-only checks…

Waiting for a timestamped observation
Customer workspace—Check duration unavailable
Pilot inquiry service—Check duration unavailable
Recent service checks
Only actual observations appear here.
Health checks describe these services. Customer API request and blocked-attack counters are not connected.Open Grafana ↗
CONTROL ROOM / API SECURITYSCOPED IDENTITYTRACEABLE DECISIONSKnow the evidence ↗
COMPONENT ROLELAB PREVENTION VERIFIED / PRODUCTION STAGED

DATA FLOW

NGINX attachment → contextual inspection → app authorization

Verify the attachment, basic model, policy and actual customer traffic path before rollout. The upstream default fails open on inspection failure; the isolated lab confirmed that behavior while application authorization remained independent. This is bounded lab evidence, not proof against all zero-day attacks or a deployed custom ML training pipeline. Premium schema enforcement and identity-based quota features are not included in the Community pilot. Advanced-model embedding rights require separate review.

Apache-2.0 engine/basic model; separate advanced-model terms

A component’s license, features and deployment terms must be checked for the exact version and commercial use. Named projects do not endorse Tucana Shield.

ARCHITECTURE / TWO ACCOUNTABLE PATHSREFERENCE VIEW · CONNECTION STATUS IS EXPLICIT
REQUEST PATH / SYNCHRONOUSA decision before an application effect
EVIDENCE PATH / ASYNCHRONOUSEvidence never grants permission
Compatible gateway + application controls + bounded evidence. Deployment is verified per environment.Component dossiers ↗
YOUR NEXT MOVESCOPE BEFORE ENFORCEMENT

START WITH ONE API

Make the boundary visible.
Then prove the control works.

Bring your gateway, an API contract and a test environment. Define the evidence, owners and response limits for a scoped pilot.

Scope an API pilotExplore the request lab