Most cost comparisons between Oracle APEX and custom development stop at the first build. That is the smallest part of the bill. The larger part is running, securing and changing the app for years.
This guide gives you a framework to compare the two honestly. It covers how APEX is licensed, how Oracle prices APEX on OCI, what drives cost on each side and how to build your own estimate. We do not quote benchmark savings, because they depend on your scope. If you are choosing a partner, see our Oracle APEX development company buyer's guide.
What APEX costs to license
Oracle states that APEX is a no-cost feature of Oracle Database, including Autonomous Database and its other database editions. In practice this means:
- On-premises or co-managed databases. If you already license Oracle Database, there is no separate APEX licence. You pay for the database, the servers and the people who run them.
- Oracle Cloud. You pay for the database service your apps run on. The APEX service documentation describes the deployment options.
- Always Free. Oracle lists APEX Application Development among its Always Free services, with fixed limits (see below).
None of these options removes the cost of design, build, testing and support. That is where most of your budget will go.
How Oracle prices the APEX service on OCI
Oracle's pricing page lists the APEX Application Development service as a consumption service. Compute is billed in ECPUs per hour, and storage is billed separately. Oracle's product page says there are no per-user fees.
An Oracle APEX blog post from January 2024 explains the move from OCPU to ECPU billing. It describes a smaller entry configuration of 2 ECPUs and 20 GB of storage, and notes that you can scale ECPUs and storage up as the app grows. It also says you are not charged by the number of app users, developers or apps.
Prices change and vary by region and contract. Always take current figures from Oracle's APEX pricing page or your Oracle account team, not from articles like this one.
What the APEX service does not include
The APEX service is a restricted workload type of Autonomous Database. Oracle's list of APEX service limitations includes no inbound SQL*Net client access, no bring-your-own-licence option and no Dedicated Infrastructure version. If you need those, Oracle's guidance is to upgrade to Autonomous Transaction Processing, which is priced differently. Check this list before you budget. A missing feature found late is an expensive surprise.
What Always Free gives you
Oracle's Always Free Autonomous Database documentation sets clear limits. In summary:
- Up to two Always Free databases per tenancy, in your home region.
- 20 GB of storage per database and a fixed number of database sessions.
- A small number of simultaneous users across APEX, ORDS and Database Actions.
- No scaling, no private endpoint and no manual or long-term backups.
- An inactive database is stopped after seven days, and may be deleted after a longer period of inactivity.
This is enough to learn APEX, prototype an app and run a short pilot. It is not a production platform for a business process. Budget for a paid service from the start of user acceptance testing. Oracle allows an Always Free database to be updated to a paid instance.
Where the cost actually sits
The table below compares the two approaches on total cost of ownership. The rows are qualitative. Fill in your own figures.
| Cost area | Oracle APEX | Custom development |
|---|---|---|
| Platform licence | No separate APEX licence; database or OCI service cost | Framework often free; database, app server and tools may be paid |
| Hosting | Database service or existing database server | App servers, database, load balancer, often containers |
| Standard screens (forms, reports, search) | Generated and configured | Written and tested by hand |
| Login and access control | Built-in authentication and authorisation schemes | Designed, built and tested by your team |
| Team roles | APEX and PL/SQL developers, part-time DBA | Front-end, back-end, database and DevOps skills |
| Security patching | APEX and database patches, applied by you or by a managed cloud service | Every library and framework patched by you |
| Upgrades | APEX and database upgrades, plus regression testing | Framework and dependency upgrades, often with code changes |
| Change requests | Mostly configuration and SQL or PL/SQL | Code, build, test and redeploy across layers |
| Custom user experience | Limited by the APEX component model; custom work is possible but costs more | Full control, at full cost |
| Exit cost | Apps tied to Oracle Database | Tied to your chosen stack and team |
Two points stand out. First, custom builds spend heavily on things APEX provides: screens, login, session handling and reports. Second, APEX moves cost into the database. If your data is not in Oracle Database today, add the cost of getting it there.
How to estimate your project, step by step
Use the same method for both options so the comparison is fair.
- List the processes, not the screens. Write down who does what, the approvals and the exceptions. For example: raise a purchase request, approve it, create the order, receive goods.
- Count the building blocks. For each process, count data entities, input forms, reports, approval steps, integrations and scheduled jobs.
- Mark what is unusual. Flag anything outside standard forms and reports: complex planning grids, offline mobile use, heavy document handling or a public website.
- Estimate build effort for each option. Ask your team or partner to estimate each building block separately for APEX and for custom. Use ranges, not single numbers.
- Add platform cost. For APEX, use your database licence position or current OCI pricing. For custom, add servers, databases, tools and environments for development, test and production.
- Add five years of running cost. Include support staff, security patching, upgrades, monitoring and backups.
- Add change cost. Estimate how many change requests you expect each year and the effort for a typical one on each option.
- Add risk. Allow contingency for integrations, data migration and any feature gap you found in step 3.
- Compare totals, then build a pilot. Pick one process and build it. A pilot gives you real effort data to replace the estimates.
When custom development is the better choice
APEX is not the answer to every brief. A custom build often makes more sense when:
- The app is a large public-facing product with its own brand and design system.
- Users need to work offline for long periods.
- Your data platform is not Oracle Database and there is no plan to change that.
- The interface is the product, such as a complex visual planner or a consumer app.
For internal business apps that sit on Oracle data, such as approvals, inventory, vendor portals and finance tools, APEX is usually the lower-cost option. Test that view with a pilot.
Cost comparison checklist
- Processes listed with approvals and exceptions
- Building blocks counted per process
- Unusual requirements flagged
- Database licence position confirmed
- Current OCI pricing taken from Oracle, with a date
- APEX service limitations checked against requirements
- Always Free used only for learning and pilots
- Hosting and environments costed for both options
- Five years of support, patching and upgrades included
- Yearly change requests estimated
- Contingency added for integrations and migration
- Pilot planned to test the estimate
Common mistakes
Comparing licence cost only. The licence is rarely the largest line. People cost more.
Running production on Always Free. It has no backups you control and limited concurrent users.
Ignoring upgrade cost. Both options need upgrades. Custom stacks often have more parts to upgrade.
Assuming low-code means no code. Business rules in APEX still live in SQL and PL/SQL. Budget for skilled developers.
Skipping the pilot. Estimates without a pilot are guesses. Use our APEX vendor scorecard to compare proposals on the same basis.
How Egisedge helps
Egisedge Technologies is an Oracle Partner, founded in 2019, with offices in Gurugram and Mahendergarh, India. We build Oracle APEX low-code applications and custom software, so we can estimate both options for your brief.
For a leading Indian auto-components manufacturer, we built Oracle APEX systems for inventory, manufacturing, procurement, payables and billing. We help clients list their processes, cost APEX and custom options side by side, and build a pilot to test the estimate. New to APEX? Start with the Oracle APEX learning path.
To compare Oracle APEX and custom development for your own project, email info@egisedge.com.
Frequently asked questions
Is Oracle APEX free to use?
Oracle describes APEX as a no-cost feature of Oracle Database, so if you already license the database you can build APEX apps on it without a separate APEX licence. On Oracle Cloud you pay for the database service the apps run on. Oracle also offers Always Free options with fixed resource limits. You still pay for the people who design, build and support the apps.
How is the APEX Application Development service on OCI priced?
Oracle prices it on consumption: compute measured in ECPUs per hour, plus database storage. Oracle states there are no charges per app user, developer or app. Check the current figures on Oracle's APEX pricing page, as prices change and vary by region and contract.
Is APEX always cheaper than custom development?
No. APEX usually costs less for data-heavy internal business apps where your data already sits in Oracle Database. A custom build can make more sense for a large public-facing product, a heavily designed user interface, offline mobile use or a non-Oracle data platform. Compare both options against your own requirements before deciding.
Can we start on Always Free and move to a paid service later?
Yes. Oracle's documentation says an Always Free Autonomous Database can be updated to a paid instance for more compute and storage. Always Free is suited to learning, prototypes and pilots. It has limits on storage, sessions and concurrent users, and an inactive database is stopped and can later be reclaimed.
Talk to Egisedge about APEX
Tell us where you are and a senior consultant will reply with next steps.



