Neon Pricing

Frequently Asked Questions

• What is a compute hour?

  Compute hour is the metric for compute usage in Neon. The quick math: [compute hours] = [compute size] x [hours your compute runs]. Each pricing plan includes a certain number of compute hours; how quickly you consume these hours depends on the size of your compute and how long it runs. Once you exceed the allocated amount of compute hours, you'll be billed for overages in a given month.

• How does billing work?

  In Neon, you are charged a monthly fee plus any additional compute and/or storage usage over what's included in your plan. For example, the Launch plan includes 300 compute-hours of compute usage; if you consume 320 compute-hours in a month, your will see extra 20 compute-hours in your monthly bill.

• When will I be billed?

  Neon bills for the past month's usage at the beginning of each calendar month. For more information, see Manage billing.

• How many compute hours will it take to run my workload?

  You can get a good idea by estimating how many hours your databases run, and at which compute size. For example: imagine you’re running a 2 CPU, 8 GB RAM database for 2 hours a day (or 62 hours per month). This equals [2 CU * 62 hours] = 124 compute hours per month.

• How can I control my costs with autoscaling?

  When enabling autoscaling, you will set a maximum autoscaling limit (e.g. 2 CU) that will act as a de-facto cost limit.

• How is storage charged in Neon?

  Neon implements a unique storage engine that enables database branching on copy-on-write, without duplicate storage. You can create instant database copies (database branches) without adding to the storage bill. Read more in our docs.

• What do I get for the "regular" cost per-GB in Neon?

  Neon's storage model is unique: our "per-GB" metric truly stretches. You can create hundreds of database copies (via branching) or replicas without increasing storage costs. High availability is also included in this price. For maximum storage scalability, consider the Business plan—our most cost-efficient option.

• What is "archive storage"?

  To save you costs, branches that are idle for at least a day and that are older than 2 weeks are considered archived storage, and billed at a reduced rate. This has no implications for you, it happens automatically. More context here.

• Do I get a notification if I am approaching my usage limits?

  Yes, we display your usage consumption in the Neon admin console, and we will also email you when you’re getting close.

• Can I use Neon for database-per-user architectures?

  Yes, Neon is a great option for designs demanding one database per user. Our recommendation is to follow a project-per-user (or project-per-tenant) pattern, taking advantage of the thousands of projects included in our pricing plans. Read more.

• Is Neon compliant?

  Yes, Neon adheres to SOC 2, ISO 27001, ISO 27701 standards and complies with GDPR and CCPA regulations. HIPAA compliance will come very soon.

• Which level of uptime can I expect with Neon?

  Neon offers a 99.95% uptime SLA for Business and Enterprise customers, ensuring consistent availability and performance for mission-critical applications.

• Can Neon help with migrations?

  Absolutely. Our expert team assists Business and Enterprise clients throughout the migration process, waiving any migration-related fees to ensure a smooth transition. Tell us here if you're considering migrating to Neon.