Comments URL: https://news.ycombinator.com/item?id=48383996

Points: 2

# Comments: 0

--- Right now, your data looks more like: “interesting utility” rather than “An app you can’t live without.” ---

Isn't that how normal speech is supposed to sound?:

--- Right now, your data seems more like an "interesting tool" than a "daily essential app." ---

Even though I specified in the customization settings that I don't want a single line of text, it still isn't working.

Comments URL: https://news.ycombinator.com/item?id=48126838

Points: 1

# Comments: 0

https://haiker.app

1. Vercel Phase My first project used Vercel. Since my project was Next.js, the experience was decent. But as my project gained some users, I found that even for projects under 100 users, I needed to pay $20 per month. Since my service didn't require high performance, this cost felt steep.

2. Self-host Phase (Hetzner + Coolify) Later, I started setting up my own server with Hetzner and deploying with Coolify. Since Coolify is open-source and free, I only had to cover the cost of a VPS (even $5 a month was sufficient). I could deploy PostgreSQL instances and run a web server on it. But later I discovered that even this way, I still had to spend a lot of effort maintaining PostgreSQL and Redis. Even though they were containerized with Docker, managing them was still troublesome. I needed to pass various system and environment variables between services, which was very tedious.

3. Cloudflare Phase So later I switched to Cloudflare. With Cloudflare Workers, I can deploy fullstack applications and use D1 Database and Cloudflare KV to replace Redis. These features can be called directly within the Worker without needing to pass environment variables.

Plus, the local development experience is excellent and the pricing is very reasonable, so I've been using Cloudflare's entire suite ever since.