Clear boundaries. Practical controls.
Security depends on the gateway, its deployment, and the upstream providers you choose. These are the controls implemented in the current product.
Separate credentials and access
Tenant API keys authorize proxy traffic. Operator credentials authorize management operations. Upstream provider credentials are managed by the gateway and are not distributed to tenant clients.
Tenant keys support scopes, optional expiry, and revocation. Authentication uses keyed hashes. Recoverable tenant keys and provider credentials are encrypted in PostgreSQL storage. Authorized operators can reveal recoverable tenant keys in the console.
HTTPS stays between client and target
HTTPS traffic uses a CONNECT tunnel. The gateway does not terminate the target TLS connection to inspect page content. Connection metadata, destination host, timing, transferred bytes, and transport outcomes can still be recorded.
Plain HTTP is forwarded without TLS content protection. Secure the client-to-proxy connection and administrative endpoints appropriately for your deployment, and assess the upstream provider's own policies.
Admission and shared capacity
The gateway checks identity, scope, quota, and route capacity before admitting traffic. Shared Redis coordinates rate and concurrency limits across replicas. Sticky requests preserve their route contract when a route is full.
Revocation is subject to each replica's authentication-cache lifetime. It does not forcibly close every already-authorized CONNECT tunnel. Operators should plan incident response around active connections as well as credential rotation.
Deployment responsibilities
Operators configure secrets, network exposure, TLS, data retention, backups, monitoring, and supported providers. PostgreSQL and Redis must be configured for the availability and workload requirements of the deployment.
Capacity and response times depend on target websites, provider behavior, network conditions, and resources. Agree on an evaluation workload before setting service objectives.
Report a security concern
Email ddc@vdtdata.com with the affected component, reproduction steps, and a redacted description of the impact. Do not include live API keys, passwords, or unrelated personal data. DDC will coordinate any additional information needed for investigation.