| ▲ | jayd16 18 hours ago | |
So wait are you saying you replaced an online tool with a local vibe coded app? Is it a web app with vibe ops? What's running all of the workflows now? Are you vibe provisioning new cloud instances? Or does everything run on local machines now? | ||
| ▲ | subscribed 18 hours ago | parent | next [-] | |
I used CF Wrkers because I wanted to try serverless(1) - I just needed a tiny https proxy for one of my personal scripts and.... It turned out to be super fun. And no surprise bills. (1) after my earlier experience with AWS lambda - almost no traffic (few requests per day), on free trier and YET I had to pay for the add-on they automatically added (and it took me almost 2 hours to find all the rhizomes that were proudly anticipating another few £ for pretty much zero traffic). | ||
| ▲ | singingtoday 18 hours ago | parent | prev | next [-] | |
We did at my work. We were paying too much for low code orchestration software. Replaced it with vibe coded workflows. Still have some infra costs but it's fantastic, cheaper, more velocity, and everybody is happy. | ||
| ▲ | hamandcheese 18 hours ago | parent | prev [-] | |
I highly recommend Workers for Platforms for anyone wanting to deploy vibecoded apps: https://developers.cloudflare.com/cloudflare-for-platforms/w... | ||