Live data from Hacker News

Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

github.com

41–50 of 149 posts

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#41

Looks compelling, but the docs are extremely vague and full of fluff. The "Why One Binary" is hilariously bad. Almost feels like content to impress managers/recruiters. https://tau.how/02-concepts/03-one-binary/#the-genesis-of-ta...

I thought you were probably exaggerating… you were not.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#42

Wouldn't using talos be better than having to run this on custom managed ubuntu servers?

Which Talos, can you send a link?

I assume https://www.talos.dev/

Basically a small OS that will prop itself up and allow you to create/adopt into a Kubernetes cluster. Seems to work well from my experience and pretty easy to get set up on.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#43
post #23

Self-hosted platform as a service?! Isn't the whole point of platforms as a service (from the customer perspective) that you don't need to do the hassle of self hosting. There are pros and cons to using an external service and to self hosting. And just throwing all these words at me together makes me feel like there isn't a coherent mental model of what this is trying to be, or if there is it isn't clearly communicat…

The point of platform isn't just that someone else hosts it. It's that it's a consistent target for your teams & different projects, with a well defined set of capabilities.

Having patterns to deploy & ship software, that also can bring up & manage other resources along the way (databases, load balancers, geo-reicatikn, etc etc).

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#44
post #8
post #3

First coolify[1] and now Tau. More competition the better for users. From the quick look it seems like coolify is more fully featured? [1]: https://coolify.io/

Before Coolify came CapRover and dokku. My toy server (64ram, ryzen 5600G 60tb HDD, 4tb NVMe) is currently running fedora/caprover, though I've been considering just putting truenas scale on it, as it added custom deployments as well...

Love Caprover. Using this on production to host many docker containers.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#45
post #36
post #23

Self-hosted platform as a service?! Isn't the whole point of platforms as a service (from the customer perspective) that you don't need to do the hassle of self hosting. There are pros and cons to using an external service and to self hosting. And just throwing all these words at me together makes me feel like there isn't a coherent mental model of what this is trying to be, or if there is it isn't clearly communicat…

Further down on the README, it explains how it uses libp2p for network autodiscovery, IPFS for distributed storage, and how it can distribute and share routes and assets and automating load-balancing. It is Webassembly-native, so you don't have to mess with compiling dependencies or execution environments. If it works as well as described, then the underlying technology (and the constraints they have) allows it to be…

Thanks for digging in.

Would be nice if READMEs opened up with what the thing was and maybe a one or two sentence problem and solution description.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#46

What's with the vilification of kubernetes? 99% of this document ( https://tau.how/99-Misc/kubernetes/01-k8s-cons/ ) boils down to "You have to understand what a pod, deployment, container, etc is" once you remove every line that discusses the cons of managing a cluster yourself, because nobody actually does that except extremely large orgs. All of these problems go away when you utilize a managed offering like DOKS,…

I like your take on this. I think K8s offers a _lot_ and it has a bad reputation because of its early days. Kubernetes has room to improve, like everything else, but the API now are becoming a lot easier to work with and the Custom Resources allows folks to extend Kubernetes.

I still think that projects like this one come from necessity. Folks want to have an alternative for vendor lock-in.

I'm building something like that too (https://github.com/pier-oliviert/sequencer) for Kubernetes, and it's also out of necessity.

Vercel, Heroku and others have a lot of helpful tools that are empower developers, and I think people want to have those without being locked-in.

It goes without saying that I'm totally bias :)

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#49

What's with the vilification of kubernetes? 99% of this document ( https://tau.how/99-Misc/kubernetes/01-k8s-cons/ ) boils down to "You have to understand what a pod, deployment, container, etc is" once you remove every line that discusses the cons of managing a cluster yourself, because nobody actually does that except extremely large orgs. All of these problems go away when you utilize a managed offering like DOKS,…

I disagree hard with this. I love kubernetes to bits, but managing complex networking issues, having proper security, or just simply rightsizing the nodes is definitely not going away with having a managed control plane.

Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative

#50
post #40
post #30

Earlier quoted context omitted.

"Self-hostable as a service" is a common pattern because it provides the benefits of as-a-service without the threat of vendor lock-in. Plus you can run the same software in temporary or test environments.

Where Vendor can also be an open source project. The cost of moving away from a project like Tau can be equally high as a closed source PaaS of course.

and if that cost of moving away is high enough, a team or org "locked in" to a FOSS solution can continue to pay humans to support it internally while evaluating off-ramps instead of being told they need to re-arch their cloud stack in three months' time.
Post reply on HN