Spatial rides for free on Autonomous Database but rides on top of your BYOL or License Included database bill everywhere else. This guide quantifies the fork so your GIS estate lands on the cheaper deployment for the workload it actually runs.
How an EBS Estate Drifts Out of Compliance
Session 5 of the Oracle EBS Licensing Series. An EBS estate rarely goes out of compliance by buying too little. It drifts in place, with no purchase order and no decision: helpdesk granted responsibilities, self service populations sliding into professional grade, database options enabled by default, and the restricted use boundary crossed by ordinary reporting work.
Spatial rides for free on Autonomous Database but rides on top of your BYOL or License Included database bill everywhere else. This guide quantifies the fork so your GIS estate lands on the cheaper deployment for the workload it actually runs.
Since December 5, 2019, Oracle Spatial (formerly Spatial and Graph) is included with Oracle Database at no additional option charge. It is bundled into Enterprise Edition, Standard Edition 2, Database Cloud Service, and Autonomous Database. Before that date it was a paid Enterprise Edition option at $17,500 per Processor or $350 per Named User Plus. That change is the entire premise of this article: Spatial itself no longer carries a line item, so the cost of running Spatial in the cloud is almost entirely the cost of the database compute underneath it.
The practical consequence: on Autonomous Database you get Spatial for free with the platform, and on self-managed OCI (Database on compute, DBCS, or Exadata) you get Spatial for free with the Enterprise Edition licence you are already paying for. Neither model bills the option. The fork is not "Spatial costs money here and not there." The fork is which compute model, and which licence posture (BYOL versus License Included), your GIS workload should run on. Get that wrong and you overpay by six or seven figures a year, with the option riding along for free either way.
Spatial is free in both models. The money is in the compute rate and the BYOL versus License Included gap underneath it.
Oracle documents Spatial as included in Autonomous AI Database Serverless, along with Spatial Studio as an Oracle-managed tool and the Geocoding API as an Oracle-managed service (no extra licence, no data acquisition). This is genuinely convenient for teams that want location intelligence without standing up mid-tier infrastructure. But convenient is not the same as free. Autonomous Database is consumption priced per ECPU, and that meter runs whether or not you touch a single Spatial function.
The published ECPU rates are $0.336 per ECPU-hour with License Included, or $0.0807 per ECPU-hour with BYOL. BYOL cuts the compute rate roughly 76 percent. The BYOL mapping is one Enterprise Edition Processor licence per 8 ECPUs (equivalently 25 Named User Plus per 8 ECPUs). On OCPU-based Serverless the list rates are $4.0288 per OCPU-hour without BYOL and $1.3441 with BYOL, mapping one EE Processor licence per 2 OCPUs. Serverless auto-scales and pauses to zero when no queries run, which helps bursty GIS analytics but hurts you when auto-scaling drifts unmanaged.
Two Spatial-specific caveats matter for GIS teams. First, Spatial Studio's default shape is included at no extra cost, but attaching a compute environment to remove its limitations is billed under Autonomous Database Serverless tool pricing. Second, Oracle's own docs state that on dedicated infrastructure the Routing Engine and mid-tier Geocoder are not available, and some components must be pulled from Oracle Cloud Marketplace. A May 2025 Oracle developer post says routing is available via a PL/SQL API on both Serverless and Dedicated, which partially contradicts the limitations doc. Treat that contradiction as a design risk: pin your exact routing and geocoding requirements against the current tenancy documentation before you commit, because the answer differs by Serverless versus Dedicated and by release.
On self-managed OCI (Database EE on standard compute, DBCS, or Exadata), Spatial is included with the Enterprise Edition or SE2 licence. The cost variable is entirely BYOL versus License Included. On standard OCI compute the License Included rate for EE is roughly $1.34 per OCPU-hour, and the BYOL rate is roughly $0.32 per OCPU-hour. The $1.02 per OCPU-hour gap is the embedded licence cost. That is the number you either pay to Oracle as a rental or offset with licences you already own.
The BYOL mapping is the same as the wider OCI rule set: one EE Processor licence covers 2 OCPUs, where one OCPU equals two physical cores (or one core with hyper-threading). For a 128-OCPU EE instance, BYOL versus License Included can be worth roughly $2.4M in annual compute savings, per market pricing references. The mechanics and the double-count trap are covered in our BYOL versus License Included comparison and the wider OCI licensing cost guide.
| Model | Metric | List rate | BYOL rate | Rate delta | BYOL mapping |
|---|---|---|---|---|---|
| Autonomous DB Serverless (ECPU) | ECPU-hour | $0.336 | $0.0807 | ~76% cut | 1 EE Proc / 8 ECPUs |
| Autonomous DB Serverless (OCPU) | OCPU-hour | $4.0288 | $1.3441 | ~67% cut | 1 EE Proc / 2 OCPUs |
| Self-managed EE on OCI compute | OCPU-hour | ~$1.34 | ~$0.32 | ~$1.02/OCPU-hr | 1 EE Proc / 2 OCPUs |
Read the table as a rate comparison, not a like-for-like TCO comparison. ECPU and OCPU are different units, Autonomous adds managed automation and Spatial Studio, and Serverless can pause to zero. What is constant across every row: Spatial the option is $0, and BYOL cuts the meter two-thirds to three-quarters. If you own the licences, BYOL is almost always the right posture. The only question is whether you own enough, unused, on active support.
Take a mid-sized GIS estate running steady state at 50 OCPUs of Enterprise Edition on OCI compute over a 720-hour month. The License Included versus BYOL difference is about $36,720 per month, roughly $440,000 per year, for identical Spatial functionality. Nobody is paying for Spatial in that number. They are paying for a licence rental they could have offset with owned licences. That is the single largest avoidable cost in a Spatial cloud migration, and it has nothing to do with the option.
A 50-OCPU estate on License Included instead of BYOL burns about $440,000 a year for zero extra Spatial capability.
On the Autonomous side the same principle holds at a different scale. Because Serverless pauses to zero and auto-scales, a bursty GIS analytics workload can genuinely be cheaper on License Included Autonomous than on a fixed self-managed footprint, once you factor in idle time. The trap is uncapped auto-scaling: set the maximum ECPU or OCPU ceiling deliberately, because Oracle bills the peak the platform reaches, not the average you intended. Our Autonomous Database licensing metric and levers page covers the auto-scale cap discipline in detail.
Spatial being free does not mean it is invisible to an audit. The oldest trap is Locator, which is the free geometry subset included with Enterprise Edition. Any use of the free Locator functionality automatically records usage of the licence-required Spatial and Graph option in Oracle's usage views. Post-2019 that specific option is bundled, so the finding is less dangerous than it once was, but Oracle's own bug notes concede the view is "not a true test for use of SDO." If you are still on a pre-2019 licence posture, or an LMS reviewer reaches back to legacy usage, that false positive can become a claim. See Locator versus Spatial: where the free line sits and the pattern behind an accidental Spatial enablement finding.
The Graph Server boundary deserves emphasis for GIS teams because it is the one place where "free Spatial" can still generate a bill. In-database Spatial SQL is covered by the bundled option. An external Graph Server or PGX process running property graph analytics is a different licensable component post-23ai. If your Spatial Studio deployment pushes work to an external process, price that separately. The migration nuance is covered in what happened to the Graph licence in 23ai.
There is a live cost-recovery opportunity for teams that still pay support on historical Spatial and Graph option licences. Oracle positioned the 2019 inclusion as a benefit for new users while continuing to collect support on pre-existing Spatial licences, even though the functionality is now part of the base Enterprise Edition licence. If you are still paying a support stream tied to a legacy Spatial option CSI, that is money spent on a capability you now receive for free. Review those support lines against your current entitlement and challenge the renewal. Even a partial reduction compounds every year on the standard 8 percent uplift, and it feeds directly into the broader Oracle cost optimization playbook.
One further lever on the cloud side: Oracle Support Rewards can offset the on-premises support bill by 25 to 33 percent of OCI consumption. If you are running self-managed Spatial workloads on OCI under BYOL, the consumption that funds your compute also earns rewards that cut the very support stream you need to keep active for BYOL eligibility. Model those two together, because they are financially linked.
First, stop treating Spatial as a cost decision. It is a free option in both cloud models. The decision is compute model plus licence posture. Map each GIS workload to steady-state versus bursty. Steady-state, predictable footprints usually favour self-managed BYOL on OCI compute at the roughly $0.32 per OCPU-hour rate. Bursty analytics that idle for long periods often favour Autonomous Serverless with BYOL and a hard auto-scale cap.
If you are running SE2 rather than Enterprise Edition, note the feature ceiling before you plan around it: Spatial is included on SE2 but with functional limits documented in Spatial on Standard Edition 2. The broader option-in-audits context sits in the Spatial and Graph licensing buyer guide. Run the BYOL math before you sign any Universal Credits commitment, because negotiated discounts range from 10 percent at a $250K annual commit to 35 percent-plus at $10M-plus, and the commitment size is a lever you set once.
Yes. Spatial is included in Autonomous Database at no additional option charge, along with Spatial Studio as an Oracle-managed tool and the Geocoding API as an Oracle-managed service. You still pay the Autonomous compute meter per ECPU or OCPU, and attaching a compute environment to remove Spatial Studio limitations is billed separately.
No, not for the option itself. Since December 5, 2019, Spatial is included with Enterprise Edition and Standard Edition 2. On self-managed OCI you pay for the database compute under BYOL or License Included, and Spatial rides along at no additional charge. The cost variable is your licence posture, not the option.
BYOL cuts the compute rate by roughly 76 percent on Autonomous Database ECPU pricing and by about $1.02 per OCPU-hour on self-managed EE compute. For a 50-OCPU steady-state estate that is about $36,720 per month, roughly $440,000 a year, for identical Spatial functionality.
Yes. Any use of the free Locator functionality automatically records Spatial option usage in Oracle's DBA views, and Oracle's own notes admit the view is not a true test for Spatial use. Post-2019 the option is bundled, but keep Locator-only evidence to defend against a false-positive finding, especially against legacy licence positions.
Oracle's docs state the Routing Engine and mid-tier Geocoder are not available on dedicated infrastructure, and some components require downloads from Oracle Cloud Marketplace. A separate Oracle developer post says routing is available via a PL/SQL API on both Serverless and Dedicated, which conflicts with the limitations doc. Confirm your exact requirements against current tenancy documentation before committing.
Steady-state, predictable footprints usually favour self-managed BYOL on OCI compute at roughly $0.32 per OCPU-hour. Bursty analytics that idle for long periods often favour Autonomous Serverless with BYOL and a hard auto-scale cap, since it pauses to zero. Model both against your workload profile, because Spatial is free in either model.
The buyer side map for Oracle Cloud@Customer: Exadata and Compute Cloud@Customer, Dedicated Region, and the BYOL economics that lower cost.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
