3 ms·
Pretty funny that I built an app in Brazil and then this happens right before it goes live. It would be nice to have stable pricing and not have a fear of diff
by zackify 2y ago
Pretty funny that I built an app in Brazil and then this happens right before it goes live.
It would be nice to have stable pricing and not have a fear of different features costing more out of the blue.
Other than this, fly has been a great service, I love the system, the CLI and litefs.
It scares me that internal bandwidth charges will start being added, the application I’m using has a lot of internal transfer which is currently free.
- davedx 2y agoThe nice thing about Fly is it’s very docker oriented, so depending on your app migrating it off may be fairly straightforward? My apps are all on Fly but in the regions without big hikes thankfully, so I’m sticking around for now, but it sucks some people are being hit by this…
- zackify 2y agoTechnically you are right. However my app is using litefs. In theory you could set this up on your own servers. Which is part of the reason I was so interested in it. However with fly it’s just one command to add a new region and my data is auto replicated there. That’s super nice compared to manually managing this. As long as bandwidth costs do not go up drastically I think it’ll be okay.
- estebarb 2y agoInternal bandwidth price is free? I decided to avoid Fly.io because the pricing page suggests it is not: "Any traffic exiting a Fly.io Machine is considered outbound data transfer, including: - traffic destined for the internet - traffic destined for other Machines or apps in your network"
- zackify 2y agoI have many edge nodes with data being synced to them internally with liteFS. This is free Edit: maybe you are right actually. I have to check on this closer. App is just about to launch so I hadn’t paid so much attention
- deleted 2y ago[deleted]