# Autoscaling Lakebase Postgres

DevFeed: [Autoscaling Lakebase Postgres](<https://devfeed.tech/articles/autoscaling-lakebase-postgres-5008.md>)

Original publisher: [Read original article](<https://neon.com/blog/autoscaling-lakebase-postgres>)

Author: Carlota Soto

Published: 2026-08-31T12:00:00Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [cpu](<https://devfeed.tech/topics/cpu.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [cache](<https://devfeed.tech/tags/cache.md>), [compute](<https://devfeed.tech/tags/compute.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [database](<https://devfeed.tech/tags/database.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [memory](<https://devfeed.tech/tags/memory.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [storage](<https://devfeed.tech/tags/storage.md>)

## AI overview

The article explains how Lakebase Postgres autoscales database compute without stopping Postgres. Its architecture separates compute from durable storage, while the autoscaler derives a target size from CPU load, memory use, and compute-cache working-set size.

## Source excerpt

Choosing a database instance size before you know the workload is an old building pattern. Lakebase Postgres omits the sizing experience altogether thanks to autoscaling.