Cheeky jokes aside, you can definitely go down the hetzner/VPS route. Not everyone has the expertise or desire to spend time doing so, but if you do, then go for it I say. We have some nifty features that are non-trivial to recreate, but again, it depends on your needs.
Hey, we do want to add numbers back to that page. The issue was that the original numbers were inaccurate.
"The goal of this metric is to represent the health of a system. However, we found this binary “is there an incident or not” approach wasn’t accurate for describing our service. For example, in the past 30 days, 99.9% of projects hosted on Neon had an uptime better than 99.95%; however, the status page displayed 99.89% uptime."
How many times do you expect to slice it? "For 99% of days this year, 99% of our customers have experienced 99% reliability for 99% of their users, we're 99% sure"? (That's just the long way of saying 95%)
This is valid. However, many production databases won't scale to zero often. The serverless proposition is still valuable if you factor in the development, test, and staging environments scaling to zero plus our autoscaling that doesn't require downtime or dropped connections.
For guaranteed message delivery, you're probably best of using a messaging system designed with that in mind instead of listen/notify.
Hi, I work for Neon. Our product team would like to chat with customers to get their perspective on the changes. If you're an existing Pro Plan user, your email should have a link that you can use to arrange a chat with the team. Feel free to reach out via Twitter or Discord instead if you'd like.
Hey, I had a meeting with your sales dept in November and have been in talks around feature suggestions and requirements before and after that. I've replied to the email I got regarding my pro plan getting bumped to a scale plan (which in itself is reasonable, it's the pricing model itself i find questionable) and I'll consider scheduling a call via the link too.
I love what you guys are doing technically, I'm just a bit anxious about the path that this seems to take you away from the pay-for-what-you-use model.
My parents are still using my old 2012 MacBook Pro. Installing an SSD and 16GB of memory a few years ago revitalised it. The last time I used it when visiting them I could see no reason to retire it, but I assume it might lose out on security updates soon.
I have some services running on my home network (e.g Kubernetes and some stuff on a Raspberry Pi) that I'd like access when I'm away from home. Tailscale made that really easy. I just setup their client on the devices that need to communicate, and that's it. I can access those devices on my home network from my Macbook when I'm out and about. What's really neat is I can even set my Raspberry Pi as a DNS server for devices in my Tailscale mesh (using their DNS features) and use Pi-hole to setup custom DNS rules for those devices. Wrote a short piece about it here: https://evanshortiss.com/crc-tailscale
