Serverless DTLS
mlhpdx
12 points
11 comments
September 10, 2026
Related Discussions
Found 5 related stories in 120.3ms across 10,559 title embeddings via pgvector HNSW
- Telegram Serverless soheilpro · 186 pts · July 15, 2026 · 52% similar
- Cloudflare K2: serverless event streams elffjs · 221 pts · October 01, 2026 · 50% similar
- Open WireGuard Endpoints mlhpdx · 33 pts · August 14, 2026 · 49% similar
- TLS certificates for internal services done right mrl5 · 143 pts · July 09, 2026 · 47% similar
- Show HN: OneDeploy – Managed open-source apps with nightly backups and TLS relatedcode · 26 pts · October 16, 2026 · 45% similar
Discussion Highlights (3 comments)
mlhpdx
Founder of Proxylity here. I'm happy to answer questions about how this works, why we built it, and where it is (and isn't) a good fit.
Fischgericht
"Clients establish a DTLS 1.2 or DTLS 1.3 session with the Listener's assigned domain and port." "Every DTLS Listener receives a server certificate and private key managed by Proxylity." I don't get it. Why would anyone want to send all their private information unencrypted to your serverless server? "Get fired from your Organization for sending company or private data unencrypted to some random guys on the Internet" as a Service? Based on lossy UDP? ...What? Why would anyone do that? I don't get it.
freeone3000
Like. It’s already over the internet. If I have to send it unencrypted to you, why not just send it unencrypted to the destination? The cat’s already out of the bagel, so to speak.