Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
101–110 of 149 posts
Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#102Isn't the entire point of vercel/netlify/cloudflare is that you *don't* have to self-host? The issue is the price of it, not the actual software. Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected. That 10k bill is roughly $50 dedi from hetzner, but the problem with that is that you need a distributed system, for that you need something more advanced that tau, let's say kubernetes…
There's also a third way, which we're trying to do at stacktape[1].
We've built a PaaS platform on top of AWS, running in your own account. So you get all of the stability, flexibility and reliability of AWS, yet the deployment process is easy as using something like Heroku.
Also, compared to Vercel, the pricing is just a % on top of AWS fees, and not a sudden $10k bill, or $550/TB Netflify egress costs.
Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#103Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#104Right now as I understand it, if you want to connect Vercel securely to a database with more than a password, you need to “contact sales” about “enterprise” (no self service option for demos and MVPs)
Might be a tech issue but imho needing to contact sales about enterprise level deals just for basic security stuff is not the best move since it forces people to expose their stuff or wait around and pay a bunch of money.
Dunno about you guys but I don’t ever click “contact sales” I just go to something else where my dev work isn’t gated by salespeople (even if it’s significantly more complicated) and I say this as a big proponent of Vercel, I wish I could use it more, but expecting users to wait around for sales to invoice them just to have a secure database connection is a dealbreaker for my use case regardless of my opinions or preferences of liking their stuff.
Sources
[1] https://github.com/orgs/vercel/discussions/42
Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#105Self-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…
Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#106Self-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…
"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.
Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#107Earlier quoted context omitted.
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…
I don’t know if the author intended to be “local first- adjacent” with this project, but I am seeing a lot of wasm-target projects lately, including replicated databases, and I wonder if this project isn’t a peek at what a truly distributed (browser-to-browser) workload might look like. This project persists the system config in GitHub, but if the components are wasm then there’s at a chance that they can use that pr…
There was a different, recent HN post about scoped propogators, which I find to have a lot of good potential for people to write and apply local customizations for their own apps.
I don’t know if those are the killer use case for this, but I think ideas along these lines takes it further out of alignment with incentives for business models.
Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#108Self-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…
Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#109What'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,…
Re: Tau: Open-source PaaS – A self-hosted Vercel / Netlify / Cloudflare alternative
#110Looks 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...