Network Segregation and Threat Monitoring

The service uses managed cloud isolation, HTTPS-only traffic, restricted database access, and provider logs to reduce network exposure.

Status: Published

Last reviewed: June 21, 2026

Owner: Leo Infinity product owner

Text to paste

Answer: Yes

Yes. Leo Infinity runs production on managed cloud infrastructure with separated production environments, HTTPS-only traffic, no public database write access, protected service-role credentials, provider network isolation, and monitoring through Vercel/Supabase logs. Admin access is restricted by least privilege. Evidence: https://app.leo.com.vc/seguranca/network-segregation-monitoring

Policy controls

Production, local development, and third-party marketplace authorization flows are separated by environment variables and callback URLs.
The public application is served over HTTPS, and marketplace OAuth callbacks are handled through server-side routes.
Database service-role credentials are never exposed to browser clients and are stored as protected production environment variables.
Operational review includes failed authorization attempts, unexpected API errors, and provider alerts where available.

Evidence notes

Vercel hosts the application behind HTTPS and edge routing.
Supabase stores application data behind managed database access controls.
Server-side API routes enforce login before returning seller data.