By Your manager just walked in. Budget is gone. Timeline is tight. But there is an Oracle Database already running in production, and someone needs to build a web application on top of it. Fast.
That is the exact problem Oracle APEX was built to solve. Oracle APEX (Application Express) is a low-code web application development platform built directly into the Oracle Database. It lets developers build secure, data-driven web applications without managing a separate application server, without writing thousands of lines of boilerplate code, and without paying for additional software licenses. If you already have Oracle Database, you already have APEX.
In this article, I answer every core question about the platform: why Oracle APEX is used, when it was released, who actually uses it today, where it runs, and how it compares to other top low-code platforms with database integration. By the end, you will know exactly whether APEX belongs in your stack.
What Is Oracle APEX and Why Is It Used?
What Does Oracle APEX Actually Do?
Oracle APEX is a low-code application development platform that lives inside your Oracle Database. Developers build web applications through a browser-based IDE that includes drag-and-drop page builders, declarative wizards, theme templates, and a built-in SQL workshop. No separate middle-tier application server required.
The architecture is intentionally simple. Three layers. A web browser, Oracle REST Data Services (ORDS) acting as the web listener, and the Oracle Database running APEX itself. Because APEX runs inside the database, it accesses data with zero network round trips between the application layer and the data layer. That architecture eliminates the latency you normally see when a Node.js or Java application reaches out across a connection pool to query Oracle.
APEX applications are metadata-driven. The platform stores your application definition (pages, regions, items, processes, dynamic actions) as rows in database tables. At runtime, the APEX engine reads that metadata and generates the HTML, CSS, and JavaScript on the fly. This is why upgrading APEX versions does not break your applications. You do not maintain framework code. Oracle does.
Why Do Developers Choose Oracle APEX Over Other Platforms?
Simple answer: speed and cost. According to a study cited by Oracle and independently validated by Pique Solutions, developers build enterprise applications 38 times faster with APEX compared to traditional full-stack development using JavaScript frameworks. One team at EffectiveSoft built a fully functional classified ads prototype in five weeks, including user management, ad listings, search and filtering, and image upload. Full-stack, that is a three to four month project minimum.
The other reason is cost. APEX ships at no extra charge with every Oracle Database edition, including the Always Free tier on Oracle Autonomous Database. You pay nothing to add it. No per-user fees. No per-application fees. No developer seat licensing. That pricing model does not exist anywhere else in the enterprise low-code market.
Developers also choose APEX because it respects their existing SQL and PL/SQL skills. You do not learn a proprietary scripting language. You write SQL to fetch data, PL/SQL to handle business logic, and APEX handles the rest declaratively. If you want to extend with JavaScript, HTML, or CSS, the platform gives you that freedom without fighting you.
What Makes It Different From Traditional Full-Stack Development?
Traditional full-stack development forces you to manage several layers of complexity that have nothing to do with your actual business problem. You maintain an ORM layer to map relational data to application objects. You manage a connection pool. You handle session state in a separate cache. You configure security at every layer individually.
Oracle’s own documentation on why APEX eliminates complexity makes a point worthrepeating: “Most middle-tier applications must define application data structures to hold, convert,interact and maintain data flow between the app to the database.” APEX removes that entire category of work.
Security is another standout area. APEX includes built-in protections against SQL injection and cross-site scripting (XSS) out of the box. The htf.escape_sc() function, session state protection, authorization schemes, and the APEX Advisor utility all help you ship secure applications without hiring a dedicated application security engineer.
I previously built a one-click task completion system directly inside an Oracle APEX Classic Report using dynamic actions, a jQuery selector, and a clean UPSERT pattern in PL/SQL. No custom REST endpoint. No separate frontend build pipeline. Thirty minutes of work. That is what “eliminating complexity” actually looks like in practice.
When Was Oracle APEX Released? A Brief History
From “Project Marvel” to HTML DB (2000 to 2004)
Oracle APEX did not start as a product. It started as an internal calendar.
In the year 2000, Oracle developer Michael Hichwa and his colleague Joel Kallman were tasked with building an internal web calendar for Oracle. They built it using a framework they called Flows. The framework had no front-end at first. All application changes were made directly in SQL*Plus via INSERT, UPDATE, and DELETE commands. Not exactly a developer experience to brag about.
The project grew. Flows became Project Marvel. The team added a graphical user interface and took the tool to a Beta Customer to build real production applications. Those applications arereportedly still running today.
In 2004, Oracle officially released the tool as a supported product. It shipped as part of Oracle Database 10g under the name HTML DB, version 1.5. That is the true release date of what we now call Oracle APEX: 2004, with roots going back to 2000.
When Did Oracle APEX Get Its Name? (2006)
In 2006, Oracle renamed HTML DB to Oracle Application Express (APEX). Version 2.1 shipped with the new name and was bundled for free with the Oracle Express Edition (XE) database. That bundling decision accelerated adoption dramatically. Developers who had never looked at HTML DB suddenly had a free, full-featured web development tool sitting inside their free Oracle database.
That same year, the APEX community started growing fast. Developers who were already comfortable with PL/SQL found that they could build polished web applications without learning Java, PHP, or .NET. The tool had found its audience.
How Has APEX Evolved Since Then?
The evolution has been steady and purposeful.
● APEX 4.0 (2010): Introduced a proper plugin architecture, dramatically improved layout capabilities, and added Team Development for multi-developer collaboration on a single application.
● APEX 4.2: Brought full HTML5 support, jQuery Mobile integration for mobile layouts, and packaged application support.
● APEX 5.0: Overhauled the entire developer experience with a redesigned IDE and Universal Theme.
● APEX 18.1 Onward: Oracle changed version numbering to align with year and quarter of release.
● APEX 24.x: Integrated generative AI tools,including natural language app generation and AI-assisted development features.
Today, APEX ships two major releases per year. Each release receives 18 months of support under Oracle’s standard database maintenance agreement. The platform has powered millions of applications across thousands of organizations over 20+ years.
Who Uses Oracle APEX?
Which Industries Rely on Oracle APEX?
Oracle APEX is used heavily in industries where data security and auditability are non-negotiable. Verified usage data from Landbase shows 2,725 confirmed companies using APEX as of 2025, spanning manufacturing, business services, custom software and IT services, finance, and government.
That list is telling. These are not industries chasing the latest trend. They are organizations running mission-critical data and needing a platform that will not break their compliance posture.
Finance teams use APEX for regulatory reporting, risk dashboards, and internal audit tools. Government agencies use it to consolidate rogue spreadsheets and legacy Oracle Forms applications into proper, auditable web systems. Healthcare organizations use it for patient
management, clinical trial tracking, and medical device integrations where HIPAA-compliance requirements rule out many SaaS alternatives. Manufacturing teams use it for shop floor controls, quality assurance dashboards, and supply chain visibility tools that pull data directlyfrom ERP systems.
Real-World Companies and Government Use Cases
The use cases are not theoretical.
Munich Re HealthTech used Oracle APEX to cut manual effort, meet strict data-residency requirements, and launch AI chatbots that now handle 90% of user questions. Siemens Mobility, Vodafone Group, Nomura Research Institute (NRI), and Syneos Health all run APEX applications in production today.
In government, the example that stands out is the UK’s COVID-19 testing system. That system processed millions of records through an Oracle APEX application. Not a proof of concept. A live, high-volume, national-scale system built in APEX because the team needed something that could ship quickly on proven Oracle infrastructure.
The US federal government is actively expanding its APEX footprint. Oracle’s government blog notes that federal agencies see APEX as a way to accelerate software development while keeping sensitive data inside their own Oracle Cloud regions.
How Many Companies Use Oracle APEX Today?
The 2,725 verified companies figure is conservative. It reflects only organizations where APEX usage is verifiable through public data. Oracle itself states “thousands of customers” and “millions of applications” on its platform homepage, backed by over 20 years of deployments.
Oracle APEX holds a 10.3% mindshare in the Low-Code Development Platforms category as ranked by PeerSpot users in 2025, placing it third behind Microsoft Power Apps and OutSystems. For a free tool bundled with a database, that ranking is significant.
If you want to build your career around Oracle and APEX, I have written a detailed guide on how to start your Oracle developer career in 2026. The demand is real. The career path is clear.
Where Is Oracle APEX Used and Where Is It Installed?
Oracle Cloud Infrastructure (OCI) – Fully Managed
The fastest way to get APEX running is Oracle Cloud Infrastructure. On Autonomous Database, APEX comes pre-installed and pre-configured. You create an account, provision an Autonomous Database instance, and APEX is already there. Oracle manages the upgrades, the ORDS layer, the database patching, and the infrastructure.
The Always Free tier of OCI includes an Autonomous Database instance with APEX enabled. For anyone evaluating the platform, this is the right starting point. I wrote a complete walkthrough on how to set up Oracle APEX on Oracle Cloud Free Tier if you want to follow along step by step.
OCI also offers the APEX Application Development Service, a standalone PaaS offering specifically for APEX workloads. You pay for compute and storage consumed by your APEX applications. No per-user licensing. No per-application fees.
On-Premises Oracle Database
For organizations that cannot or will not move to the cloud, APEX installs directly onto any on-premises Oracle Database instance. The installation requires running a SQL script (apexins.sql) against your database as SYSDBA. Then you install Oracle REST Data Services (ORDS) on a separate server (or the same server for smaller environments), configure it to point at your database, and expose it through a web listener.
ORDS supports deployment on Apache Tomcat, Oracle WebLogic Server, or in standalon mode for smaller workloads. ORDS is a Java application, so it requires Java 11 or higher on the host server. The APEX images folder (static resources like JavaScript, CSS, and images) gets served from this ORDS server.
On-premises is the right choice for organizations with strict data-residency rules, air-gapped environments, or compliance requirements that prohibit cloud deployment. The application you build runs identically on-premises or in the cloud. APEX does not distinguish.
Third-Party Clouds (AWS RDS, Azure, GCP)
APEX runs on any cloud platform that supports Oracle Database. Oracle’s deployment documentation confirms support for Linux, Unix, and Windows platforms regardless of where Oracle Database runs.
On Amazon RDS for Oracle, you add APEX as an option group to your DB instance. ORDS still needs to run on a separate host (an EC2 instance works well). AWS manages the database infrastructure while you manage the ORDS layer on your compute instance.
On Azure and GCP, you can run Oracle Database on a virtual machine and install APEX and ORDS directly. The GCP partnership with Oracle Cloud Infrastructure also allows multi-cloud architectures where Oracle Database runs in OCI and workloads span both clouds.
For teams connecting APEX to external systems, I covered the complete process of calling external HTTPS APIs from Oracle APEX using Oracle Wallet. REST integration from within APEX is straightforward once your wallet and network ACLs are configured.
Best Platforms for Building Low-Code Web Applications
With Database Integration
Choosing the right low-code platform depends heavily on your existing data infrastructure. Here is an honest comparison of the top options.
Oracle APEX – Best for Oracle Database Shops
Ideal for: Organizations already running Oracle Database who want to build data-centric web applications fast.
Strengths:
● Zero additional licensing cost for existing Oracle Database customers
● Native SQL and PL/SQL integration with no ORM layer
● Unlimited applications, developers, and end users on a single instance
● Built-in security (SQL injection prevention, XSS protection, session state protection)
● Runs on-premises, OCI, AWS RDS, Azure, or GCP
Limitations: APEX is tied to Oracle Database. It does not connect natively to PostgreSQL, MySQL, or SQL Server as primary data sources. If your data lives outside Oracle, you face extra integration work.
Oracle APEX holds a 4.5-star average rating with approximately 90% user satisfaction across review platforms.
Microsoft Power Apps – Best for Microsoft Ecosystems
Ideal for: Organizations running Microsoft 365, SharePoint, Azure, and Teams who need to build departmental apps quickly.
Strengths: 1,100+ pre-built connectors, tight integration with Microsoft productivity tools, Copilot AI assistance, strong citizen developer experience.
Limitations: Costs scale fast per user. Complex applications require deep familiarity with the Power Platform suite. Performance can degrade on large datasets without careful Dataverse tuning.
Power Apps holds the largest mindshare in the low-code category at 18.3%, driven primarily by
its integration with Microsoft’s existing enterprise installed base.
OutSystems – Best for Complex Enterprise Apps
Ideal for: Large enterprises building core business systems, customer portals, and legacy modernization projects where full-stack control matters.
Strengths: Strongest DevOps tooling in the low-code space, performance monitoring, visual development with professional-grade deployment pipelines.
Limitations: Pricing starts at $1,513 per month. The learning curve is steeper than other platforms. Citizen developers cannot easily self-serve on OutSystems without IT involvement.
OutSystems received the highest peer rating of 8.9 among low-code platforms in the PeerSpot 2025 rankings. It earns that rating. But it costs accordingly.
Mendix – Best for Agile Collaboration Between IT and Business
Ideal for: Teams where business analysts and IT developers need to collaborate closely inside a shared visual modeling environment.
Strengths: Strong collaboration tools, reusable components, pre-built connectors for SAP, Oracle, and Salesforce through standard REST/SOAP/OData protocols, flexible cloud deployment.
Limitations: Out-of-the-box features become significantly harder to implement when your requirements deviate from the standard templates. Enterprise features require higher-tier licensing.
Mendix is a recognized Gartner Magic Quadrant leader for enterprise low-code platforms. It fits organizations that need to bridge the gap between non-technical business users and IT development teams.
Which One Should You Choose?
Here is the decision framework I use:
● You run Oracle Database → Oracle APEX. No contest. Free, fast, and built for your data.
● You run Microsoft 365 and need internal tools → Power Apps. Leverage what you already pay for.
● You need complex customer-facing apps with enterprise DevOps → OutSystems. Worth the cost at scale.
● You need IT and business to co-develop in a shared visual environment → Mendix. Built for that workflow.
The mistake most teams make is choosing a platform based on marketing rather than their actual data infrastructure. The best low-code platform is always the one that sits closest to where your data already lives.
Is Oracle APEX the Right Fit for You?
Is Oracle APEX Free?
Oracle APEX is included at no cost with every Oracle Database edition, including Oracle Database Express Edition (XE) and Oracle Autonomous Database. You do not pay per user, per developer, or per application. On Oracle Cloud Infrastructure, APEX is available on the Always Free tier at no charge. If you use APEX Application Development as a standalone cloud service, you pay for compute and storage only, starting at approximately $122 per month.
Do I Need to Know PL/SQL to Use Oracle APEX?
You do not need PL/SQL to get started. The declarative components (forms, reports, charts, dynamic actions) require only basic SQL for data queries. However, PL/SQL becomes necessary as soon as you start writing custom business logic, handling complex validations, or automating background processes. Developers with solid SQL and PL/SQL skills build production-ready APEX applications significantly faster than those approaching from a pure front-end background. If you want to strengthen your Oracle fundamentals, I have found Oracle Dev Gym to be one of the best free resources available, with 2,400+ quizzes covering SQL, PL/SQL, and APEX.
Can Oracle APEX Scale for Enterprise Use?
Yes. Oracle APEX inherits the full scalability of Oracle Database. The platform supports thousands of concurrent users on a single APEX instance. ORDS manages the connection pooling, and Oracle Database resource management lets DBAs assign consumer groups to specific workspaces or applications. Companies like Munich Re HealthTech and Nomura Research Institute run APEX at enterprise scale in regulated, high-availability environments. If you are hitting scaling challenges with your current APEX setup, it is usually an ORDS configuration issue or a SQL query efficiency problem, not a platform ceiling. I wrote about why some Oracle developers are stuck in 2026 and how to break out if you want a broader perspective on the skills and approaches that matter most.
Oracle APEX started as an internal Oracle calendar in 2000. It became HTML DB in 2004. It became Oracle Application Express in 2006. And it has spent the last two decades quietly powering some of the most data-intensive applications in finance, government, healthcare, and
manufacturing, without most of the industry paying attention.
That is actually an advantage for the developers and architects who do know it.
You get a platform that handles application security, session management, responsive UI, REST integration, and database connectivity in a single coherent environment. You get it for free on Oracle Database. You deploy it anywhere Oracle runs. And you build on top of 25 years of production hardening that no startup low-code platform can replicate.
If you are running Oracle Database and you are not using APEX, you are leaving a fast, proven, and completely free development platform sitting unused in your stack.
Have you built something with Oracle APEX? Drop your experience in the comments. I read every one.
Hassan Raza
An Oracle ACE Associate and Senior Oracle Application Developer at S&H Software Solution. I am specialized in Oracle APEX, SQL, and PL/SQL and writes about Oracle development at oraclewithhassan.com.
