Oracle APEX · Rate Limits

Oracle Apex Rate Limits

APEX inherits its API throughput from ORDS (Oracle REST Data Services) and the underlying database. Operators tune ORDS connection pools and database resource manager rules to enforce rate limits. Free-tier services (apex.oracle.com, Always-Free Autonomous) apply unpublished fair-use ceilings.

4 Limits Throttle: 429
Low-CodeDatabaseRate LimitingOracle

Limits

APEX hosted workspace (apex.oracle.com) workspace
varies
fair-use; not numerically published
Free shared evaluation environment; suitable for prototyping, not production traffic.
Always-Free Autonomous Database instance
ECPU
fixed-shape (2 ECPU, 20 GB)
Throughput bounded by fixed-shape compute.
Paid Autonomous (APEX Service / ATP) instance
ECPU
configured by instance shape and auto-scale settings
Self-hosted Oracle Database database
varies
bounded by ORDS pool size and DB resource manager

Policies

ORDS pooling
ORDS controls concurrent DB connections; tune jdbc.MaxLimit and jdbc.InitialLimit to shape throughput.
Resource Manager
Use Oracle Database Resource Manager to cap CPU per consumer group when multi-tenant.
Fair use on free tiers
apex.oracle.com and Always-Free instances are intended for prototyping; sustained production load may be throttled or suspended.

Sources