March 7, 2026
Magic or mirage?
Migrating from Heroku to Magic Containers
Heroku slows; Bunny’s 'Magic' brings nostalgia, sticker shock, and 'is this Cloud Run' vibes
TLDR: Heroku is freezing new features, and bunny.net’s Magic Containers is pitching itself as the next stop. Commenters argue it lacks Heroku’s push-and-go ease, balk at pricing, and some are jumping to DigitalOcean or comparing cheaper Cloudflare options — the real fight is convenience versus cost.
Heroku just tapped the brakes on new features, and the dev world is in its feelings. Enter Magic Containers from bunny.net: it promises a clean landing, but the comments lit up fast. One camp mourns the old Heroku “git push and chill” era, saying the magic sauce was not thinking about containers at all. Now you’re building app “images,” picking a registry, and clicking through dashboards — the vibe is “Cloud Run, but with extra steps.” Others only realized mid-thread that Magic Containers is a bunny.net product, which added to the confusion.
Then came the sticker shock. A top comment did the math: “almost a dollar an hour” can balloon to ~$700 a month if you’re always on, while Cloudflare’s take might land closer to $70–$80. Meanwhile, pragmatic voices are already packing: one team flat-out said they “picked DigitalOcean” because it feels Heroku-ish without big-cloud headaches. Skeptics piled on missing features too — like only pulling app images from two places — and wondered what else isn’t there yet.
The memes wrote themselves: farewell to “git push heroku master,” hello to Docker gym class. Is Bunny’s Magic the rebound we need, or just a shiny new situationship for burned teams?
Key Points
- •On Feb 6, 2026, Heroku announced a shift to a sustaining engineering model with no new features or enterprise contracts.
- •The article proposes migrating Heroku apps to Magic Containers and maps key concepts (e.g., Dyno→Container, Buildpack→Docker image).
- •Magic Containers deploys standard Docker images from Docker Hub or GitHub Container Registry (public or private).
- •It supports multi-container apps with localhost communication, persistent volumes, and networking over HTTP, TCP, and UDP via global Anycast.
- •Deployments use CI/CD-built images selected in a dashboard; autoscaling is enabled by default with configurable behavior.