Cloud Engineer at a financial services firm with 10,001+ employees
Real User
Top 10
Nov 20, 2025
My experience with pricing, setup costs, and licensing for Azure Database for PostgreSQL is positive; I appreciate it all. The pricing is very cost-effective and stable given that we have many database products.
Lead Software Engineer at a retailer with 5,001-10,000 employees
Real User
Top 10
Nov 19, 2025
Azure Database for PostgreSQL has affected my database-related costs and resource allocation. There's probably room for improvement on the Postgres side, certainly on the Azure SQL side. We have a lot of large relational databases that I'm sure are fairly consistent in their needs. Moving to reserved instances probably would be helpful and we're probably in a spot where we'd investigate that more now than ever with tariffs and everything that's going on. We're a fairly profitable company, so we've been focusing on moving faster and faster. As time goes along, it's going to be more and more useful. As our usage of Postgres increases, which I'm thinking it will, it will make an impact. Right now the devil we know is pay-as-you-go, so we've stuck with it and it's fine for our needs.
Staff Data Engineer at a transportation company with 10,001+ employees
Real User
Top 10
Nov 19, 2025
The pay-as-you-go pricing model of Azure Database for PostgreSQL has affected our database-related cost and resource allocation. We started with the pay-as-you-go model because we wanted to give it a try, grow slower and then steady, in a phased approach. We eventually decided that we know what our reserved capacity looks like. So we changed our strategy last year to go buy the reserved capacity, but we started with the pay-as-you-go. This is a really nice entry point for any customer who wants to come and try it. Pay-as-you-go is a really good pricing choice. Once you are comfortable and ready to make some commitments, you get about 30 percent saving if you are going with one-year or three-year reservation cost. We pretty much started with pay-as-you-go, but now we have moved into a reserved cost.
Transformation Edge Ai Delivery Lead Director, Infrastructure at a tech vendor with 10,001+ employees
Real User
Top 10
Nov 19, 2025
The pay-as-you-go pricing model of Azure Database for PostgreSQL has actually increased costs. The licensing model that I had before in some use cases was very beneficial and included volume discounts. Once you move to that model, if you do not have it tightly integrated with FinOps, you will pay more. In comparison to my previous expenses for maintaining an on-premises PostgreSQL database, the costs are higher.
Cloud Solutions Architect at Measurement Incorporated
Real User
Top 10
Nov 18, 2025
Our experience with pricing, setup cost, and licensing of Azure Database for PostgreSQL is that the decision came as a requirement from the development team. We chose it because it is more cost-effective than Microsoft SQL.
Learn what your peers think about Azure Database for PostgreSQL. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
Director, Alliances & Engineering at a computer software company with 1,001-5,000 employees
MSP
Top 10
Nov 21, 2024
The pay-as-you-go pricing model has significantly lowered our database-related costs. We've reduced costs by 60 percent compared to maintaining on-premises solutions.
Admin (hands on user) at a comms service provider with 11-50 employees
Real User
Top 10
Nov 21, 2024
I like PostgreSQL's pay-as-you-go pricing because I only pay for what I use. However, it depends on the use case. If the application is in high demand, I'd rather go for a fixed license. I'm using it sparsely, I prefer pay-as-you-go.
The pricing experience is positive. Azure Database for PostgreSQL reduces the need for hardware investments, and the pay-as-you-go pricing model positively affects database-related costs by allowing us to start small and scale as needed.
Azure Database for PostgreSQL offers efficient management, robust networking, and seamless Microsoft integration. Known for its strong performance and high satisfaction in enterprise settings, it provides operational efficiency, security, and monitoring.With features that facilitate Azure integration, easy configuration, and AI integration, Azure Database for PostgreSQL serves as a valuable choice for businesses requiring operational efficiency and cost-effectiveness. Users benefit from...
My experience with pricing, setup costs, and licensing for Azure Database for PostgreSQL is positive; I appreciate it all. The pricing is very cost-effective and stable given that we have many database products.
Azure Database for PostgreSQL has affected my database-related costs and resource allocation. There's probably room for improvement on the Postgres side, certainly on the Azure SQL side. We have a lot of large relational databases that I'm sure are fairly consistent in their needs. Moving to reserved instances probably would be helpful and we're probably in a spot where we'd investigate that more now than ever with tariffs and everything that's going on. We're a fairly profitable company, so we've been focusing on moving faster and faster. As time goes along, it's going to be more and more useful. As our usage of Postgres increases, which I'm thinking it will, it will make an impact. Right now the devil we know is pay-as-you-go, so we've stuck with it and it's fine for our needs.
The pay-as-you-go pricing model of Azure Database for PostgreSQL has affected our database-related cost and resource allocation. We started with the pay-as-you-go model because we wanted to give it a try, grow slower and then steady, in a phased approach. We eventually decided that we know what our reserved capacity looks like. So we changed our strategy last year to go buy the reserved capacity, but we started with the pay-as-you-go. This is a really nice entry point for any customer who wants to come and try it. Pay-as-you-go is a really good pricing choice. Once you are comfortable and ready to make some commitments, you get about 30 percent saving if you are going with one-year or three-year reservation cost. We pretty much started with pay-as-you-go, but now we have moved into a reserved cost.
The pay-as-you-go pricing model of Azure Database for PostgreSQL has actually increased costs. The licensing model that I had before in some use cases was very beneficial and included volume discounts. Once you move to that model, if you do not have it tightly integrated with FinOps, you will pay more. In comparison to my previous expenses for maintaining an on-premises PostgreSQL database, the costs are higher.
Our experience with pricing, setup cost, and licensing of Azure Database for PostgreSQL is that the decision came as a requirement from the development team. We chose it because it is more cost-effective than Microsoft SQL.
advise to get E5 for better security and governance of your data and systems
Pricing is affordable for us. PostgreSQL is good and affordable for our needs.
The pay-as-you-go pricing model has significantly lowered our database-related costs. We've reduced costs by 60 percent compared to maintaining on-premises solutions.
I like PostgreSQL's pay-as-you-go pricing because I only pay for what I use. However, it depends on the use case. If the application is in high demand, I'd rather go for a fixed license. I'm using it sparsely, I prefer pay-as-you-go.
I'm not familiar with the licensing aspect, as I do not handle it. However, pricing, licensing, and setup costs are not major issues.
We do not pay for a full-year subscription because our usage is still at the beginning phase and not much. The pay-as-you-go model works well for us.
The pricing experience is positive. Azure Database for PostgreSQL reduces the need for hardware investments, and the pay-as-you-go pricing model positively affects database-related costs by allowing us to start small and scale as needed.