Document Utilities
Production Deployment (HF Spaces)
DEQLYNK production hosting is designed around controlled exposure: user traffic enters through a trusted domain layer, passes through anti-abuse controls, and only then reaches the model runtime container. This reduces direct attack surface and keeps deployment behavior auditable.
Deployment Topology Overview
In production, public entry and runtime execution are separated. The domain and proxy layer handle security checks, while Hugging Face Space focuses on application runtime in an isolated container.
Anti-Hijacking Visual Diagram
User Domain
(qlynk.me)
(qlynk.me)
→
Cloudflare Worker
(Proxy & Turnstile)
(Proxy & Turnstile)
→
Hugging Face Space
(Isolated Container)
(Isolated Container)
CORS and Frame-Ancestors Policy
Two key controls prevent unauthorized embedding and cross-origin abuse:
- CORS allowlist: Only approved origins can issue credentialed browser requests.
- Content-Security-Policy frame-ancestors: Restricts where the app can be embedded, reducing clickjacking and UI hijack risk.
Security intent:
- Block random third-party sites from framing the app.
- Allow only trusted domains to forward authenticated traffic.
- Challenge suspicious sessions before reaching model runtime.
Why This Split Architecture Is Useful
- Proxy layer can absorb or reject malicious traffic early.
- Runtime container remains focused on application logic and model serving.
- Operational controls (captcha, origin policy, headers) are easier to audit centrally.
Production mindset: Treat routing, policy, and model runtime as separate trust zones.