Alternative

Neon alternatives for production PostgreSQL in your own cloud

Community PostgreSQL sized for a steady production workload and run 24/7 by AceMQ engineers in our cloud, your cloud account or your data center.

45 minutes with an engineer: we review your workload and sketch the design.

  • Operated by AceMQ
  • PostgreSQL
Neon → OSStend · at a glance

OSStend is a Neon alternative for teams whose serverless Postgres has become a steady production database. It runs dedicated community PostgreSQL, sized and configured for the workload, in our cloud, your AWS, Azure or Google Cloud account, or your data center, with AceMQ engineers on call 24/7. Neon remains the better fit for branch-per-PR development databases.

160+AceMQ customers
10+Years running these systems
24/7Engineers on call
3Places it runs: our cloud, yours, your data center
Engines we run, on the platforms you already use
  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Valkey
  • OpenSearch
  • Kafka
  • RabbitMQ
  • AWS
  • Google Cloud
  • Azure
  • Kubernetes
  • OpenShift
  • Prometheus
  • Grafana
  • Datadog
  • Dynatrace
  • Splunk
Compare

Neon and OSStend at a glance

Neon is a serverless Postgres that Databricks announced its intent to acquire in May 2025, priced by compute-hour. OSStend runs dedicated PostgreSQL sized for the workload, wherever it has to run.

OSStendNeon
What it isManaged community PostgreSQL, dedicated and tailored per workloadServerless Postgres; its pricing page names the product Lakebase Postgres (Neon pricing)
Where it runsOur cloud, your AWS, Azure or Google Cloud account, your data center8 AWS regions; new projects can no longer be created in Azure regions (Neon regions)
Compute modelDedicated nodes sized to the measured loadBilled per compute-unit (CU) hour; scale to zero after 5 minutes idle on the Free plan (Neon pricing)
PricingPrice drivers on pricingFrom $0.106 per CU-hour on Launch (Neon pricing)
OwnershipOperated by AceMQDatabricks announced its intent to acquire Neon on 14 May 2025 (Databricks)
Who runs itNamed AceMQ engineers, 24/7Neon operates the service

Sources: Neon pricing and regions pages and the Databricks announcement, checked 15 Nov 2026.

Operated by AceMQCompany figures, as published on acemq.com
160+customers served by AceMQ, which operates OSStend
10+years running open source data and messaging
24/7on-call engineers, not a ticket queue

Why teams look for a Neon alternative

Four reasons come up: an ownership change, no new Azure projects, a database that never idles and a requirement to run it somewhere Neon does not. Each one is sourced below.

Illustrative: plan names and shapes stand in for any provider's menu.
Ownership change.
Databricks announced its intent to acquire Neon on 14 May 2025 (Databricks, checked 15 Nov 2026). Customers ask what that means for a database they run today. The announcement is the source here, not a forecast.
Azure.
Neon's regions page says "You can no longer create new projects in Azure regions" (Neon regions, checked 15 Nov 2026).
Steady load.
A database that never scales to zero pays the CU-hour rate around the clock. At the Scale list price of $0.222 per CU-hour, 4 CU for 730 hours is $648.24 a month of compute before storage (Neon pricing; illustrative, list price, checked 15 Nov 2026).
Where it must run.
A data center, an air-gapped site or your own cloud account. Neon's regions page lists Neon-run AWS regions only.
A fair snapshot

A fair snapshot of Neon

Neon does several things well for development and variable workloads. Each fact below carries the page it came from.

  • Branching: the Free plan lists 10 branches per project, and scale to zero after 5 minutes idle (Neon pricing, checked 15 Nov 2026).
  • Free plan limits: 100 projects, 100 CU-hours per project, up to 2 CU (8 GB RAM) and 1 GB of storage per project (Neon pricing, checked 15 Nov 2026).
  • Compute ceilings: 16 CU (64 GB RAM) on Launch, and on Scale up to 56 CU (224 GB RAM) (Neon pricing, checked 15 Nov 2026).
  • Compliance as listed by Neon: ISO 27001 and 27701 certified, SOC 2 audited, GDPR and CCPA compliant on all plans, and HIPAA on Scale with a BAA (Neon pricing, checked 15 Nov 2026).
  • Free-plan projects inactive for 90 days or more are subject to deletion as of 5 October 2026 (Neon regions, checked 15 Nov 2026).

Where Neon is the better choice: development and preview databases per branch or pull request, spiky or idle workloads that benefit from scale to zero, and teams that want self-serve sign-up.

Compare

Full comparison: OSStend and Neon

OSStend is listed first. The Neon column comes from its public pages with the date checked, and it covers what Neon does well.

FactorOSStendNeon
Good fitSteady production PostgreSQL that must run in your account, in Azure or in a data center; tailored extensions and configurationDevelopment and preview databases per branch; spiky or idle workloads; self-serve teams
Poor fitBranch-per-PR development databases, free tiers, card sign-upProduction databases that must sit in a data center or your own cloud account
Where it runsOur cloud, your cloud account, your data center, Kubernetes or OpenShift, air-gapped8 AWS regions, fixed when the project is created (Neon regions)
TailoringExtensions, configuration, versions and upgrade calendar designed with youWithin Neon's plans
MigrationOSStend runs and owns the cutover, with both sides live until you switchYour team plans and runs it
Service levelsWritten SLA per plan (see service levels)An uptime SLA is listed on the Scale plan only (Neon pricing)
Pricing modelPrice drivers: size, SLA tier, where it runs. See pricingPer CU-hour and per GB-month (Neon pricing)

Sources: Neon pricing and regions pages, checked 15 Nov 2026. Tailoring and migration cells are descriptive.

Enterprise only

How OSStend does it

OSStend designs the PostgreSQL cluster around the workload, moves the data across with both sides live and runs it 24/7 with named AceMQ engineers. It is enterprise only, with no free tier or card sign-up. The first step is a 45-minute workload review with an engineer: the current setup is reviewed, the design is sketched, and a price follows for that design.

Fully managed in our cloud or yours, or co-managed in your data center. See managed PostgreSQL and bring your own cloud.

Contact us if

  • A steady production load, with no idle periods to scale away.
  • The database must run in your account, in Azure or in a data center.
  • You need tailored extensions or configuration, and a named on-call team.
Talk to an engineer

Not a fit if

  • You want per-branch development databases: Neon fits.
  • Scale to zero matters most.
  • You want self-serve sign-up or a free tier.
Pricing

Neon pricing and what OSStend's price depends on

Neon lists three plans: Free at $0, Launch at $0.106 per CU-hour and Scale at $0.222 per CU-hour, with storage at $0.35 per GB-month on both paid plans (Neon pricing, checked 15 Nov 2026). OSStend prices the design, and the drivers are the engine, the size, the service level tier and where it runs.

Neon planComputeStorageCompute ceiling
Free100 CU-hours per project1 GB per project2 CU / 8 GB RAM
Launch$0.106 per CU-hour$0.35 per GB-month16 CU / 64 GB RAM
Scale$0.222 per CU-hour$0.35 per GB-monthUp to 56 CU / 224 GB RAM

Source: Neon pricing, checked 15 Nov 2026. Neon's own typical-spend examples for Postgres compute and storage: $15 a month on Launch and $31 on Scale for an intermittent load, $353 on Launch and $701 on Scale for a high load.

Prices are quoted per design, after the workload review, so the figure is for the cluster you need rather than a plan size. Send the engine, rough size and where it must run, and the engineer prices that design.

To compare, take the CU-hours, storage and branches you run today and price the same shape on both sides. See pricing, and the list prices of seven services in managed PostgreSQL pricing compared, or Neon vs Supabase for the two platforms side by side.

Neon pricing at production scale

At Neon's list prices, a database that runs around the clock costs from about $79 a month for 720 CU-hours and 10 GB on Launch to about $1,682 a month for 6,000 CU-hours and 1,000 GB on Scale, before branches, history, egress and support (Neon pricing, checked 15 Nov 2026). The figures below are our arithmetic on Neon's published rates and its own load profiles.

Neon load profileCompute and storageLaunch a monthScale a month
Intermittent140 CU-hours, 1 GB$15.19$31.43
Medium, constant load720 CU-hours, 10 GB$79.82$163.34
High3,000 CU-hours, 100 GB$353.00$701.00
XL6,000 CU-hours, 1,000 GB$986.00$1,682.00
One 4 CU compute, always on2,920 CU-hours, storage extra$309.52$648.24

Sources: the CU-hour and storage rates, and the load profiles, are from Neon pricing, checked 15 Nov 2026 (page dated 4 Nov 2026). Monthly figures are compute at $0.106 (Launch) or $0.222 (Scale) per CU-hour plus storage at $0.35 per GB-month, multiplied by us. Neon says its estimates cover Postgres compute and storage only.

What the list price leaves out. The same page lists charges that sit beside compute and storage: additional branches at $0.002 per branch-hour beyond the 10 included on Launch (25 on Scale); instant restore history at $0.20 per GB-month, based on the volume of data changes in the history window, which is up to 7 days on Launch and up to 30 days on Scale; snapshots at $0.09 per GB-month; and public network transfer above 500 GB per project at $0.10 per GB (Neon pricing, checked 15 Nov 2026). SLAs, HIPAA and private networking are listed on Scale only.

What changes the comparison. Autoscaling bills the CU-hours actually used, so a database that idles overnight costs less than the always-on rows. A database that does not idle pays the same rate every hour. Take your own CU-hours, storage and branch count, price them on both sides, and ask for the OSStend side as a design price. OSStend is quoted per design, with the drivers on pricing: Talk to an engineer.

Fair notes on other options

Teams leaving Neon also compare a Postgres-based backend platform, a hyperscaler database and other managed platforms.

Supabase.
A backend platform built on Postgres. See Supabase alternatives.
Crunchy Bridge.
A self-serve cloud Postgres. See EDB vs Crunchy Data.
Amazon RDS.
AWS's managed relational database. See Amazon RDS alternatives.
Heroku Postgres.
See Heroku Postgres alternatives.
Aiven.
A multi-engine platform. See Aiven alternatives.

The documented ceilings of several turnkey services, Neon's included, are in the managed service limits index.

How to choose a Neon alternative

Choose by the shape of the workload and where the database has to run.

  1. If you run branch-per-PR or mostly idle databases, stay on Neon.
  2. If it is steady production on AWS and AWS-native is fine, compare Amazon RDS or Aurora.
  3. If it must run in your account, in Azure or in a data center, choose OSStend.
  4. If you want bundled auth and storage, compare Supabase.
How it works

Migration path from Neon

The new database is built to the signed-off design and loaded from Neon, with Neon kept available for rollback until the cutover is verified.

Illustrative: each phase is planned and rehearsed with your team before traffic moves.
  1. Review

    Database size, extensions, branches in use, connection pooling and the apps that connect.

  2. Design

    Size, topology, extensions, configuration, versions and where the database runs.

  3. Move

    Neon documents publishing data out once logical replication is enabled on the project, a setting its guide says cannot be reverted (Neon docs, checked 15 Nov 2026). PostgreSQL logical replication then keeps the new database current while Neon stays live. Where that is not possible, a dump and restore runs in a planned window.

  4. Cut over

    Connection strings switch once the new database is verified. Neon stays available for rollback.

FAQ

Questions about moving from Neon

Talk to an engineer →

What happened to Neon after the Databricks deal?

Databricks announced its intent to acquire Neon on 14 May 2025 (Databricks). Neon's pricing page now names the product Lakebase Postgres. Plans and prices are on Neon's pricing page, checked 15 Nov 2026.

How much does Neon cost for a production database?

At list prices, 3,000 CU-hours and 100 GB is $353 a month on Launch or $701 on Scale, before branches, history and egress. Neon's own rates and load profiles are on its pricing page, checked 15 Nov 2026. The production-scale table shows five profiles.

Can I run PostgreSQL in Azure instead of Neon?

Neon no longer allows new projects in Azure regions, per its regions page. OSStend runs PostgreSQL fully managed in your Azure account, in its own cloud, or co-managed in a data center.

Does a dedicated database cost more than serverless?

It depends on the load shape. Idle and spiky databases favour scale to zero. A steady 24/7 load is billed the same every hour either way. Compare the CU-hours used against a design price.

Will my extensions work?

OSStend runs community PostgreSQL with the extensions the design lists. Neon-specific features, such as branching and the serverless driver, need checking before the move.

Who runs the database after the move?

Named AceMQ engineers, 24/7. Response terms are on the service levels page.

Talk to an engineer

Plan your move off Neon with an engineer

45 minutes: your Neon projects are reviewed and the PostgreSQL design is sketched.

  • A design sketch for your workload, not a plan menu
  • A zero-downtime cutover path for what you run today
  • A price for that design, after the review
See pricing →

Your request goes to the OSStend team. No newsletter sign-up.

Get a quoteTalk to an engineer
2Engines
3Where should it run?
4What do you need?

Your request goes to the OSStend team. No newsletter sign-up.