FAQ

Frequently Asked Questions

Everything you need to know about Dejanu and Remote Browser Isolation.

SWG filters traffic but active web code still executes on endpoints. Dejanu runs the browser remotely—only pixels reach devices. Use both together for defense-in-depth.

VDI is powerful but expensive for browser-only access. Keep VDI for power users; move web-only users to Dejanu at 60% lower cost and 5× faster deployment.

Yes. Full feature parity in cloud, on-premises, or air-gapped deployments. Docker and Kubernetes supported.

Export session recordings, retention logs, and policy enforcement reports. Evidence, not explanations.

Dejanu uses WebRTC for sub-50ms media transport with TURN for difficult networks. RBI is deployed for risk-heavy workflows where security plus acceptable UX is the goal.

Policies are enforced in the runtime network path using proxy plus egress restrictions—not only UI restrictions. This reduces bypass routes.

For 100 users, 2 hours/day, 30-day retention: approximately 9 million rials/month total storage. Less than the cost of one audit finding.

MOAT locks the remote browser to a single web application. Users cannot open new tabs, type URLs, or navigate outside the designated app. Ideal for contractors, vendor portals, and BPO agents.

Defense-in-depth: CSRF protection, anti-replay HMAC signatures (timestamp + nonce), IP-bound JWTs with server-side blacklisting, distributed rate limiting, mTLS device binding, TOTP 2FA for admins, and strict CSP/HSTS headers.

It is optional and tenant-gated. It works from a screenshot of the current view—not your raw browsing history—is rate-limited per minute and per day, and provider keys are encrypted at rest. You choose the provider (OpenAI, Azure, Anthropic, Google, or a compatible endpoint).

Stop securing endpoints.
Start isolating browsers.

30-day free pilot · 25–50 users · Architecture review included · No credit card required

Start Free Pilot