---
title: "Turboku - The Art Of Faster Heroku Apps"
description: "Turboku is a migration path that automatically turns Heroku web dynos into Fly applications, addressing how existing Heroku apps can move to Fly’s globally distributed edge network. Fly routes requests to the closest datacenter through one global IP address, or two with IPv6, while TLS terminates closer to users and modern ECDSA certificates are automatic for Fly domains. A benchmark around the world used an existing application to compare Heroku and Fly connection stages, full requests, and cached requests. Fly reduced DNS, TCP, TLS, network, and full-request times, with the largest reported improvement appearing when caching was used: 180.16 ms versus Heroku’s 817.75 ms, a 77.91% reduction; uncached full requests fell 35.39%, while TTFB was 1.24% higher."
---

# Turboku - The Art Of Faster Heroku Apps

[Fly.io](https://yomu.fyi/company/fly-io) · Feb 5, 2020

**Type:** Benchmark

## Summary

Turboku is a migration path that automatically turns Heroku web dynos into Fly applications, addressing how existing Heroku apps can move to Fly’s globally distributed edge network. Fly routes requests to the closest datacenter through one global IP address, or two with IPv6, while TLS terminates closer to users and modern ECDSA certificates are automatic for Fly domains. A benchmark around the world used an existing application to compare Heroku and Fly connection stages, full requests, and cached requests. Fly reduced DNS, TCP, TLS, network, and full-request times, with the largest reported improvement appearing when caching was used: 180.16 ms versus Heroku’s 817.75 ms, a 77.91% reduction; uncached full requests fell 35.39%, while TTFB was 1.24% higher.

## Context

Existing Heroku applications need a way to move to Fly so they can run around the globe, closer to users, on Fly’s edge network. The post evaluates whether that change improves connection and request performance.

## Approach / What changed

Turboku automatically converts Heroku web dynos into Fly applications. Fly routes traffic to the closest datacenter using a globally working IP address, terminates TLS near users, and provides automatic ECDSA certificates for Fly domains. The post compares Heroku and Fly timings around the world using an existing application.

## Takeaways

- Turboku converts Heroku web dynos into Fly applications automatically, allowing them to deploy to Fly’s global edge network.
- Fly’s benchmark reduced TLS time from 225.28 ms to 33.41 ms and network time from 353.68 ms to 58.53 ms.
- With caching enabled, the measured request time was 180.16 ms on Fly versus 817.75 ms on Heroku; uncached TTFB was slightly higher on Fly.

**Tags:** [Caching](https://yomu.fyi/topic/caching), [Fly.io](https://yomu.fyi/topic/fly-io), [Heroku](https://yomu.fyi/topic/heroku), [Performance](https://yomu.fyi/topic/performance)

- Source: [Fly.io](https://fly.io/blog/turboku)
- Source URL: https://fly.io/blog/turboku
- Ingested by Yomu: 2026-09-02T11:57:47.030Z

[Read original post](https://fly.io/blog/turboku)