Sage has publicly identified PostgreSQL as its strategic database platform for Sage X3 SaaS, stating that the decision supports a more competitive offering through reduced infrastructure costs. However, Sage's decision to restrict PostgreSQL support to its own SaaS offering appears inconsistent with the broader objective of improving Sage X3's commercial competitiveness. On premises customers and independent hosting partners remain dependent on Microsoft SQL Server or Oracle Database, both of which introduce substantial database licensing costs.
If PostgreSQL delivers sufficient commercial and technical benefits for Sage to adopt it as its strategic SaaS database, those same benefits should be available to customers and partners operating Sage X3 under alternative deployment models.
Furthermore, Sage X3 already supports Linux based application deployments, including Red Hat Enterprise Linux and Oracle Linux. Combined with Sage's investment in PostgreSQL for SaaS, the technological foundations exist to investigate a supported Linux and PostgreSQL deployment option.
I propose that Sage extend PostgreSQL certification and support to on premises and partner hosted Sage X3 environments, providing greater database flexibility, reduced licensing expenditure and improved total cost of ownership.
Sage has acknowledged that PostgreSQL offers commercial advantages through reduced infrastructure costs, supporting a more competitive SaaS offering. However, limiting these benefits to Sage managed SaaS environments creates a potential commercial disadvantage for customers and independent hosting partners. Customers choosing on premises or privately hosted Sage X3 should not be required to incur additional commercial database licensing costs simply because PostgreSQL is unavailable as a certified platform.
Commercial competitiveness should be an objective across the entire Sage X3 ecosystem, not a benefit restricted to a single deployment model.
Extending PostgreSQL support would strengthen Sage X3's competitiveness against alternative ERP platforms while providing customers with greater flexibility over their infrastructure investments.
Microsoft SQL Server and Oracle Database licensing represent significant ongoing expenditure for many Sage X3 customers.
These costs become particularly relevant for hosting partners managing multiple customer environments, including production, development, testing and disaster recovery systems.
PostgreSQL is an established, enterprise capable relational database platform that does not require the equivalent commercial database licensing expenditure.
Supporting PostgreSQL would allow customers and hosting partners to potentially reduce infrastructure costs and redirect those savings towards application development, integrations, security and other business improvements.
While PostgreSQL still requires appropriate administration, maintenance and support, eliminating commercial database licensing would provide a meaningful opportunity to reduce total cost of ownership.
Sage X3 already supports Linux based application and runtime deployments, including Red Hat Enterprise Linux and Oracle Linux. However, the current certified Linux application architecture depends on Oracle Database.
This limits the potential licensing and infrastructure savings achievable through Linux based deployments. Introducing PostgreSQL as an additional certified database would provide a logical extension of Sage's existing technology capabilities.
A supported Linux and PostgreSQL architecture would offer several advantages:
Reduced licensing expenditure: Remove the requirement for commercial Oracle database licensing in supported Linux deployments.
Infrastructure flexibility: Enable customers to deploy Sage X3 using Linux and PostgreSQL within their existing infrastructure or private cloud environments.
Reduced vendor dependency: Provide an alternative to commercial database platforms without requiring customers to change their ERP application.
Greater hosting flexibility: Allow independent hosting partners to develop competitive infrastructure offerings using established Linux and PostgreSQL technologies.
Strategic consistency: Align Sage's existing Linux application support with its investment in PostgreSQL for SaaS.
Importantly, Sage already has experience supporting Linux based Sage X3 infrastructure and is investing in PostgreSQL for its SaaS architecture. While combining these technologies would require additional engineering, integration testing and certification, Sage would not be starting from an entirely unfamiliar technology platform.
The logical next step is to evaluate bringing these two existing capabilities together into a certified Linux and PostgreSQL deployment option for Sage X3.
This would not necessarily eliminate every Windows component from the architecture, but it would offer a significant alternative to existing commercial database deployments.
Independent Sage partners play an important role in implementing, hosting, supporting and maintaining Sage X3 environments.
By adopting PostgreSQL exclusively within its own SaaS offering, Sage potentially creates an infrastructure cost advantage that independent hosting partners cannot reproduce using a certified Sage X3 database platform.
This creates an uneven commercial environment where infrastructure costs may differ significantly depending on the customer's chosen hosting model.
Independent hosting partners should be able to compete based on service quality, technical capability, reliability and customer requirements rather than being constrained by database licensing restrictions.
Extending PostgreSQL support would allow Sage partners to compete on more equal technical and commercial terms while strengthening the broader Sage X3 ecosystem.
Not every organisation can or wishes to adopt a vendor managed SaaS deployment. Some customers require on premises or privately hosted infrastructure because of operational requirements, integration complexity, data governance, regulatory obligations or existing technology investments. These customers should not be excluded from the commercial advantages of PostgreSQL.
Supporting PostgreSQL alongside Microsoft SQL Server and Oracle Database would provide greater flexibility in database selection, infrastructure design and long term technology planning. It would also reduce dependency on individual database vendors and provide customers with more control over their operating costs.
I recommend that Sage introduce PostgreSQL support through a phased certification programme.
Introduce PostgreSQL as a supported database for new Sage X3 V12 on premises and partner hosted environments.
Prioritise certification of the Sage X3 application, runtime, database connector and associated administration components.
Include support for Linux based deployments, particularly Red Hat Enterprise Linux and Oracle Linux, alongside supported Windows configurations where technically appropriate.
Extend certification and compatibility testing to:
Sage X3 batch processing and application services.
Sage X3 Console and administration tools.
Reporting services, including Crystal Reports database connectivity.
Third party applications and ISV solutions.
Existing integration frameworks and database dependent customisations.
Backup, recovery and high availability configurations.
Provide clear guidance identifying any database specific functionality requiring modification.
Develop documented and supported migration procedures allowing customers to transition existing Microsoft SQL Server and Oracle Database environments to PostgreSQL.
This should include database schema conversion, data migration, compatibility validation and rollback procedures.
Prioritising new deployments would allow Sage to establish certification and operational experience before supporting more complex existing customer migrations.
Publish technical guidance covering:
Recommended infrastructure sizing.
Database configuration and performance optimisation.
Comparative performance benchmarks using representative Sage X3 workloads.
Backup, recovery and high availability recommendations.
Monitoring, maintenance and operational support requirements.
Include PostgreSQL within the standard Sage X3 compatibility matrix, maintenance releases and support lifecycle.
Sage has previously stated that PostgreSQL is replacing SQL Server as the strategic database for X3 SaaS, supporting a more competitive offering and a lower cost infrastructure strategy. In the same statement, Sage indicated that PostgreSQL was not a customer driven feature and would not be extended to on premises or self hosted environments.
I believe this position warrants reconsideration.
Reducing infrastructure licensing costs is inherently a customer benefit, regardless of whether Sage, an independent hosting partner or the customer operates the infrastructure. While PostgreSQL may have originated as an internal technology decision to improve the economics of Sage's SaaS offering, its potential financial benefits are equally relevant to customers operating alternative deployment models.
Furthermore, Sage already supports Linux based Sage X3 application infrastructure.
With PostgreSQL becoming part of Sage's SaaS strategy, there is an opportunity to leverage these existing investments across the wider Sage X3 product ecosystem. I acknowledge that supporting PostgreSQL outside Sage managed SaaS would introduce additional engineering, certification and ongoing maintenance requirements.
However, these costs should be evaluated against the potential commercial benefits, including broader market competitiveness, reduced customer infrastructure expenditure and greater flexibility for Sage's independent partner network.
The question is not simply whether PostgreSQL is technically feasible for Sage X3, but why the commercial advantages Sage has identified for its own SaaS offering should remain unavailable to customers and partners operating the same ERP platform under alternative deployment models.
Sage's decision to adopt PostgreSQL for SaaS demonstrates a strategic commitment to reducing database infrastructure costs and improving commercial competitiveness. Sage also has an established history of supporting Linux based application deployments.
Restricting PostgreSQL to Sage managed SaaS environments potentially undermines these same commercial objectives for the broader Sage X3 customer and partner ecosystem.
Extending PostgreSQL certification would deliver greater customer choice, reduce dependency on commercial database licensing and enable independent hosting partners to offer more competitive infrastructure solutions.
I encourage Sage to reconsider its current position and establish a roadmap for PostgreSQL certification across all Sage X3 deployment models, beginning with new implementations and progressing towards supported migration options for existing customers.
If PostgreSQL is strategically important to Sage X3's commercial competitiveness, its benefits should extend to the entire Sage X3 ecosystem, not exclusively to Sage managed SaaS customers.