←back to thread

Show HN: Novanode, Global load balancing with Caddy, no vendor lock-in

77 points martianE | 3 comments | 03 Apr 25 14:59 UTC | HN request time: 0.64s | source

I've been a long-time Cloudflare user, but sometimes I just want a global load balancer without the lock-in and with full configuration control (e.g., some Cloudflare rules require an enterprise plan).

I love Caddy for its easy configuration, and that's why I created Novnaode. It makes it easy to launch hosted Caddy instances (with Nginx coming soon) and puts you fully in control of how to manage the configurations.

No more being restricted by enterprise tiers or limited configuration options - just simple, powerful, and flexible global load balancing.

Check it out here: https://novanode.sh

1. codegeek ◴[03 Apr 25 16:03 UTC] No.43571685[source]▶
I love Caddy. Correct me if I am wrong but this looks like a hosted Caddy primarily for Load Balancing ? What about things like SSL termination or general reverse proxy capabilities ?

I would be interested in a hosted caddy cluster that lets me configure everything that Caddy provides without needing to fiddle with Caddyfiles or its API directly.

replies(1): >>43571870 #
2. martianE ◴[03 Apr 25 16:14 UTC] No.43571870[source]▶
Our goal is actually not to hide the configs behind a bunch of partial UI elements you get full control of your proxy. All your caddy configs should work out of the box. For SSL termination we use acme and you can use the dns method (let us know if you dns provider isn't in the plugins and we'll add it)

Pretty much the only thing we add is a storage layer for your certs so you avoid the acme rate limit for multi-region deployments

replies(1): >>43572543 #
3. SparkyMcUnicorn ◴[03 Apr 25 17:02 UTC] No.43572543[source]▶
This addresses questions I had about certificate generation across nodes/regions.

Slightly off topic, but something nice about Caddy is that it automatically falls back on ZeroSSL (if you have an email address defined) when you hit letsencrypt rate limits. I have a case where more certificates for a root domain are needed than LE is capable of providing, and this fallback solves for the rate limit problem seamlessly.