# fly.io

Fly.io is a company offering hardware-isolated virtual machines that boot quickly, run near users, and scale to large workloads.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Well, That Wasn't Fun: October 16 '26

DevFeed: [Well, That Wasn't Fun: October 16 '26](<https://devfeed.tech/articles/well-that-wasn-t-fun-october-16-26-121085.md>)

Original publisher: [Read original article](<https://fly.io/blog/well-that-wasnt-fun/>)

Author: Daniel Botha

Published: 2026-11-06T00:00:00Z

Content type: news

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [TCP/IP](<https://devfeed.tech/topics/tcp-ip.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [payload](<https://devfeed.tech/topics/payload.md>), [network-intelligence](<https://devfeed.tech/topics/network-intelligence.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [based](<https://devfeed.tech/tags/based.md>), [bug](<https://devfeed.tech/tags/bug.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [card](<https://devfeed.tech/tags/card.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [checksums](<https://devfeed.tech/tags/checksums.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [code](<https://devfeed.tech/tags/code.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [customer](<https://devfeed.tech/tags/customer.md>), [cve](<https://devfeed.tech/tags/cve.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [example](<https://devfeed.tech/tags/example.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [field](<https://devfeed.tech/tags/field.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [fun](<https://devfeed.tech/tags/fun.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [networking](<https://devfeed.tech/tags/networking.md>), [october](<https://devfeed.tech/tags/october.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [servers](<https://devfeed.tech/tags/servers.md>), [the-fly-blog](<https://devfeed.tech/tags/the-fly-blog.md>)

### AI overview

Fly.io patched and rebooted its fleet after CVE-2026-99999 exposed a flaw in Linux IPv4 checksum-offload validation for virtual machine traffic. By redirecting checksum writes, an attacker could alter two trusted IPv4 header bytes after routing and firewall checks, enabling a firewall bypass or a 32-byte out-of-bounds read that might expose host or neighboring VM data. Fly.io says it has no evidence customer data was exposed, but advises customers who ran there October 15-17 to rotate credentials sent over unencrypted protocols, including plaintext traffic over 6PN. The 10-hour rollout required staggered host reboots to limit disruption to Managed Postgres clusters; some machines remained down after hardware and reinstall problems, with no machines or customer data lost. Fly.io also revised incident communications so executives own the communication plan. Its practical security guidance includes encrypting internal traffic, using scoped and expiring agent credentials, limiting shared exposure across trust boundaries, treating agent inputs as hostile, and rehearsing credential rotation.

### Source excerpt

October 16, 2026 began like any other day at Fly.io (meaning, we were anticipating only a medium amount of chaos). By that evening, we had patched and rebooted our entire fleet in response to a Linux kernel bug. The full rollout took 10 hours, but the emotional damage persists. CVE-2026-99999 The rest of this won't make much sense without a clear read on the bug itself, so: the Linux kernel CVE team and pwn.ai announced CVE-2026-99999 on the morning of the 15th. We heard about it that night, and started working on mitigations. IP sleight of hand Protocols like TCP and UDP include checksums to detect corruption on the way across the internet. Calculating one means reading the whole message, which adds up at high speeds. Linux avoids that with checksum offload: instead of calculating the checksum immediately, the kernel stores metadata saying where the checksum should read from and write to. If the checksum turns out not to be needed, the kernel never spends the CPU on it. Not needed, for example, when sending to localhost, or when the network card can add its own checksums. Checksum offload works the same way for virtual machines. The virtual network card accepts checksum metadata and passes it to the host. On the host side, the packet is treated like any other offloaded packet, using the metadata the guest provided. The offload code has checks meant to reject bad metadata. For IPv4, they were wrong. To exploit that, an attacker needs to do three things: point the checksum at a different header field, pick a message that produces the checksum they want, and force the host to calculate the checksum in software. The pwn.ai post goes into detail on pulling that off. The end result: the host receives the packet, parses it, decides where to send it, then applies the checksum, in the wrong place. The attacker now controls two bytes of an IPv4 header the host has already trusted. Based on network activity during the rollout, we believe it's unlikely that any of our customer

## Feng Shui for Robots: The Fly MCP Server

DevFeed: [Feng Shui for Robots: The Fly MCP Server](<https://devfeed.tech/articles/feng-shui-for-robots-the-fly-mcp-server-97514.md>)

Original publisher: [Read original article](<https://fly.io/blog/feng-shui-for-robots/>)

Author: Daniel Botha

Published: 2026-10-23T00:00:00Z

Content type: article

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>)

Tags: [2023](<https://devfeed.tech/tags/2023.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apps](<https://devfeed.tech/tags/apps.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [computers](<https://devfeed.tech/tags/computers.md>), [databases](<https://devfeed.tech/tags/databases.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [environment](<https://devfeed.tech/tags/environment.md>), [files](<https://devfeed.tech/tags/files.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [server](<https://devfeed.tech/tags/server.md>), [servers](<https://devfeed.tech/tags/servers.md>), [the-fly-blog](<https://devfeed.tech/tags/the-fly-blog.md>)

### AI overview

Fly.io's `mcp.fly.io` connects agents to Sprites for development and Fly.io apps for production. Sprites provide Linux environments where agents can install packages, persist files across restarts, run services, expose HTTPS endpoints and checkpoint or roll back the filesystem. When an app needs to stay available, the agent can use the same MCP server to create a Fly Machine, volume and secrets, moving a Linux service between Linux machines. Setup uses browser authorization to select organizations, apps and Sprite permissions; access is limited to approved apps, and IP addresses and certificates are readable but not writable. Scheduled Sprite jobs are described as forthcoming, and adding MPG skills for managed Postgres is under investigation. This overview reflects the supplied excerpt.

### Source excerpt

In Databricks' State of AI Agents 2026 report, there's a chart from Neon's telemetry that's somehow both mind-blowing and unsurprising. In October 2023, AI agents created 0.1% of the databases on Neon. By October 2025 they created 80% of them. We're seeing this play out all across the infra landscape, including here at Fly.io, where agents have overtaken humans as our most common customer species. Thing is, we think it's important to remember that there's a human with aspirations behind those agents. Often one trying to build something that actually makes it to prod. If we want to make that easy, "computers for agents" can't just be a sandbox where an agent can vibe. Agents need a whole cloud now. Somewhere safe to try dumb stuff, sure, but also a dead simple migration path to, and all the requisite parts of, a scalable production environment. This is kinda our whole thing right now. So we built mcp.fly.io: one MCP server that connects your agent to Sprites and to your Fly.io apps. Start with a Sprite Building something real with an agent should start in a sandbox. The speed and scale at which you can test different approaches and solutions is easily one of the most significant benefits of building with agents. So you want them to be able to kick all the tires to find out which of them explode. This is why the sandbox you choose in this step is so important. There are plenty of places to safely execute agent code. But what you want is to actually install packages, write files, start a server on a port, hit the server, and see what restarting the server does in real life. This is how you get from vibes to a robust product. It's why you should tell your agent to build in a Sprite. Just Linux, all the way down When your agent builds something on a Sprite, it builds it the way it would on any Linux box. Packages go where packages go. Files sit on a disk that survives sleeps and restarts. The server runs as a service, a long-running process that survives the Sprite reboo

## Writing to AWS S3 from Fly.io (in Go)

DevFeed: [Writing to AWS S3 from Fly.io (in Go)](<https://devfeed.tech/articles/writing-to-aws-s3-from-fly-io-in-go-89758.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/18/fly-s3/>)

Author: Jamie Tanna

Published: 2026-10-18T16:46:39Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [IO](<https://devfeed.tech/topics/io.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [go](<https://devfeed.tech/tags/go.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [s3](<https://devfeed.tech/tags/s3.md>)

### AI overview

A Go tutorial shows how to obtain a short-lived OpenID Connect token from Fly.io, exchange it through AWS STS for temporary credentials, and use those credentials to write objects to S3. It also gives example IAM trust and bucket policies and notes that overly restrictive trust-policy conditions caused an access-denied error.

### Source excerpt

I'm currently in the process of moving my site's media (under media.jvt.me) from Netlify to AWS S3. The underlying infrastructure for my site that writes this media is hosted on Fly.io, so needs a way to write to S3. I really wanted to avoid long-lived AWS credentials, and fortunately Fly supports OpenID Connect which integrates with AWS' OpenID Connect Federation to allow you to use short-lived OpenID Connect tokens to authenticate as a given IAM role, and then perform any necessary AWS actions. Although Fly has an example with curl, I wanted to blogument the "how to" with Go, as it wasn't super straightforward to do so. I've written this up in a sample repo on GitLab.com. Go code The core pieces are: // via https://gist.github.com/teknoraver/5ffacb8757330715bcbcc90e6d46ac74 var unixClient = http.Client{ Transport: &http.Transport{ DialContext: func(_ context.Context, _, _ string) (net.Conn, error) { return net.Dial("unix", "/.fly/api") }, }, } func getOIDCToken(unixClient http.Client) (string, error) { s3Body := bytes.NewReader([]byte(`{"aud":"sts.amazonaws.com"}`)) // or could be `{"aud":"https://sts.amazonaws.com"}` as long as it matches your Trust Policy // get the OIDC token resp, err := unixClient.Post("http://localhost/v1/tokens/oidc", "application/json", s3Body) if err != nil { slog.Error("Failed to call Fly OIDC tokens endpoint", "err", err) return "", err } defer resp.Body.Close() body, err := io.ReadAll(resp.Body) if err != nil { slog.Error("Failed to read body", "err", err) return "", err } return string(body), nil } func newAWSClient(oidcToken string) (*s3.Client, error) { cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithRegion("eu-west-1")) if err != nil { return nil, err } stsClient := sts.NewFromConfig(cfg) assumedRoleInput := &sts.AssumeRoleWithWebIdentityInput{ RoleArn: aws.String(os.Getenv("AWS_ASSUME_ROLE_ARN")), RoleSessionName: aws.String("..."), WebIdentityToken: aws.String(oidcToken), } resp, err := stsClient.AssumeRoleWithWeb

## Run AI agents safely with Ollama and Fly.io

DevFeed: [Run AI agents safely with Ollama and Fly.io](<https://devfeed.tech/articles/run-ai-agents-safely-with-ollama-and-fly-io-86260.md>)

Original publisher: [Read original article](<https://ollama.com/blog/fly-io-sprites>)

Published: 2026-10-13T00:00:00Z

Content type: release

Language: en

Sources: [Ollama](<https://devfeed.tech/sources/ollama.md>)

Topics: [Ollama](<https://devfeed.tech/topics/ollama.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [curl](<https://devfeed.tech/tags/curl.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [ollama](<https://devfeed.tech/tags/ollama.md>)

### AI overview

Ollama Cloud models can now be used from Fly.io Sprites, persistent Linux virtual machines designed for agents. A Fly.io gateway adds the Ollama API key to requests, keeping it out of the Sprite while access controls determine which Sprites can use the connector. The article also gives setup steps, API examples, and a fuzzing workflow using multiple models.

### Source excerpt

AI agents can now use Ollama's cloud models safely inside Fly.io's cloud computers.

## datasette-publish-fly 1.4

DevFeed: [datasette-publish-fly 1.4](<https://devfeed.tech/articles/datasette-publish-fly-1-4-31162.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Sep/11/datasette-publish-fly/>)

Author: Simon Willison

Published: 2026-09-11T02:58:52Z

Content type: release

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [App](<https://devfeed.tech/topics/app.md>), [bug](<https://devfeed.tech/topics/bug.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [datasette](<https://devfeed.tech/tags/datasette.md>), [datasette-1-542](<https://devfeed.tech/tags/datasette-1-542.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-40](<https://devfeed.tech/tags/fly-40.md>), [https](<https://devfeed.tech/tags/https.md>), [release](<https://devfeed.tech/tags/release.md>), [volume](<https://devfeed.tech/tags/volume.md>)

### AI overview

Release notes for datasette-publish-fly 1.4. The release sets force_https=true in fly.toml, fixes a volume lookup bug, and adds compatibility with app-scoped deploy tokens.

### Source excerpt

Release: datasette-publish-fly 1.4 Sets force_https=true in fly.toml. #31 Fix for Volume could not be found bug. #32 Compatible with app-scoped deploy tokens. #34 Tags: datasette, fly

## A comprehensive guide to Fly.io logging

DevFeed: [A comprehensive guide to Fly.io logging](<https://devfeed.tech/articles/a-comprehensive-guide-to-fly-io-logging-20051.md>)

Original publisher: [Read original article](<https://www.honeybadger.io/blog/fly-io-logging/>)

Author: Muhammed Ali

Published: 2026-08-13T07:00:00Z

Content type: tutorial

Language: en

Sources: [Honeybadger](<https://devfeed.tech/sources/honeybadger.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [log management](<https://devfeed.tech/topics/log-management.md>), [Cloud Logging](<https://devfeed.tech/topics/cloud-logging.md>), [error tracking](<https://devfeed.tech/topics/error-tracking.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [article](<https://devfeed.tech/tags/article.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [collect](<https://devfeed.tech/tags/collect.md>), [container](<https://devfeed.tech/tags/container.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops-articles](<https://devfeed.tech/tags/devops-articles.md>), [errors](<https://devfeed.tech/tags/errors.md>), [fastapi](<https://devfeed.tech/tags/fastapi.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [guide](<https://devfeed.tech/tags/guide.md>), [lightweight](<https://devfeed.tech/tags/lightweight.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [platform](<https://devfeed.tech/tags/platform.md>), [process](<https://devfeed.tech/tags/process.md>), [program](<https://devfeed.tech/tags/program.md>), [running](<https://devfeed.tech/tags/running.md>), [vector](<https://devfeed.tech/tags/vector.md>)

### AI overview

Fly.io automatically collects application output written to standard output and standard error and streams it for access. The excerpt describes logs being gathered in each app container, sent from the host through Vector into Fly.io's internal NATS cluster, then read by the log shipper and forwarded to a sink such as Honeybadger. It introduces a FastAPI example with endpoints intended to generate informational, warning, and error logs, but the excerpt ends before showing the commands or results. It does not establish how to configure Honeybadger.

### Source excerpt

Logging is an import part of debugging an app. Without a good method of catching errors or logs in general, you would end up with uncaught issues and could also lose valuable customers in the process. Read this article to learn how to effectively handle logs on Fly.io.

## Monitoring Your Django App Health on Fly.io

DevFeed: [Monitoring Your Django App Health on Fly.io](<https://devfeed.tech/articles/monitoring-your-django-app-health-on-fly-io-44049.md>)

Original publisher: [Read original article](<https://blog.appsignal.com/2026/07/22/monitoring-your-django-app-health-on-fly-io.html>)

Author: Dejan Lukić

Published: 2026-07-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [AppSignal](<https://devfeed.tech/sources/appsignal.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Django](<https://devfeed.tech/topics/django.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>), [Object-relational mapping](<https://devfeed.tech/topics/orm.md>), [SQL](<https://devfeed.tech/topics/sql.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [django](<https://devfeed.tech/tags/django.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

A step-by-step guide to instrumenting and configuring a Django application on Fly.io with AppSignal to monitor errors, performance, database queries, and host health from a dashboard.

### Source excerpt

A step-by-step guide to connecting AppSignal to your Django app on Fly.io so you can track errors, performance, and host health from a single dashboard.

## A comparison of startup latency for diverse workloads on Kubernetes and Daytona

DevFeed: [A comparison of startup latency for diverse workloads on Kubernetes and Daytona](<https://devfeed.tech/articles/kubernetes-is-the-wrong-primitive-for-diverse-workloads-81628.md>)

Original publisher: [Read original article](<https://www.daytona.io/dotfiles/kubernetes-is-the-wrong-primitive-for-diverse-workloads>)

Author: Daniel Thi Graviet ML Researcher

Published: 2026-07-13T00:00:00Z

Content type: comparison

Language: en

Sources: [Dotfiles Insider](<https://devfeed.tech/sources/dotfiles-insider.md>)

Topics: [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>)

Tags: [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [browser-based-ide](<https://devfeed.tech/tags/browser-based-ide.md>), [browser-ide](<https://devfeed.tech/tags/browser-ide.md>), [cloud-coding](<https://devfeed.tech/tags/cloud-coding.md>), [cloud-dev-environment](<https://devfeed.tech/tags/cloud-dev-environment.md>), [cloud-development-environment](<https://devfeed.tech/tags/cloud-development-environment.md>), [cloud-editor](<https://devfeed.tech/tags/cloud-editor.md>), [cloud-ide](<https://devfeed.tech/tags/cloud-ide.md>), [cloud-programming](<https://devfeed.tech/tags/cloud-programming.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [code-in-cloud](<https://devfeed.tech/tags/code-in-cloud.md>), [code-on-web](<https://devfeed.tech/tags/code-on-web.md>), [coding-environment](<https://devfeed.tech/tags/coding-environment.md>), [container](<https://devfeed.tech/tags/container.md>), [daytona](<https://devfeed.tech/tags/daytona.md>), [ide-editor-online](<https://devfeed.tech/tags/ide-editor-online.md>), [ide-in-browser](<https://devfeed.tech/tags/ide-in-browser.md>), [ide-online](<https://devfeed.tech/tags/ide-online.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [latency](<https://devfeed.tech/tags/latency.md>), [online-code-editor](<https://devfeed.tech/tags/online-code-editor.md>), [online-ide](<https://devfeed.tech/tags/online-ide.md>), [online-programming](<https://devfeed.tech/tags/online-programming.md>), [online-web-dev-ide](<https://devfeed.tech/tags/online-web-dev-ide.md>), [online-web-development-ide](<https://devfeed.tech/tags/online-web-development-ide.md>), [sde](<https://devfeed.tech/tags/sde.md>), [standardised-development-environment](<https://devfeed.tech/tags/standardised-development-environment.md>), [stories-insights](<https://devfeed.tech/tags/stories-insights.md>), [web-based-coding](<https://devfeed.tech/tags/web-based-coding.md>), [web-ide](<https://devfeed.tech/tags/web-ide.md>)

### AI overview

An evaluation compares Kubernetes and Daytona on 500 sequential launches of prepared environments, varying the working set from 1 to 100 distinct environments. Daytona's median time to first command was about 1.1 seconds across those cases, compared with 4.2-4.4 seconds for Kubernetes, while Daytona had a heavier tail. The results apply to prepared, sequential launches and do not measure concurrent launches, autoscaling, model loading, or end-to-end latency.

### Source excerpt

We tested diverse workloads and found that Kubernetes startup latency rises sharply as each job brings a different environment.

## Run Paperclip AI on a Sprite

DevFeed: [Run Paperclip AI on a Sprite](<https://devfeed.tech/articles/run-paperclip-ai-on-a-sprite-122061.md>)

Original publisher: [Read original article](<https://fly.io/blog/paperclip-on-a-sprite/>)

Author: Daniel Botha

Published: 2026-04-01T00:00:00Z

Content type: tutorial

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [free software](<https://devfeed.tech/topics/free-software.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [computer](<https://devfeed.tech/tags/computer.md>), [config](<https://devfeed.tech/tags/config.md>), [database](<https://devfeed.tech/tags/database.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [execution](<https://devfeed.tech/tags/execution.md>), [file-storage](<https://devfeed.tech/tags/file-storage.md>), [node](<https://devfeed.tech/tags/node.md>), [npx](<https://devfeed.tech/tags/npx.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [paperclip](<https://devfeed.tech/tags/paperclip.md>), [paperclip-ai](<https://devfeed.tech/tags/paperclip-ai.md>), [paperclipai](<https://devfeed.tech/tags/paperclipai.md>), [port](<https://devfeed.tech/tags/port.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [resume](<https://devfeed.tech/tags/resume.md>), [robots](<https://devfeed.tech/tags/robots.md>), [self-host-paperclip](<https://devfeed.tech/tags/self-host-paperclip.md>), [sprites](<https://devfeed.tech/tags/sprites.md>), [the-fly-blog](<https://devfeed.tech/tags/the-fly-blog.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

The excerpt shows how to run Paperclip, an open-source platform for organizing AI agents, on a Sprite. Create a Sprite, install Paperclip with `npx paperclipai onboard -y` (which uses embedded PostgreSQL, local file storage, and port 3100 by default), then configure authenticated access, bind the server to `0.0.0.0`, allow the Sprite hostname, and register the app as a service. The article also describes checking the health endpoint, retrieving the dashboard URL, and creating an admin account. Sprites provide hardware isolation, checkpoints that can restore the environment and agent state, and automatic pause/resume to reduce idle costs. Their network policy can restrict which domains agents reach. The excerpt notes that making the Sprite URL public removes Fly.io authentication while Paperclip's own login remains in place.

### Source excerpt

Paperclip is extremely hot right now. I'm not going to explain what it is in any detail here because you have YouTube. But in short: it's an open-source orchestration platform that lets you set up teams of AI agents that operate like a company. Org charts, goals, budgets, autonomous execution. It's perfect for people who want a team of robots to do all the work that they issue from a dimly lit room in which they stroke a cat and sip from a crystal glass. It is genuinely cool and appears to have real utility. So it's a safe bet that Mac Minis are sold out in every store in your city again. Fortunately, Sprites people have already forgotten what it feels like to have something as trivial as hardware scarcity get in the way of building cool things. Let's get a Sprite to run our Paperclip on: Wrap text Copy to clipboard sprite create paperclip Now we have a hardware-isolated Linux computer with 100GB of storage, its own URL with TLS, and a pause/resume lifecycle that means you only pay for it when it's actually doing something. Setup Node 22 is already in your Sprite. So this is the whole install: Wrap text Copy to clipboard npx paperclipai onboard -y The -y flag accepts all defaults: embedded PostgreSQL, local file storage, port 3100. It creates your config, sets up the database, generates secrets. Done. Make It Reachable and Register the Service Paperclip's default config binds to 127.0.0.1 in local_trusted mode. You're not sitting at this machine, so it needs to bind to 0.0.0.0 in authenticated mode, get told about your Sprite's hostname, and be registered as a Sprite service. Tell Claude: In ~/.paperclip/instances/default/config.json, change server.deploymentMode to "authenticated" and server.host to "0.0.0.0". Then run npx paperclipai allowed-hostname with this Sprite's hostname (get it from sprite-env info). Then register Paperclip as a Sprite service called "paperclip" using sprite-env services create with the command npx (use which npx to get the full path), arg

## Offloading FFmpeg with Cloudflare

DevFeed: [Offloading FFmpeg with Cloudflare](<https://devfeed.tech/articles/offloading-ffmpeg-with-cloudflare-51840.md>)

Original publisher: [Read original article](<https://kentcdodds.com/blog/offloading-ffmpeg-with-cloudflare>)

Published: 2026-03-09T00:00:00Z

Content type: opinion

Language: en

Sources: [Kent C. Dodds Blog](<https://devfeed.tech/sources/kent-c-dodds-blog.md>)

Topics: [FFmpeg (Fast Forward Moving Picture Experts Group)](<https://devfeed.tech/topics/ffmpeg.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [container](<https://devfeed.tech/topics/container.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Server](<https://devfeed.tech/topics/server.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [audio](<https://devfeed.tech/tags/audio.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [code](<https://devfeed.tech/tags/code.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [feature](<https://devfeed.tech/tags/feature.md>), [ffmpeg](<https://devfeed.tech/tags/ffmpeg.md>), [flow](<https://devfeed.tech/tags/flow.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [hit](<https://devfeed.tech/tags/hit.md>), [load](<https://devfeed.tech/tags/load.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [mp3](<https://devfeed.tech/tags/mp3.md>), [offloading](<https://devfeed.tech/tags/offloading.md>), [performance](<https://devfeed.tech/tags/performance.md>), [processing](<https://devfeed.tech/tags/processing.md>), [server](<https://devfeed.tech/tags/server.md>)

### AI overview

A long FFmpeg audio-processing job caused severe CPU saturation on the Fly.io machine serving a website. The author explains moving podcast episode processing off the primary server and onto Cloudflare Queues and Containers.

### Source excerpt

How I moved Call Kent podcast episode processing off my primary Fly.io app server and onto Cloudflare Queues and Containers: what broke, what I missed, and whether it was worth the complexity.

## I Build Everything In Sprites Now

DevFeed: [I Build Everything In Sprites Now](<https://devfeed.tech/articles/i-build-everything-in-sprites-now-122057.md>)

Original publisher: [Read original article](<https://fly.io/blog/i-build-everything-in-sprites-now/>)

Author: Daniel Botha

Published: 2026-02-03T00:00:00Z

Content type: opinion

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [versioning](<https://devfeed.tech/topics/versioning.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cloud-development-environment](<https://devfeed.tech/tags/cloud-development-environment.md>), [costs](<https://devfeed.tech/tags/costs.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [database](<https://devfeed.tech/tags/database.md>), [development](<https://devfeed.tech/tags/development.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [fly-io-sprites](<https://devfeed.tech/tags/fly-io-sprites.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [projects](<https://devfeed.tech/tags/projects.md>), [sprites](<https://devfeed.tech/tags/sprites.md>), [the-fly-blog](<https://devfeed.tech/tags/the-fly-blog.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

The author uses a separate persistent Sprite for each project to avoid conflicts between local runtimes, databases, environment variables, and services. Sprites are described as hardware-isolated Linux computers with 100 GB storage that incur costs only while active; they pause when idle and wake within seconds with services and state restored. Each Sprite provides its own ports and an HTTPS URL, which the author says supports OAuth callbacks, webhooks, and sharing a live project view without tunneling. Checkpoints snapshot the whole environment, including dependencies, database state, services, and environment variables, for restoring experiments. The author also favors a project-specific Claude and context per Sprite, with skills propagated to other Sprites through the API. These are the author's reported workflows and product claims in the supplied text.

### Source excerpt

I just realised I build everything in Sprites now. It feels weird to say because Sprites are still really new (even for people who work at Fly.io). They're obviously super exciting for people building agents, but when I finally "got" Sprites, it pretty much instantly felt weird to build anything anywhere else. If, like me, you have to flit between many projects every day - because breaking only one thing a day is lazy - you'll know that local development is a joke. Let me pause what I'm working on to fix this tiny bug over on this other project! Wrong Node version. asdf local nodejs 18.17.0. Oh wait, this project uses nvm. Fine. nvm use. No .nvmrc file. Check the README. Last updated in 1996. Check package.json engines field. Install that version. Now the wrong packages are installed. Ah, productivity. Oh of course, the wrong database is running. Start Postgres. Wait, this project uses MySQL. Stop Postgres, start MySQL. Except the other project's MySQL data is still there. Where's the docker-compose for this one? Ah I have screwy environment variables, let me just update the ... wait is it .env, .env.local, .env.development, .env.example, env.thisone? This project needs API_KEY set but that collides with the other project's API_KEY which points somewhere else. Swear I have a .env.projectname file somewhere. Maybe. Which shell session has the right exports? Yes! It's running! Wait what was I doing again? No. Just No. Now every project I'm working on is in its own Sprite. It feels like having a different computer for every project because that's exactly what it is. Every Sprite is a persistent, fully hardware isolated linux computer with 100gb storage that only costs anything when it's actually doing something. I can have 30 projects in 30 Sprites and I'm only ever paying for the one I'm currently working on. Wrap text Copy to clipboard sprite create dashboard sprite create api-backend sprite create billion-dollar-side-project Each one has its own versions, its own serv

## The Design & Implementation of Sprites

DevFeed: [The Design & Implementation of Sprites](<https://devfeed.tech/articles/the-design-implementation-of-sprites-1694.md>)

Original publisher: [Read original article](<https://fly.io/blog/design-and-implementation/>)

Published: 2026-01-14T00:00:00Z

Content type: article

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [ssh](<https://devfeed.tech/topics/ssh.md>), [container](<https://devfeed.tech/topics/container.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cost](<https://devfeed.tech/tags/cost.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [linux](<https://devfeed.tech/tags/linux.md>), [networking](<https://devfeed.tech/tags/networking.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [platform](<https://devfeed.tech/tags/platform.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [scale](<https://devfeed.tech/tags/scale.md>), [servers](<https://devfeed.tech/tags/servers.md>), [ssh](<https://devfeed.tech/tags/ssh.md>)

### AI overview

Fly.io's article introduces Sprites, disposable Linux virtual machines designed to start in seconds, provide root access and a durable 100GB filesystem, and automatically sleep when inactive. It explains the orchestration decisions behind the platform, including moving away from container images while retaining convenient, Docker-like workflows.

### Source excerpt

We're Fly.io, and this is the place in the post where we'd normally tell you that our job is to take your containers and run them on our own hardware all around the world. But last week, we launched Sprites, and they don't work that way at all. Sprites are something new: Docker without Docker without Docker. This post is about how they work. Replacement-level homeowners buy boxes of pens and stick them in "the pen drawer". What the elites know: you have to think adversarially about pens. "The purpose of a system is what it does"; a household's is to uniformly distribute pens. Months from now, the drawer will be empty, no matter how many pens you stockpile. Instead, scatter pens every place you could possibly think to look for one -- drawers, ledges, desks. Any time anybody needs a pen, several are at hand, in exactly the first place they look. This is the best way I've found to articulate the idea of Sprites, the platform we just launched at Fly.io. Sprites are ball-point disposable computers. Whatever mark you mean to make, we've rigged it so you're never more than a second or two away from having a Sprite to do it with. Sprites are Linux virtual machines. You get root. They create in just a second or two: so fast, the experience of creating and shelling into one is identical to SSH'ing into a machine that already exists. Sprites all have a 100GB durable root filesystem. They put themselves to sleep automatically when inactive, and cost practically nothing while asleep. As a result, I barely feel the need to name my Sprites. Sometimes I'll just type sprite create dkjsdjk and start some task. People at Fly.io who use Sprites have dozens hanging around. There aren't yet many things in cloud computing that have the exact shape Sprites do: Instant creation No time limits Persistent disk Auto-sleep to a cheap inactive state This is a post about how we managed to get this working. We created a new orchestration stack that undoes some of the core decisions we made for Fly

## Kurt Got Got

DevFeed: [Kurt Got Got](<https://devfeed.tech/articles/kurt-got-got-1701.md>)

Original publisher: [Read original article](<https://fly.io/blog/kurt-got-got/>)

Published: 2025-10-08T00:00:00Z

Content type: article

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [X (Twitter)](<https://devfeed.tech/topics/twitter.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>)

Tags: [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [developer](<https://devfeed.tech/tags/developer.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [networking](<https://devfeed.tech/tags/networking.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [servers](<https://devfeed.tech/tags/servers.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Fly.io describes how its CEO was phished, leading to an account takeover of the company's Twitter/X account. The attack exploited social-engineering cues related to the company's use of developer memes, and the team responded by auditing access to login credentials in 1Password and removing recent access.

### Source excerpt

The $FLY Airdrop is live! Claim your share of the token powering Fly.io's global network of 3M+ apps and (🤮) own a piece of the sky! We know. Our Twitter got owned. We knew within moments of it happening. We know exactly how it happened. Nothing was at risk other than our Twitter account (and one Fly.io employee's self-esteem). Also: for fuck's sake. Here's what happened: Kurt Mackey, our intrepid CEO, got phished. Had this been an impactful attack, we would not be this flippant about it. For this, though, any other tone on our part would be false. How They Got Kurt Two reasons: one, it was a pretty good phishing attack, and two, Twitter fell outside the "things we take seriously" boundary. The phishing attack was effective because it exploited a deep psychological vulnerability in our management team: we are old and out of touch with the youths of today. For many months now, we've had an contractor/intern-type-person Boosting Our Brand on Twitter by posting dank developer memes (I think that's what they're called). The thing about this dankery is that we don't really understand it. I mean, hold on, we know what the memes mean technically. We just don't get why they're funny. However, in pushing back on them, we're up against two powerful forces: The dank memes appear to perform better than the stuff we ourselves write on Twitter. We are reliably informed by our zoomer children that we are too cringe to be trusted on these matters. Here's the phish Kurt got: Diabolical. Like a scalpel expertly wielded against Kurt's deepest middle-aged-dude insecurity. Our ruthless attackers clinically designed this email to trigger an autonomic Kurt response: "oh, what the fuck is this, and why did we post it?" ATO is cool-kid for "got owned" I'm getting a little ahead of the story here. We knew our X.com account had suffered an ATO because a bunch of us simultaneously got another email saying that the @flydotio account's email address now pointed to achilles19969@gmail.com. Our im

## Make your ZeroGPU Spaces go brrr with ahead-of-time compilation

DevFeed: [Make your ZeroGPU Spaces go brrr with ahead-of-time compilation](<https://devfeed.tech/articles/make-your-zerogpu-spaces-go-brrr-with-ahead-of-time-compilation-7575.md>)

Original publisher: [Read original article](<https://huggingface.co/blog/zerogpu-aoti>)

Author: Charles Bensimon; Sayak Paul; Linoy Tsaban; Apolinário from multimodal AI art

Published: 2025-09-02T00:00:00Z

Content type: tutorial

Language: en

Sources: [Hugging Face](<https://devfeed.tech/sources/hugging-face-blog.md>)

Topics: [RAPIDS](<https://devfeed.tech/topics/rapids.md>), [GPU](<https://devfeed.tech/topics/gpu.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [PyTorch](<https://devfeed.tech/topics/pytorch.md>), [quantization](<https://devfeed.tech/topics/quantization.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [compilation](<https://devfeed.tech/tags/compilation.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hugging-face](<https://devfeed.tech/tags/hugging-face.md>), [image-to-image](<https://devfeed.tech/tags/image-to-image.md>), [image-to-video](<https://devfeed.tech/tags/image-to-video.md>), [inference](<https://devfeed.tech/tags/inference.md>), [latency](<https://devfeed.tech/tags/latency.md>), [models](<https://devfeed.tech/tags/models.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [python](<https://devfeed.tech/tags/python.md>), [pytorch](<https://devfeed.tech/tags/pytorch.md>), [quantization](<https://devfeed.tech/tags/quantization.md>), [spaces](<https://devfeed.tech/tags/spaces.md>), [text-to-image](<https://devfeed.tech/tags/text-to-image.md>), [zerogpu](<https://devfeed.tech/tags/zerogpu.md>)

### AI overview

This tutorial explains how to use PyTorch ahead-of-time compilation in ZeroGPU Spaces. It covers faster model startup and inference, FP8 quantization, dynamic shapes, and the process-based GPU allocation model used by ZeroGPU, with reported speedups of 1.3x-1.8x on Flux, Wan, and LTX models.

### Source excerpt

We're on a journey to advance and democratize artificial intelligence through open source and open science.

## Phoenix.new - The Remote AI Runtime for Phoenix

DevFeed: [Phoenix.new - The Remote AI Runtime for Phoenix](<https://devfeed.tech/articles/phoenix-new-the-remote-ai-runtime-for-phoenix-1715.md>)

Original publisher: [Read original article](<https://fly.io/blog/phoenix-new-the-remote-ai-runtime/>)

Published: 2025-06-20T00:00:00Z

Content type: article

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [phoenix](<https://devfeed.tech/topics/phoenix.md>), [Elixir](<https://devfeed.tech/topics/elixir.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [browser](<https://devfeed.tech/topics/browser.md>), [real-time](<https://devfeed.tech/topics/real-time.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [coding](<https://devfeed.tech/tags/coding.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [networking](<https://devfeed.tech/tags/networking.md>), [phoenix](<https://devfeed.tech/tags/phoenix.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [servers](<https://devfeed.tech/tags/servers.md>), [vscode](<https://devfeed.tech/tags/vscode.md>)

### AI overview

Phoenix.new is a fully online coding agent tailored to Elixir and Phoenix. It runs in a browser-backed, isolated Fly Machine with shell access, a VSCode interface, and browser tools that let the agent inspect front-end changes and JavaScript state while building real-time collaborative applications.

### Source excerpt

I'm Chris McCord, the creator of Elixir's Phoenix framework. For the past several months, I've been working on a skunkworks project at Fly.io, and it's time to show it off. I wanted LLM agents to work just as well with Elixir as they do with Python and JavaScript. Last December, in order to figure out what that was going to take, I started a little weekend project to find out how difficult it would be to build a coding agent in Elixir. A few weeks later, I had it spitting out working Phoenix applications and driving a full in-browser IDE. I knew this wasn't going to stay a weekend project. If you follow me on Twitter, you've probably seen me teasing this work as it picked up steam. We're at a point where we're pretty serious about this thing, and so it's time to make a formal introduction. World, meet Phoenix.new, a batteries-included fully-online coding agent tailored to Elixir and Phoenix. I think it's going to be the fastest way to build collaborative, real-time applications. Let's see it in action: What's Interesting About Phoenix.new First, even though it runs entirely in your browser, Phoenix.new gives both you and your agent a root shell, in an ephemeral virtual machine (a Fly Machine) that gives our agent loop free rein to install things and run programs -- without any risk of messing up your local machine. You don't think about any of this; you just open up the VSCode interface, push the shell button, and there you are, on the isolated machine you share with the Phoenix.new agent. Second, it's an agent system I built specifically for Phoenix. Phoenix is about real-time collaborative applications, and Phoenix.new knows what that means. To that end, Phoenix.new includes, in both its UI and its agent tools, a full browser. The Phoenix.new agent uses that browser "headlessly" to check its own front-end changes and interact with the app. Because it's a full browser, instead of trying to iterate on screenshots, the agent sees real page content and JavaScript state

## parking\_lot: ffffffffffffffff...

DevFeed: [parking\_lot: ffffffffffffffff...](<https://devfeed.tech/articles/parking-lot-ffffffffffffffff-1714.md>)

Original publisher: [Read original article](<https://fly.io/blog/parking-lot-ffffffffffffffff/>)

Published: 2025-05-28T00:00:00Z

Content type: article

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Programming language](<https://devfeed.tech/topics/programming-language.md>), [async](<https://devfeed.tech/topics/async.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [bug](<https://devfeed.tech/tags/bug.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [machine](<https://devfeed.tech/tags/machine.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [project](<https://devfeed.tech/tags/project.md>), [protocols](<https://devfeed.tech/tags/protocols.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [public-cloud](<https://devfeed.tech/tags/public-cloud.md>), [regions](<https://devfeed.tech/tags/regions.md>), [request](<https://devfeed.tech/tags/request.md>), [router](<https://devfeed.tech/tags/router.md>), [routing](<https://devfeed.tech/tags/routing.md>), [rust](<https://devfeed.tech/tags/rust.md>), [servers](<https://devfeed.tech/tags/servers.md>)

### AI overview

Fly.io's Anycast router, fly-proxy, must track rapidly changing Machine availability across thousands of servers so it can route requests correctly. Machines may start in under a second or terminate instantly, making distribution of routing state across millions of connections and apps the central challenge. Fly.io describes this as a routing protocol problem and identifies Corrosion as its current protocol. The excerpt introduces the system and its operational constraints but does not include the bug's diagnosis or fix.

### Source excerpt

We're Fly.io, a public cloud that runs apps in a bunch of locations all over the world. This is a post about a gnarly bug in our Anycast router, the largest Rust project in our codebase. You won't need much of any Rust to follow it. The basic idea is simple: customers give us Docker containers, and tell us which one of 30+ regions around the world they want them to run in. We convert the containers into lightweight virtual machines, and then link them to an Anycast network. If you boot up an app here in Sydney and Frankfurt, and a request for it lands in Narita, it'll get routed to Sydney. The component doing that work is called fly-proxy. It's a Rust program, and it has been ill behaved of late. Dramatis Personae fly-proxy, our intrepid Anycast router. corrosion, our intrepid Anycast routing protocol. Rust, a programming language you probably don't use. read-write locks, a synchronization primitive that allows for many readers or one single writer. parking_lot, a well-regarded optimized implementation of locks in Rust. Gaze not into the abyss, lest you become recognized as an abyss domain expert, and they expect you keep gazing into the damn thing Mathewson 6:31 Anycast Routing You already know how to build a proxy. Connection comes in, connection goes out, copy back and forth. So for the amount of time we spend writing about fly-proxy, you might wonder what the big deal is. To be fair, in the nuts and bolts of actually proxying requests, fly-proxy does some interesting stuff. For one thing, it's written in Rust, which is apparently a big deal all on its own. It's a large, asynchronous codebase that handles multiple protocols, TLS termination, and certificate issuance. It exercises a lot of Tokio features. But none of this is the hard part of fly-proxy. We operate thousands of servers around the world. A customer Fly Machine might get scheduled onto any of them; in some places, the expectation we set with customers is that their Machines will potentially start in l

## Launching MCP Servers on Fly.io

DevFeed: [Launching MCP Servers on Fly.io](<https://devfeed.tech/articles/launching-mcp-servers-on-fly-io-1709.md>)

Original publisher: [Read original article](<https://fly.io/blog/mcp-launch/>)

Published: 2025-05-19T00:00:00Z

Content type: opinion

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [Security](<https://devfeed.tech/topics/security.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [json](<https://devfeed.tech/tags/json.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [networking](<https://devfeed.tech/tags/networking.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [servers](<https://devfeed.tech/tags/servers.md>), [slack](<https://devfeed.tech/tags/slack.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

This opinionated blog post introduces Fly.io's approach to launching MCP Servers. It explains the trade-offs between local process-based servers and remote HTTP servers, including configuration complexity and OAuth 2.1 security requirements, then demonstrates a Slack MCP Server for interacting with Slack workspaces.

### Source excerpt

This is a blog post. Part showing off. Part opinion. Plan accordingly. The Model Context Protocol is days away from turning six months old. You read that right, six months old. MCP Servers have both taken the world by storm, and still trying to figure out what they want to be when they grow up. There is no doubt that MCP servers are useful. But their appeal goes beyond that. They are also simple and universal. What's not to like? Well, for starters, there's basically two types of MCP servers. One small and nimble that runs as a process on your machine. And one that is a HTTP server that runs presumably elsewhere and is standardizing on OAuth 2.1. And there is a third type, but it is deprecated. Next there is the configuration. Asking users to manually edit JSON seems so early 21th century. With Claude, this goes into ~/Library/Application Support/Claude/claude_desktop_config.json, and is found under a MCPServer key. With Zed, this file is in ~/.config/zed/settings.json and is found under a context_servers key. And some tools put these files in a different place depending on whether you are running on MacOS, Linux, or Windows. Finally, there is security. An MCP server running on your machine literally has access to everything you do. Running remote solves this problem, but did I mention OAuth 2.1? Not exactly something one sets up for casual use. None of these issues are fatal - something that is obvious by the fact that MCP servers are quite popular. But can we do better? I think so. Demo time. Let's try out the Slack MCP Server: MCP Server for the Slack API, enabling Claude to interact with Slack workspaces. That certainly sounds like a good test case. There is a small amount of setup you need to do, and when you are done you end up with a Bot User OAuth Token staring with xoxb- and a Team ID starting with a T. You would run it using the following: Wrap text Copy to clipboard npx -y @modelcontextprotocol/server-slack But instead, you convert that command to JSON an

## Provisioning Machines using MCPs

DevFeed: [Provisioning Machines using MCPs](<https://devfeed.tech/articles/provisioning-machines-using-mcps-1710.md>)

Original publisher: [Read original article](<https://fly.io/blog/mcp-provisioning/>)

Published: 2025-05-07T00:00:00Z

Content type: article

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [claude](<https://devfeed.tech/tags/claude.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [commands](<https://devfeed.tech/tags/commands.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [delete](<https://devfeed.tech/tags/delete.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [effort](<https://devfeed.tech/tags/effort.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [list](<https://devfeed.tech/tags/list.md>), [llms](<https://devfeed.tech/tags/llms.md>), [machine](<https://devfeed.tech/tags/machine.md>), [machines](<https://devfeed.tech/tags/machines.md>), [mcps](<https://devfeed.tech/tags/mcps.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>), [servers](<https://devfeed.tech/tags/servers.md>)

### AI overview

The author describes using an MCP integration for Fly.io to create and manage volumes through an LLM. After adding volume creation support to the Fly MCP server, they later added the other volume commands with GitHub Copilot. Claude listed volumes for an app and identified unattached ones; the author asked it to delete the oldest, and it did. The author found this more direct than writing code against the machines API or consulting flyctl documentation, and noted the dashboard then lacked volume sorting and deletion. They say the integration would return an error if asked to destroy a mounted volume, which gave them confidence to try the command. The excerpt presents this as an intuitive way to change app resources, while its proposed future workflow is cut off.

### Source excerpt

Today's state of the art is K8S, Terraform, web based UIs, and CLIs. Those days are numbered. On Monday, I created my first fly volume using an MCP. For those who don't know what MCPs are, they are how you attach tools to LLMs like Claude or Cursor. I added support for fly volume create to fly mcp server, and it worked the first time. A few hours later, and with the assistance of GitHub Copilot, i added support for all fly volumes commands. This movie summary is from When Worlds Collide, by Nalaka Gunawardene I'm reminded of the memorable scene in the film Star Trek IV: The Voyage Home (1986). Chief Engineer Scotty, having time-travelled 200 years back to late 20th century San Francisco with his crew mates, encounters an early Personal Computer (PC). Sitting in front of it, he addresses the machine affably as "Computer!" Nothing happens. Scotty repeats himself; still no response. He doesn't realise that voice recognition capability hadn't arrived yet. Exasperated, he picks up the mouse and speaks into it: "Hello, computer?" The computer's owner offers helpful advice: "Just use the keyboard." Scotty looks astonished. "A keyboard?" he asks, and adds in a sarcastic tone: "How quaint!" A while later, I asked for a list of volumes for an existing app, and Claude noted that I had a few volumes that weren't attached to any machines. So I asked it to delete the oldest unattached volume, and it did so. Then it occurred to me to do it again; this time I captured the screen: A few notes: I could have written a program using the machines API, but that would have required some effort. I could have used flyctl directly, but to be honest, I would have had to use the documentation and a bit of copy/pasting of arguments. I could have navigated to a list of volumes for this application in the Fly.io dashboard, but there currently isn't any way to sort the list or delete a volume. Had those been in place, that would have been a reasonable alternative if that was something I was active

## Our Best Customers Are Now Robots

DevFeed: [Our Best Customers Are Now Robots](<https://devfeed.tech/articles/our-best-customers-are-now-robots-1697.md>)

Original publisher: [Read original article](<https://fly.io/blog/fuckin-robots/>)

Published: 2025-04-08T00:00:00Z

Content type: opinion

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Vibe coding](<https://devfeed.tech/topics/vibe-coding.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [container](<https://devfeed.tech/topics/container.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [cdn](<https://devfeed.tech/tags/cdn.md>), [cli](<https://devfeed.tech/tags/cli.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [servers](<https://devfeed.tech/tags/servers.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>)

### AI overview

Fly.io argues that AI-driven "robots" and vibe coding are becoming major sources of platform growth, potentially making traditional developer experience less decisive. The article describes Fly.io's cloud as a service that turns Docker containers into hardware-isolated virtual machines and emphasizes its CLI-first workflow for containerizing and deploying applications.

### Source excerpt

We're Fly.io, a developer-focused public cloud. We turn Docker containers into hardware-isolated virtual machines running on our own metal around the world. We spent years coming up with a developer experience we were proud of. But now the robots are taking over, and they don't care. It's weird to say this out loud! For years, one of our calling cards was "developer experience". We made a decision, early on, to be a CLI-first company, and put a lot effort into making that CLI seamless. For a good chunk of our users, it really is the case that you can just flyctl launch from a git checkout and have an app containerized and deployed on the Internet. We haven't always nailed these details, but we've really sweated them. But a funny thing has happened over the last 6 months or so. If you look at the numbers, DX might not matter that much. That's because the users driving the most growth on the platform aren't people at all. They're... robots. What The Fuck Is Happening? Here's how we understand what we're seeing. You start by asking, "what do the robots want?" Yesterday's robots had diverse interests. Alcohol. The occasional fiddle contest. A purpose greater than passing butter. The elimination of all life on Earth and the harvesting of its cellular iron for the construction of 800 trillion paperclips. No one cloud platform could serve them all. [*] We didn't make up this term. Don't blame us. Today's robots are different. No longer masses of wire, plates, and transistors, modern robots are comprised of thousands of stacked matrices knit together with some simple equations. All these robots want are vectors. Vectors, and a place to burp out more vectors. When those vectors can be interpreted as source code, we call this process "vibe coding"[*]. We seem to be coated in some kind of vibe coder attractant. I want to talk about what that might be. If you want smart people to read a long post, just about the worst thing you can do is to sound self-promotional. But a lot of th

## Taming A Voracious Rust Proxy

DevFeed: [Taming A Voracious Rust Proxy](<https://devfeed.tech/articles/taming-a-voracious-rust-proxy-1718.md>)

Original publisher: [Read original article](<https://fly.io/blog/taming-rust-proxy/>)

Published: 2025-02-26T00:00:00Z

Content type: article

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [Rust](<https://devfeed.tech/topics/rust.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Tokio](<https://devfeed.tech/topics/tokio.md>), [container](<https://devfeed.tech/topics/container.md>), [Network](<https://devfeed.tech/topics/network.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [cpu](<https://devfeed.tech/topics/cpu.md>)

Tags: [async](<https://devfeed.tech/tags/async.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [http](<https://devfeed.tech/tags/http.md>), [i](<https://devfeed.tech/tags/i.md>), [incident](<https://devfeed.tech/tags/incident.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [rust](<https://devfeed.tech/tags/rust.md>), [servers](<https://devfeed.tech/tags/servers.md>), [tokio](<https://devfeed.tech/tags/tokio.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>)

### AI overview

The article investigates a recurring CPU and HTTP-error incident affecting Fly.io edge proxies. Profiling reveals unexpectedly high overhead in Rust tracing's Subscriber while the proxy handles largely idle asynchronous work, leading into a review of async Rust futures and Tokio execution.

### Source excerpt

Here's a fun bug. The basic idea of our service is that we run containers for our users, as hardware-isolated virtual machines (Fly Machines), on hardware we own around the world. What makes that interesting is that we also connect every Fly Machine to a global Anycast network. If your app is running in Hong Kong and Dallas, and a request for it arrives in Singapore, we'll route it to HKG. Our own hardware fleet is roughly divided into two kinds of servers: edges, which receive incoming requests from the Internet, and workers, which run Fly Machines. Edges exist almost solely to run a Rust program called fly-proxy, the router at the heart of our Anycast network. So: a week or so ago, we flag an incident. Lots of things generate incidents: synthetic monitoring failures, metric thresholds, health check failures. In this case two edge tripwires tripped: elevated fly-proxy HTTP errors, and skyrocketing CPU utilization, on a couple hosts in IAD. Our incident process is pretty ironed out at this point. We created an incident channel (we ❤ Rootly for this, seriously check out Rootly, an infra MVP here for years now), and incident responders quickly concluded that, while something hinky was definitely going on, the platform was fine. We have a lot of edges, and we've also recently converted many of our edge servers to significantly beefier hardware. Bouncing fly-proxy clears the problem up on an affected proxy. But this wouldn't be much of an interesting story if the problem didn't later come back. So, for some number of hours, we're in an annoying steady-state of getting paged and bouncing proxies. While this is happening, Pavel, on our proxy team, pulls a profile from an angry proxy. So, this is fuckin' weird: a huge chunk of the profile is dominated by Rust tracing's Subscriber. But that doesn't make sense. The entire point of Rust tracing, which generates fine-grained span records for program activity, is that entering and exiting a span is very, very fast. If the mere

## Self-Hosting with Convex: Everything You Need to Know

DevFeed: [Self-Hosting with Convex: Everything You Need to Know](<https://devfeed.tech/articles/self-hosting-with-convex-everything-you-need-to-know-81443.md>)

Original publisher: [Read original article](<https://stack.convex.dev/self-hosted-develop-and-deploy>)

Author: Stack

Published: 2025-02-13T15:00:00Z

Content type: tutorial

Language: en

Sources: [Stack](<https://devfeed.tech/sources/stack.md>)

Topics: [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [cloud-sql](<https://devfeed.tech/topics/cloud-sql.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Nextcloud](<https://devfeed.tech/topics/nextcloud.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [advanced](<https://devfeed.tech/tags/advanced.md>), [automated-testing](<https://devfeed.tech/tags/automated-testing.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [convex](<https://devfeed.tech/tags/convex.md>), [database](<https://devfeed.tech/tags/database.md>), [database-migration](<https://devfeed.tech/tags/database-migration.md>), [docker](<https://devfeed.tech/tags/docker.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [neon](<https://devfeed.tech/tags/neon.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [production](<https://devfeed.tech/tags/production.md>), [self-hosting](<https://devfeed.tech/tags/self-hosting.md>)

### AI overview

This guide explains how to self-host a Convex backend and dashboard using Fly.io or Docker, connect a frontend, and use SQLite or Postgres such as Neon. It outlines benefits including data control and local testing, along with operational responsibilities such as scaling, migrations, backups, and monitoring.

### Source excerpt

Learn how to self-host Convex, the reactive database and backend. This guide covers setup with Docker, Fly.io, and Neon.tech, plus pros and cons of self-hosting vs. cloud hosting.

## Do It Yourself Database CDN with Embedded Replicas

DevFeed: [Do It Yourself Database CDN with Embedded Replicas](<https://devfeed.tech/articles/do-it-yourself-database-cdn-with-embedded-replicas-5935.md>)

Original publisher: [Read original article](<https://turso.tech/blog/do-it-yourself-database-cdn-with-embedded-replicas>)

Author: Jamie Barton

Published: 2025-02-12T00:00:00Z

Content type: article

Language: en

Sources: [Turso](<https://devfeed.tech/sources/turso-blog.md>)

Topics: [Embedded Replicas](<https://devfeed.tech/topics/embedded-replicas.md>), [Turso](<https://devfeed.tech/topics/turso.md>), [Database](<https://devfeed.tech/topics/database.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Replication](<https://devfeed.tech/topics/replication.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [embedded-replicas](<https://devfeed.tech/tags/embedded-replicas.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [replication](<https://devfeed.tech/tags/replication.md>), [turso](<https://devfeed.tech/tags/turso.md>)

### AI overview

The article is titled "Do It Yourself Database CDN with Embedded Replicas" and concerns deploying Turso Edge Replicas with Embedded Replicas and Fly.io. The supplied text also notes that the post references an older version of Turso.

### Source excerpt

Deploy your own Turso Edge Replicas with Embedded Replicas and Fly.io

## A Blog, If You Can Keep It

DevFeed: [A Blog, If You Can Keep It](<https://devfeed.tech/articles/a-blog-if-you-can-keep-it-1686.md>)

Original publisher: [Read original article](<https://fly.io/blog/a-blog-if-kept/>)

Published: 2025-02-10T00:00:00Z

Content type: opinion

Language: en

Sources: [Fly](<https://devfeed.tech/sources/the-fly-blog.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Publishing](<https://devfeed.tech/topics/publishing.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [close-to-users](<https://devfeed.tech/tags/close-to-users.md>), [deploy-app-servers](<https://devfeed.tech/tags/deploy-app-servers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [elixir](<https://devfeed.tech/tags/elixir.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [go](<https://devfeed.tech/tags/go.md>), [heroku-alternative](<https://devfeed.tech/tags/heroku-alternative.md>), [heroku-competitor](<https://devfeed.tech/tags/heroku-competitor.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [i](<https://devfeed.tech/tags/i.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql-clusters](<https://devfeed.tech/tags/postgresql-clusters.md>), [servers](<https://devfeed.tech/tags/servers.md>), [technical](<https://devfeed.tech/tags/technical.md>), [writing](<https://devfeed.tech/tags/writing.md>)

### AI overview

A Fly.io team member reflects on the company's use of long-form technical EffortPosts to reach Hacker News audiences. The article argues that strict editorial processes, perfectionism, and concern about exhausting the audience have slowed publication, and describes a shift toward publishing more freely.

### Source excerpt

A boldfaced lede like this was a sure sign you were reading a carefully choreographed EffortPost from our team at Fly.io. We're going to do less of those. Or the same amount but more of a different kind of post. Either way: launch an app on Fly.io today! Over the last 5 years, we've done pretty well for ourselves writing content for Hacker News. And that's mostly been good for us. We don't do conventional marketing, we don't have a sales team, the rest of social media is atomized over 5 different sites. Writing pieces that HN takes seriously has been our primary outreach tool. There's a recipe (probably several, but I know this one works) for charting a post on HN: Write an EffortPost, which is to say a dense technical piece over 2000 words long; within that rubric there's a bunch of things that are catnip to HN, including runnable code, research surveys, and explainers. (There are also cat-repellants you learn to steer clear of.) Assiduously avoid promotion. You have to write for the audience. We get away with sporadically including a call-to-action block in our posts, but otherwise: the post should make sense even if an unrelated company posted it after you went out of business. Pick topics HN is interested in (it helps if all your topics are au courant for HN, and we've been very lucky in that regard). Like 5-6 more style-guide things that help incrementally. Probably 3 different teams writing for HN will have 3 different style guides with only like ½ overlap. Ours, for instances, instructs writers to swear. I like this kind of writing. It's not even a chore. But it's become an impediment for us, for a couple reasons: the team serializes behind an "editorial" function here, which keeps us from publishing everything we want; worse, caring so much about our track record leaves us noodling on posts interminably (the poor Tigrises have been waiting for months for me to publish the piece I wrote about them and FoundationDB; take heart, this post today means that one i

## Deploying applications to Fly.io without Docker

DevFeed: [Deploying applications to Fly.io without Docker](<https://devfeed.tech/articles/deploying-applications-to-fly-io-without-docker-38534.md>)

Original publisher: [Read original article](<https://msfjarvis.dev/posts/deploying-applications-to-flyio-without-docker/>)

Author: Harsh Shandilya

Published: 2024-10-05T06:30:00Z

Content type: tutorial

Language: en

Sources: [Posts on Harsh Shandilya](<https://devfeed.tech/sources/posts-on-harsh-shandilya.md>)

Topics: [fly.io](<https://devfeed.tech/topics/fly-io.md>), [Skopeo](<https://devfeed.tech/topics/skopeo.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Docker Image](<https://devfeed.tech/topics/docker-image.md>), [Nix](<https://devfeed.tech/topics/nix.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-image](<https://devfeed.tech/tags/docker-image.md>), [docker-registry](<https://devfeed.tech/tags/docker-registry.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [nix](<https://devfeed.tech/tags/nix.md>), [oci-registry](<https://devfeed.tech/tags/oci-registry.md>), [skopeo](<https://devfeed.tech/tags/skopeo.md>)

### AI overview

A guide to deploying applications on Fly.io without installing Docker locally. It explains how to use Nix to build an OCI image and Skopeo to copy the image archive to Fly.io's registry before deployment.

### Source excerpt

A quick guide to deploying apps to Fly.io without a local Docker installation

[Next page](<https://devfeed.tech/topics/fly-io.md?cursor=WyIyMDI0LTEwLTA1VDA2OjMwOjAwKzAwOjAwIiwgIjdiZGMyZGI3LTYwNzEtNGNlNi04ZDY3LWE3ZGJiMmVlOGIzZiJd>)