Documentation
Gate AI behaviour on real Snapdragon and Jetson hardware — or behind an HTTP endpoint — wire it into CI, and keep signed evidence of every run.
Getting started
CI/CD Integration
Wire EdgeGate into GitHub Actions so a model, runtime, or firmware change is gated on real hardware before it merges.
Read →SetupConnect a Device
Register your own Snapdragon or Jetson hardware as a self-hosted runner, alongside the EdgeGate-provided fleet.
Read →QuickstartGating an API-Backed Workflow
Regression-gate an n8n, Zapier, Make, or custom HTTP workflow. Same eval set and signed evidence, pointed at a URL instead of a device.
Read →Reference
MCP Server
Drive EdgeGate from an agent. Tool surface, auth, and the workflows the MCP server exposes.
Read →ReferenceField Recorder
A black box for deployed edge AI — a tamper-evident, signed log of on-device decisions, with replay.
Read →ProtocolField Recorder Protocol
Wire format, signing scheme, and ingest contract for Field Recorder events.
Read →EnterpriseBring Your Own Storage
Keep artifacts and evidence bundles in your own S3-compatible bucket instead of EdgeGate's.
Read →Not sure where to start?
Run the free NPU check to see how your model places on real silicon — no account required.
Run the free NPU check →© 2026 EdgeGate. Powered by Qualcomm AI Hub.