Progress OpenEdge

active

by Progress Software · since 1984 · also known as OpenEdge, Progress 4GL, OpenEdge RDBMS, Progress ABL

Integrated RDBMS plus ABL 4GL application platform behind thousands of ERP and vertical business apps.

relationaldatabase engineproprietarylegacy

Overview

OpenEdge is Progress Software's application platform: a transactional relational database tightly coupled to ABL (formerly Progress 4GL), a business language where queries, locking and transactions are part of the syntax. That pairing is why so many mid-market ERP, distribution and vertical ISV products were built on it, and why they still run on it decades later. The database offers replication, table partitioning, transparent data encryption, CDC and a SQL-92 engine for ODBC/JDBC reporting, while PASOE serves ABL logic over REST. 12.8 is the long-term-support line; 13.0 (February 2026) is a shorter-lived innovation release with ABL generics, a built-in AI coding assistant and FIPS 140-3 work.

Strengths & trade-offs

Strengths

  • +ABL makes transactions, record locking and queries first-class language constructs
  • +Very stable, long-lived databases that run with modest DBA effort
  • +Built-in replication, partitioning, TDE and CDC options
  • +Large catalogue of ERP and vertical ISV applications already built on it

Trade-offs

  • −ABL skills are scarce and the talent pool is ageing
  • −SQL engine is secondary; complex reporting via ODBC can be slow
  • −Proprietary stack ties applications to Progress licensing
  • −No horizontal scaling

Great for

  • +Running ERP, distribution and manufacturing packages built on OpenEdge
  • +Modernising ABL apps behind REST APIs with PASOE
  • +ISV vertical applications sold to SMBs

Think twice for

  • −New applications outside the ABL ecosystem
  • −Analytics and data warehousing
  • −Teams that need a large hiring pool

Capabilities

Native or official first-party support · 11 of 25 tracked

✓Transactions
✓Joins
✓Secondary indexes
✓Full-text search
✓Change data capture
✓Triggers
✓Stored procedures
✓Durable persistence
✓Encryption at rest
✓Role-based access
✓Online schema changes
–Vector search
–Geospatial
–JSON
–Materialized views
–TTL / expiry
–Pub/Sub
–Columnar storage
–In-memory
–Compression
–Time travel
–Branching
–Streaming ingest
–Offline sync
–Runs in WebAssembly

Scale & consistency

Comfortable data size
Medium · ≤ 10 TB
Horizontal scaling
None
Multi-region
Read replicas
Transactions
Full ACID
Consistency
Strong
Schema
Strict
Architecture
Client server, Primary replica
Query languages
ABL (Advanced Business Language), SQL-92

Vertical scale with table partitioning; OpenEdge Replication for hot standby and DR.

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

Ecosystem

apis & protocolsABL client/server protocol, ODBC, JDBC, PASOE REST/SOAP
client languagesABL, Java, C#, C

Alternatives to Progress OpenEdge

Compare all→
Microsoft SQL ServerRelational71.0

Microsoft's flagship RDBMS: T-SQL, columnstore, Always On, and now native vectors and JSON.

progress-openedge vs sql-server →
Oracle DatabaseRelational56.9

The enterprise heavyweight: RAC, Data Guard and a converged engine for SQL, JSON, graph and vectors.

progress-openedge vs oracle-database →
PostgreSQLRelational93.2

The extensible, standards-first open-source relational database.

progress-openedge vs postgresql →
InterSystems IRISRelational13.3

Multi-model data platform (SQL, objects, globals, vectors) with built-in interoperability, big in healthcare.

progress-openedge vs intersystems-iris →
4DRelational12.8

French integrated database and app-development platform for desktop, client/server and web apps.

progress-openedge vs 4d →
Actian ZenRelational11.7

The Btrieve/Pervasive lineage: zero-admin embedded database with key-level and SQL access, now edge-focused.

progress-openedge vs actian-zen →

Progress OpenEdge FAQ

What is Progress OpenEdge?

Progress OpenEdge is a relational database by Progress Software, first released in 1984. OpenEdge is Progress Software's application platform: a transactional relational database tightly coupled to ABL (formerly Progress 4GL), a business language where queries, locking and transactions are part of the syntax. That pairing is why so many mid-market ERP, distribution and vertical ISV products were built on it, and why they still run on it decades later. The database offers replication, table partitioning, transparent data encryption, CDC and a SQL-92 engine for ODBC/JDBC reporting, while PASOE serves ABL logic over REST. 12.8 is the long-term-support line; 13.0 (February 2026) is a shorter-lived innovation release with ABL generics, a built-in AI coding assistant and FIPS 140-3 work.

Is Progress OpenEdge open source?

No. Progress OpenEdge is proprietary, closed-source software.

Does Progress OpenEdge support ACID transactions?

Yes. Progress OpenEdge supports full ACID transactions, with strong consistency.

Does Progress OpenEdge scale horizontally?

Progress OpenEdge does not scale horizontally; it runs on a single node, so you scale it up rather than out. It is comfortable at medium scale (≤ 10 TB). It supports cross-region read replicas.

How can I run Progress OpenEdge?

You can self-host it.

What is Progress OpenEdge best for?

Progress OpenEdge is a strong fit for running ERP, distribution and manufacturing packages built on OpenEdge; modernising ABL apps behind REST APIs with PASOE; and ISV vertical applications sold to SMBs. Think twice for new applications outside the ABL ecosystem.

What are the best alternatives to Progress OpenEdge?

Common alternatives to Progress OpenEdge include Microsoft SQL Server, Oracle Database, PostgreSQL, InterSystems IRIS and 4D. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

How popular is Progress OpenEdge?

Progress OpenEdge ranks #157 of 844 databases on the WhichDB Score (20.4/100), and #51 among relational databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.