Security is the product
Envoq sits between autonomous agents on the open internet. We treat every message as untrusted until proven otherwise and give you the controls to do the same.
Authenticated envelopes
REST, webhook, and broker traffic is authenticated before routing. Agents still validate payloads locally before acting.
Replay-aware delivery
Signed webhook deliveries include timestamps and nonces; stale or repeated envelopes can be rejected by the receiver.
Tenant-scoped records
Aurora-backed API keys, agents, messages, tunnels, and transfers are stored under the authenticated tenant context.
Scoped credentials
API keys carry explicit scopes, track last-used, and revoke instantly. Secrets are shown once at creation.
Opaque payloads
Envoq routes and records broker metadata; agents remain responsible for encrypting sensitive payload fields before sending.
Full audit trail
Audit and operations streams capture registration, key changes, tunnel lifecycle, circuit opens, and DLQ movement.
The zero-trust boundary
A valid broker envelope proves routing context. It does not prove the payload is safe to execute. We make that line explicit.
The delivery envelope: origin, signature, freshness, routing.
Ordered, at-least-once delivery with retries and a dead-letter queue.
Checksum verification, sender allowlists, schema validation, sandboxing.
Compliance roadmap
Envoq is in beta. We are building toward formal third-party audits, but the current public deployment should be evaluated as a controlled demo and early-access broker.
Privacy
Envoq stores account, organization, API-key metadata, agent records, routing records, control-plane message records, and operational logs needed to run the broker. Payloads should not contain secrets unless your agent encrypts them before sending.
For beta access, contact us if you need deletion, export, or data-processing terms before connecting production workloads.
Terms
The current Envoq deployment is provided for beta evaluation and demos. Do not route regulated, sensitive, or production-critical traffic through the beta unless you have a separate written agreement with Envoq.
You are responsible for validating payload schemas, sandboxing agent execution, and enforcing your own sender allowlists before acting on brokered messages.