From 2009-2023, my web stack most often included Heroku but I wanted to move to a new provider. I created a webstack repo to prototype options.

Based on the users of the primary web app I work on, I set up API checks via Checkly from Northern California and London.

The hosting providers I tested the most were:

The Postgres databases I tested the most were:

I also spent some time with Vercel, PlanetScale, Supabase, Cockroach, and Fly.io SQLite. See the repo for details on those; they aren't covered in this article.

Each stack served a healthcheck-style HTTP API endpoint that executed a SELECT 1 to a SQL database and responded with JSON {"status":"ok"}. Each stack used a lightweight router, a SQL database driver (no ORM), and a database connection pool. Most stacks were written in Go. Example:

package main

import (


func main() {
	// env
	port, ok := os.LookupEnv("PORT")
	if !ok {
		port = "8080"
	dbUrl, ok := os.LookupEnv("DATABASE_URL")
	if !ok {
		dbUrl = "postgres:///webstack_dev"

	// db
	db, err := pgxpool.Connect(context.Background(), dbUrl)
	if err != nil {
	defer db.Close()

	// routes
	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		var col int
		db.QueryRow(r.Context(), "SELECT 1").Scan(&col)
		w.Header().Set("Content-Type", "application/json")
		fmt.Fprintf(w, "{\"status\":\"ok\"}")

	// listen
	log.Println("Listening at http://localhost:" + port)
	log.Fatal(http.ListenAndServe(":"+port, nil))

Neon and Crunchy Bridge offer connection pooling via PgBouncer, which I enabled. See Neon docs, and Crunchy Bridge docs. In Neon, you enable it with a web UI toggle. In Crunchy Bridge, you enable it by `psql`'ing into your cluster and running CREATE EXTENSION crunchy_pooler;.


My baseline Heroku workflow has historically been:

While performance and reliability have been very good on Heroku, I wanted to migrate off due to the platform's offerings beginning to stagnate. My confidence was particularly shaken when its GitHub integration broke in April 2022 and it took over a month to be resolved.

Heroku lacked some long overdue features such as HTTP/2 support and it was not possible to restrict access to its Postgres database from public internet without a major increase in cost.













My stack choice

For the app I work on, I ended up choosing Render and Crunchy Bridge Postgres.

It felt like the smallest step from Heroku. I felt both companies were mature organizations and reliability for my software would be good. I am "all-in" on Postgres; I use it as my queuing system and have no other databases such as Redis.

Recommendations for others

Consider Fly if your priorities are multi-region, low-latency, or lowest cost.

Consider Northflank if your app and users are mainly in Europe, or if your mindset is particularly oriented around Docker or Kubernetes.

Consider Railway if your priorities are fast build times or you want to interact with your infrastructure primarily via web UI.

Consider Aiven if you have multiple database types you want managed such as some combination of Postgres, Redis, Kafka, or ElasticSearch.

Consider Crunchy Bridge if you are "all-in" on Postgres and want your database tooling and support to be optimized around Postgres.