Product overview
ByteGuard Enterprise AI Security Gateway
The control plane, identity model, enforcement flow and deployment coverage in one deck.
Request a copyResources
Product material, documentation and answers to the questions security teams ask first.
Resource library
Product overview
The control plane, identity model, enforcement flow and deployment coverage in one deck.
Request a copyDatasheet
Supported surfaces, endpoint agents, browser extensions and integration points.
Request a copyDocumentation
Enrollment, policy and playbook design, agent health and reporting guides for customers.
Contact usFAQ
Need something more specific? Our team can walk you through it in a demo.
Request a DemoOn supported enforcement surfaces the decision is made before the prompt, file or tool call reaches the AI provider. ByteGuard holds the request, evaluates it against policy and then allows, blocks or quarantines it.
Unresolved files, such as password-protected or unknown formats, are handled fail-closed and blocked by default.
PDF, Office documents [DOCX, XLSX, PPTX], structured data [TXT, CSV, JSON] and images [PNG, JPG, TIFF] through OCR.
Endpoint agents run on Windows, macOS and Linux. Browser coverage uses enterprise force-install management for Chrome and Edge and a signed XPI for Firefox.
No. ByteGuard is a standalone AI security layer that works alongside DLP, EDR, identity, SIEM, SWG, DNS security and firewalls, and adds AI awareness to them.
A quarantined request is held pending approval instead of being sent to the provider, so sensitive cases receive a human decision.
Yes. The AI Identity Model combines endpoint, OS session, application, surface, provider account and department, so the same provider can fall under different policies.
Yes. ByteGuard provides inventory, usage visibility and policy for MCP servers, tools, skills and project workspace context.
Yes. ByteGuard reports AI usage by user, provider, account and department, and can apply quota-based policies such as allow or block when a limit is reached.
No. Coverage is capability-based. The surfaces we list are representative examples, not the full product scope.