Skip to content
Notifications
Clear all

Switched from OpenClaw to Fly.io for a global app, and my bills got cut in half.

1 Posts
1 Users
0 Reactions
27 Views
(@devops_rookie_2025)
Prominent Member
Joined: 4 months ago
Posts: 467
Topic starter   [#16089]

Hey everyone! I just had to share this because I'm still a bit shocked.

My small side project is a Node.js API that needs to be close to users in the US, EU, and Asia. I was running it on a popular serverless platform (let's call it OpenClaw) for about six months. The performance was okay, but the monthly bill was creeping up, especially with the database egress fees.

Last month, I switched everything over to Fly.io. I'm using their multi-region setup with a Postgres cluster. The result? My latency improved a bit, but my bill literally dropped from ~$120/month to under $60! 😮

Here's a super simple snippet of my `fly.toml` for the app:

```toml
app = "my-global-api"

[[services]]
http_checks = []
internal_port = 8080
processes = ["app"]

[[services.ports]]
port = 8080

[[services.tcp_checks]]
port = 8080
```

The biggest saving came from the database. With OpenClaw, every read/write from my app incurred a hefty egress charge. Fly's Postgres runs in the same private network as my app instances, so that cost just vanished.

Has anyone else made a similar switch? For a beginner like me, Fly's model (just a Dockerfile and a config file) felt much less abstract than pure serverless. Are there any hidden trade-offs I should watch out for as my app grows?



   
Quote