Domains & edge
Domains with HTTPS, guarded at the edge.
Coswarm’s own proxy routes every host to its service, gets certificates from Let’s Encrypt and filters traffic with Coraza and the OWASP Core Rule Set.
HTTPS without thinking about it
Certificates come from Let’s Encrypt by HTTP-01 or TLS-ALPN-01 and renew on their own. Upload your own instead when you have one; expiry dates are always in sight.
A firewall per domain
Coraza with the OWASP Core Rule Set. Choose from 14 rule groups per domain: SQL injection, XSS, remote code execution, scanners and more.
Decide who gets in
IP allowlists and blocklists, by address or CIDR, and basic auth. Requests from outside an allowlist are dropped without an answer.
gRPC, TLS upstreams, Cloudflare
Serve gRPC over h2c, talk HTTPS to the upstream, and read real client addresses when Cloudflare sits in front.
In detail
What you get
Traffic you can see
- Proxy logs you can search by host, address or path, filtered by status class.
- A 24-hour traffic chart on the dashboard, with each deploy marked where it happened.
- What the firewall dropped, counted.
Routing
- Each host goes to a service and its port; Swarm spreads requests over the replicas.
- Subdomains under your panel’s domain, an HTTPS redirect per domain.
- The proxy runs as its own service on ports 80 and 443.
With Cosmo
Cosmo can add, change and remove domains, summarise traffic for any window up to a week, and probe DNS, TCP or HTTP from inside an app’s container to find where a request stops.
How Cosmo works- “Why does api.acme.dev return 502?”
- “Put grafana behind an IP allowlist”
- “Which paths returned the most 5xx today?”
Your servers are waiting.
One command, a minute or so, and the panel is on your domain. Free, and yours to keep.
curl -fsSL https://coswarm.dev/install.sh | bash