Data egress is the charge that applies when data leaves the cloud provider network. The charge applies to outbound traffic from the cloud region to the public internet, to other cloud providers, and in some cases to other regions on the same provider. The Oracle Cloud Infrastructure egress charges are lower than the corresponding charges on Amazon Web Services and Microsoft Azure. The lower rate is part of the Oracle commercial positioning against the hyperscale competitors. The egress cost is still material on data heavy workloads and warrants negotiation attention.
The OCI egress structure.
The OCI egress charge applies to outbound traffic from the OCI network to destinations outside the OCI network. The charge does not apply to inbound traffic from outside the OCI network. The charge does not apply to traffic within the same OCI region. The charge does apply to traffic between OCI regions on a separate inter region rate.
The standard OCI egress rate is approximately one quarter of the corresponding AWS or Azure rate at the time of writing. The OCI rate is published on the OCI pricing site and is denominated per gigabyte. The rate decreases on a tiered basis as the monthly egress volume increases. The tiering is more aggressive than on the hyperscale providers and produces additional reduction at scale.
The free allowance.
OCI provides a free egress allowance of ten terabytes per month per tenancy at the time of writing. The allowance applies to internet egress and is consumed automatically before the metered egress begins. The allowance is a meaningful difference for buyers with moderate egress volumes who can fit the total monthly egress within the allowance.
The free allowance is a tenancy level allowance rather than a per region allowance. A buyer with multiple OCI regions consumes a single shared allowance across the regions. The allowance is also not negotiable in the published commercial. The published allowance is the floor rather than a negotiation starting point.
The hyperscale comparison.
The egress comparison with the hyperscale providers is one of the principal commercial arguments that Oracle uses in the cloud sales conversation. The Oracle account team will produce comparison tables that show the OCI rate alongside the AWS and Azure rates. The Oracle position is that the egress saving alone justifies the OCI selection for data heavy workloads.
The buyer position should engage with the comparison rather than dismiss it. The egress rate is real and the saving is real. The buyer position should also assess the corresponding charges on the rest of the OCI service portfolio to determine whether the egress saving is offset by higher charges on other components. The net assessment is a workload specific analysis. See the Autonomous Database pricing note for the related cost dimension.
The negotiation levers.
The egress rate is negotiable on substantive OCI commitments. The Universal Credits program offers an effective egress discount through the prepaid balance arrangement. The buyer commitment can also extend the free allowance beyond the published ten terabyte floor as a negotiated concession. The expanded allowance is typically structured as a defined buyer specific allowance rather than as a published rate change.
The negotiation should also address the inter region rate. The inter region rate applies to traffic between OCI regions and can become substantial for buyers with multi region architectures. The inter region rate is published separately from the internet egress rate and is negotiated separately. The buyer position should size the inter region rate against the expected multi region traffic pattern.
Architectural reduction.
The egress cost can be reduced through architectural choices rather than only through commercial negotiation. The use of edge caching, the use of compression on egress paths, and the consolidation of egress through fewer paths all reduce the metered egress volume. The architectural reduction is most effective when it is integrated into the initial deployment design rather than retrofitted after the cost becomes visible.
The architectural choices should also consider the data residency requirements that may force egress between regions or to specific destinations. The data residency requirement is typically a regulatory rather than a commercial driver and may not be negotiable. The architectural design should accommodate the residency requirement and minimise the resulting egress as a secondary objective.
The exit scenario.
The egress charge is the primary commercial obstacle to a future exit from OCI. A buyer that has accumulated petabytes of data on OCI faces a substantial egress charge to migrate the data to another provider. The exit charge can therefore lock the buyer into the OCI service even when the commercial position would otherwise support a move.
The exit scenario should be addressed in the initial commercial negotiation rather than at the exit event. The negotiation should include an exit allowance that waives the egress charge for a defined volume during a defined transition period. The exit allowance is typically structured as a commitment of the Oracle account team rather than as a published contract term and should be captured in writing in the order document.
Engaging an independent advisor.
The OCI egress commercial benefits from external review. An independent advisor can model the egress cost under the actual workload pattern and can identify the negotiation levers that are most material for the specific buyer. The independent review also produces a defensible position for the architectural choices that reduce the egress exposure over the term.
For the wider cluster see Cloud Negotiation. For the service see Cloud Migration Advisory. For the deal structure see OCI Universal Credits. For the Oracle product see Oracle OCI. For the full research read the Oracle Negotiation Playbook.
A worked example.
A European media buyer migrated a content delivery workload to OCI in 2024. The Oracle proposal sized the monthly egress at approximately three hundred terabytes per month. The standard rate produced an egress cost of approximately twenty thousand dollars per month against the workload.
An independent advisor reviewed the egress design and identified that approximately one third of the egress was inter region traffic that could be redirected through architectural changes. The advisor also negotiated an expanded free allowance of fifty terabytes per month as part of the Universal Credits commitment. The corrected monthly egress cost was approximately seven thousand dollars per month. The total annual saving against the original proposal was approximately one hundred and fifty thousand dollars.