Network access requirements
Zingle connects to a small, well-defined set of systems. This page lists the outbound connections the platform makes so you can configure network access and egress rules.
Outbound connections
| Destination | Purpose | Required |
|---|---|---|
| Your data warehouse | Run SQL, introspect schemas, validate models | Yes |
| Your Git provider | Read repositories, push branches, open pull requests | Yes |
| LLM endpoint (AWS Bedrock or model-provider API) | Agent inference | Yes |
| Email provider | Send login (one-time code) emails | Yes (for email sign-in) |
| Metadata store | The platform's own database | Yes (internal) |
| Metadata/lineage source (e.g. DataHub) | Optional usage/lineage signals | Only if configured |
| Package registries | Install dbt and dependencies during build/sync | Build/sync time |
Customer VPC egress
In a Customer VPC deployment, the services run inside your network. The connections that leave your VPC are:
- The LLM endpoint (unless you configure an in-region/in-account option such as AWS Bedrock in your own account).
- The email provider for sign-in emails.
- Package registries at build/sync time.
Warehouse and Git traffic stays within your network when those systems are also inside your environment.
Inbound
Users reach the web app over HTTPS.