Networking
Who can reach a service, what a service can reach, and the per-project firewall.
Default deny
Every workspace runs in its own network, closed by default:
- In: the internet reaches a web service only through BWEZE's edge, over
HTTPS on its
bweze.appURL or your domains. Nothing else gets in. - Between services: your workspace's services reach each other directly;
a private service answers at
http://app-<name>-<id>. Other workspaces cannot reach them. - Out: services can call anything on the public internet, but never private, carrier-grade NAT, link-local or loopback addresses.
- Backends: apps reach a backend through its public URL, like any other client.
BWEZE runs in one data center.
Firewall
Each project has an ordered list of rules that allow or block an IP address or range (CIDR), applied at the edge before a request reaches your service.
bweze projects firewall add <projectId> -a block -c 203.0.113.0/24 --note "scraper"
bweze projects firewall add <projectId> -a allow -c 198.51.100.7/32 --note "office"
bweze projects firewall list <projectId>
bweze projects firewall delete <ruleId>curl -X POST https://api.bweze.com/v1/projects/PROJECT_ID/firewall \
-H "authorization: Bearer bw_sk_..." -H "content-type: application/json" \
-d '{ "action": "block", "cidr": "203.0.113.0/24", "note": "scraper" }'How rules apply:
- Rules are checked in order, and the first one that matches wins.
- A blocked request gets
403. - With no matching rule, the request is let through, unless the list has
any
allowrule: then it works as an allowlist, and everything not allowed is blocked.
A project has at most 100 rules. The client address is the one Cloudflare's
edge saw (CF-Connecting-IP), which a client cannot forge.
Custom domains and SSL
Every hostname gets a certificate automatically. See Domains to connect one you own or buy one.