Fly.io runs your applications in light-weight micro-VMs called Fly Machines instead of containers, but why is this? The short answer: Isolation. In this video, we'll explore a few different categories of isolation and what kind of security they provide.

An Intro to Fly Machines:
https://fly.io/docs/machines/overview/

Machines API:
https://fly.io/docs/machines/api/

Fly Kubernetes:
https://fly.io/docs/kubernetes/

Fly.io offers insights into edge computing, serverless architecture, and global content delivery network (CDN), providing documentation, tutorials, and best practices for deploying and scaling applications at the network edge. By exploring Fly.io's curated content, developers can learn about Fly's edge computing platform, distributed application runtime, and HTTP/2 load balancing for building fast, secure, and scalable web applications. Whether you're optimizing latency for global users, offloading compute-intensive tasks, or deploying microservices, Fly.io offers resources to supercharge your application performance and reliability.

Fly.io

We don't use containers, and here's why.

<p>To save your time: They use Firecracker VMs because their business model is running other people’s untrusted code. A good tradeoff between security and hardware overhead, still the miniature is personally pissing me off.</p>
