Fly.io Blog

https://fly.io and https://vultr.com I used Fly as a modern successor to Heroku (I know Heroku is still around). Features are good, scaling to 0 is great, their networking stuff is solid, and pricing is fair. I generally use it to host application backends. Vultr for when I want a long lived server or build my own infrastructure platforms. I use it as just a VPS provider for larger machines at reasonable costs. Caveat being I’m managing my own infrastructure with all the trade-offs that come with it.

Some options: - https://fly.io/ - https://render.com/ Your best bet is probably to containerize your application instead of looking for services that natively support ASGI.

Since we're all sharing our favorite simplest solutions, I guess I'll throw https://fly.io out there. The DX is far from perfect right now so this answer is _ever-so-slightly theoretical_ but, if you know how to use Docker, `fly launch` is extremely hard to beat.

A couple other similar options are Vercel (https://vercel.com) and Fly (https://fly.io), but there are several of these. Vercel might be the best choice if you're building with Next, though.

It's not exactly what you're asking for, but <https://fly.io> is pretty neat. It's easy to get going and will deploy any docker images you want with a bit of their config added. As for AWS ECS mentioned in the other reply -- it's great if you ever get it working, but it is a nightmare to learn and use.

Better yet, pick a few shades of grey ranging from white to black and a few shades of _one_ other colour. https://fly.io/ comes to mind. Also, here is a great video on choosing colour: https://www.youtube.com/watch?v=mq8LYj6kRyE

For deployment, I like Cloudflare Pages/Workers for small projects and https://fly.io for large projects. For frontend, I think you'll really enjoy Elm if you like R and Python. Personally, I use vanilla JS (no framework) for small projects and Elm for large projects. For backend, there are plenty of excellent REST API frameworks for Rust, Go, Deno, Elixir, etc. I can give specific language recommendations if you're interested. [1] https://elm-lang.org [2] http://vanilla-js.com

https://fly.io has been amazing for me. Dunno how their docs used to look but IMHO today it is very detailed they are especially forward-thinking regarding documenting some nice edge use-cases for the platform.

I was a long time Heroku user/lover (~10 years) for both personal and company projects. I've recently moved to Render[1], and so far it's been great. I haven't been using them long enough to put it through it's paces, but I'd certainly say it's worth a look. Other alternatives I've heard good things about are Fly.io[2] and Porter[3]. [1] - https://render.com/ [2] - https://fly.io/ [3] - https://porter.run/

Buyvm offers that for a VM: https://buyvm.net/anycast-vps/. And fly.io offers that but it's not a classic VM with SSH but a service similar to heroku: https://fly.io/ I'm affiliated with neither of these.

This is such a good feature. Go has been great for shipping single purpose binaries (like the CLI for https://fly.io), but I really enjoy writing TypeScript more than Go.

Hi there, after a “soft launch” some months ago using the tool internally. Today I released a new version of Plek adding support for https://fly.io/. Would love any kind of feedback!

This kind of problem is present in most of the currently available crop of coding agents. Some of them have default settings that would prevent it (though good luck figuring that out for each agent in turn - I find those security features are woefully under-documented). And even for the ones that ARE secure by default... anyone who uses these things on a regular basis has likely found out how much more productive they are when you relax those settings and let them be more autonomous (at an enormous increase in personal risk)! Since it's so easy to have credentials stolen, I think the best approach is to assume credentials can be stolen and design them accordingly: - Never let a coding agent loose on a machine with credentials that can affect production environments: development/staging credentials only. - Set budget limits on the credentials that you expose to the agents, that way if someone steals them they can't do more than $X worth of damage. As an example: I do a lot of work with https://fly.io/ and I sometimes want Claude Code to help me figure out how best to deploy things via the Fly API. So I created a dedicated Fly "organization", separate from my production environment, set a spending limit on that organization and created an API key that could only interact with that organization and not my others.

Hi HN! I’m Grant, creator of (https://cicada.build). Cicada lets you write CI/CD pipelines in TypeScript and test them locally. We built Cicada because of our own struggles building CI/CD pipelines. YAML is cumbersome, not type-safe, and does not scale well for large pipelines. Sharing logic across pipelines is hard and most providers don’t let you test your pipelines locally. Cicada lets you 1. write your pipelines in a real programming language. Using TypeScript gives you type-checking, syntax highlighting, and in-line documentation out of the box. It also lets you extend your pipelines by hooking into the entire TypeScript ecosystem of packages and modules. 2. test your pipelines locally. All jobs are run in containers. This means you can test them with Docker/Podman. It also means you get great caching. 3. run your pipelines on our cloud. Pipelines are checked into your repository and run when triggered by an event in your repository (like a commit/PR), when triggered manually, or at a defined schedule. We use Deno [0] to create pipeline definitions, Docker Buildkit [1] as our build engine, and Fly [2] for our cloud hosting. Our CLI is written in Rust for speed and stability. The hardest technical challenge we faced was writing BuildKit bindings for Rust [3]. Cicada’s client is fully MIT OSS (the CLI, BuildKit integration, and SDK) [4]. Our dashboard and cloud runners are closed source. The cloud runners have a generous free tier for individuals and are cheap…

As someone that was there at Heroku after the acquisition, I don't think you can state that since the acquisition it's been consistently downhill. There isn't much debate that things have stagnated in the last 5-7 years which is a longer story on why probably. Some examples of innovation that happened and were launched after the acquisition: buildpacks (at the time of acquisition Heroku was still Ruby only), Heroku Postgres launched forks/followers/dataclips all after the acquisition, review apps came several years after. Salesforce may have had an eventual hand in it, but there was still a lot of innovation happening due to the folks there in the near to mid-term after the acquisition for several years. All that said, very excited for the new crop of players in the space. There are a number of companies trying to be a cheaper or more stable Heroku. Personally I'm excited about the ones that are taking their own unique approach. https://www.fly.io and https://www.railway.app are two that to me seem to bring their own perspective vs. just trying to recreate Heroku as a carbon copy clone. There are a number more in the jamstack space that have become staples such as Netlify and Vercel which are also doing great things.

We're already there. We have huge companies using elixir and phoenix, with phoenix powering the web platform for the majority of them. Several great case studies exist on elixir-lang.org if you're interested, ie: Pepsi: https://elixir-lang.org/blog/2021/04/02/marketing-and-sales-intelligen… Heroku: https://elixir-lang.org/blog/2020/09/24/paas-with-elixir-at-Heroku/ Change.org https://elixir-lang.org/blog/2020/10/27/delivering-social-change-with-… And of course Bleacher Report, which has been on Phoenix since 2014, well before 1.0. On the sponsorship side, DockYard invested in my work for the last six years where I spent the majority of the year working on oss, and I've just joined https://fly.io where I'll spend 85% of my time working on Phoenix and related libraries. So we are well covered on the corporate sponsorship side. We also have Michael Crumm on the Phoenix team who works at Cargo Sense, where they support a portion of his time working on LiveView. Of course it would be great for other large companies leveraging value out of our work to give back, but we're well established on the sponsorship side :)

Would it be right to say this is sentry.io meets envoy, grpc, and konghq? Super interesting. Congratulations. How do I manage my API integrations, you ask? Global Accelerator (GLA) is a key infrastructure piece for a HA service I'm building but for the data-plane. It is such a hassle-free but slightly expensive way to vend anycast IPs (no need to purchase ASNs and/or announce routes from colos across the globe) and have the traffic load-balanced to 25+ AWS regions, that I recommend it instantly to anyone architecting HA services. https://fly.io and https://stackpath.com/edge-computing are viable alternatives. Cloudflare announced MagicTransit which isn't as smooth as AWS GLA in terms of developer experience, whilst Azure and Google offer global-load-balancers, too, and may be even before AWS announced it in 2018? So, really, I think utilizing GLA is something folks should do if they run global HA services. The only issue with using NLB behind AWS GLA is the client-IP is not preserved. In our case, we needed it, so we had to get creative with sticky routing and port assignment (listeners) to do load-balancing / traffic-shaping. Another HA trick I plan to employ is to use Cloudflare-Workers (200+ PoPs) to front https-traffic to our control-plane endpoints. It lacks observability, monitoring, and alerting unless you're on Cloudflare's enterprise plans. The rate-limiting option is expensive ($0.05 per 10k good requests). I'm sure there's no way to queue requests…

> although why would you use it for evil I couldn't help it! Ben Johnson recently wrote a Litestream post touching on this topic [1]: > multiple-writer distributed SQLite databases are the Lament Configuration and we are not explorers over great vistas of pain I offer my sincerest apologies if this database release may have inadvertently opened the gates of Hell. [1] https://fly.io/blog/litestream-writable-vfs/

do you remember writing this? https://fly.io/blog/carving-the-scheduler-out-of-our-orchestrator/ this was amazing post. i enjoyed reading it, it was relevant to some work stuff i was battling with. the linked articles at the end were amazing too. i had tonnes of respect for fly.io and yourself because of these posts. technically informative, clear, engaging. great stuff. the llm post? complete polar opposite. > I would like to take this moment to apologize to you, personally, for not giving a shit about "AGI". I wish I could tell you I've come to see the error of my ways, but I continue not to care about it. thanks for the snark, and kinda proving my previous point about the tone of the article that was supposed to be a personal blog post and then ended up on a company blog https://news.ycombinator.com/item?id=49052217

I like the Vanta people just fine and think it's a fine product, but I would not recommend it to startups looking to get SOC2. https://fly.io/blog/soc2-the-screenshots-will-continue-until-security-… Most startups should be doing way, way less than automation platforms like these tell them they need to do to get a SOC2 attestation.

You can if you script the request yourself, or you could have a front end that lets you cut out those paragraphs from the conversation. I only say that because yesterday I followed this guide: https://fly.io/blog/everyone-write-an-agent/ except I had to figure out how to do it with Gemini API instead. The context is always just (essentially) a list of strings (or "parts" anyway, doesn't have to be strings) that you pass back to the model so you can make the context whatever you like. It shouldn't be too hard to make a frontend that lets you edit the context, and fairly easy to mock up if you just put the request in a script that you add to.

That would be great, but > Fly.io supports Google and GitHub as Identity Providers[1] How about you just support SAML like a real enterprise vendor, so IdP-specific support isn't your problem anymore? I get it, SAML is hard, but it's really the One True Path when it comes to this stuff. [1] https://fly.io/docs/security/sso/

I like the concept. Many times I look for high quality articles to go deep on some topics. I recommend you the fly.io blog [1], it has really nice articles. [1] https://fly.io/blog/

> Great Slate fundraiser Thomas Ptacek Who is of course a frequent HN poster, one of the very top rated on the site. https://news.ycombinator.com/user?id=tptacek I remain strongly suspicious that this column of his is in fact a long and convoluted troll: https://fly.io/blog/youre-all-nuts/ That got about 2.5K upvotes here: https://news.ycombinator.com/item?id=44163063

how much faster does an engine on rocket fuel go, than one not on rocket fuel? The article in question[0] has the literal tag line: > My AI Skeptic Friends Are All Nuts how much saner is someone who isn't nuts to someone who is nuts? 10x saner? What do the specific numbers matter given you're not writing a paper? You're enjoying the click bait benefits of using strong language and then acting offended when someone calls you out on it. Yes, maybe you didn't literally say "10x" but you said or quoted things in exactly that same ballpark and its worthy of a counter point like the OP has provided. They're both interesting articles with strong opinions that make the world a more interesting place so idk why you're trying to disown the strength with which you wrote your article. [0] : https://fly.io/blog/youre-all-nuts/

> against the credulous lovers of "mediocrity" (cf. https://fly.io/blog/youre-all-nuts/) I read that article when it was posted on HN, and it's full of bad faith interpretations of the various objections to using LLM-assisted coding. Given that the article comes from a person whose expertise and viewpoints I respected, I had to run it through a friend; who suggested a more cynical interpretation that the article might have been written to serve his selfish interests. Given the number of bugs that LLMs often put in, it's not difficult to see why a skilled security researcher might be willing to encourage people to generate code in ways that lead to cognitive atrophy, and therefore increase his business through security audits.

The landing page shows all logos of small companies, including one that is migrating away from them (Turso) https://fly.io/

I just use Fly (http://fly.io) for toys... and it works pretty well. Have not tested at scale / reliability for a real thing.

For experiments and hobby projects the value proposition is amazing. Where else can you spin up an independent instance for $1.94 per month?* *Note this is for an instance with only 256MB RAM (https://fly.io/docs/about/pricing/), but it's definitely possible to run non-trivial projects on that. Rust-based web servers like Rocket require only about 10MB RAM. Basic PHP servers should also fit from what I can find.

Speaking of which, there's a great write-to about a related kind auth token, macaroons: https://fly.io/blog/macaroons-escalated-quickly/