Sign-in domains
Overview
To guarantee secure authentication and license provisioning across corporate firewalls, network administrators should whitelist official Plannix identity and API hostnames.
Official domain allowlist
The following hosts are used by Plannix Studio, Plannix Build CLI, and web consoles:
| Domain | Protocol / Port | Purpose |
|---|---|---|
accounts.plannix.web.id | HTTPS (443) | Primary SSO sign-in portal and MFA challenge |
auth.plannix.web.id | HTTPS (443) | OAuth 2.0 token issuance and PKCE exchange |
api.plannix.web.id | HTTPS (443) / WSS | Model inference streaming and CLI communications |
cdn.plannix.web.id | HTTPS (443) | Application binaries, editor updates, and extensions |
Firewall and proxy configurations
When operating behind deep-packet inspection (DPI) proxies or Zscaler / Palo Alto firewalls:
- Enable outbound traffic to
*.plannix.web.idon port 443. - Ensure WebSocket upgrades (
Upgrade: websocketheader) are permitted for real-time model streaming. - Allow local loopback binding on range
127.0.0.1:4040-4045for CLI terminal OAuth responses.
IP addresses and egress routes
Because Plannix leverages global Anycast routing through Cloudflare and fast edge nodes, IP addresses may change dynamically for performance and DDoS mitigation. We strongly recommend configuring FQDN / domain-based allowlists rather than hardcoded CIDR blocks.
Security and phishing prevention
Security Reminder: Plannix representatives will never ask for your passwords, private keys, or 2FA codes. Always verify that your browser URL explicitly ends with
.plannix.web.id before entering credentials.