Oracle estates, run predictably.

Managed Oracle with Data Guard, RMAN and licence-aware architecture — enterprise database discipline without enterprise database drama.

Data GuardRMAN managedLicence-aware

Talk to us All Databases

Capabilities

Enterprise Oracle, operated

Data Guard

Standby databases with tested switchover and failover.

Standby in a second zone

RMAN done right

Backup and recovery managed, verified by restore drills.

Backups that restore

Licence-aware designArchitectures that respect your Oracle agreements — no audit surprises.Cores placed deliberately

Performance careAWR-driven tuning by DBAs who've seen your wait events before.AWR-driven tuning

Patch cadenceQuarterly updates applied with tested rollback.Current without drama

Sovereign placementRegulated data stays in-jurisdiction on certified hosts.Residency by design

Private networkingListeners live on your networks only.No public listener

Capacity trendingGrowth is watched and expansion agreed before it hurts.No surprise pressure

Migration runwayCross-platform moves with rehearsed cutover.Arrive without weekends

Standby drillsSwitchover rehearsed on an agreed cadence.DR that has been used

Compare the shapes

Single, Data Guard, or licence-aware

Operated Oracle in every shape — the difference is availability and how carefully the licence position is managed around it.

ProductionEdgeComing soon

SHAPE 01

Single Instance

Operated and backed up

One managed instance with RMAN backups, patch cycles and monitoring — for departmental and second-tier Oracle workloads.

Best for

Departmental appsDev & testReporting instances

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

Standard4 vCPU · 32 GB RAM · RMAN backupsSign in →Standard Plus8 vCPU · 64 GB RAM · extended retentionSign in →CustomAny shape, storage and retention windowSign in →

SHAPE 02Production default

Data Guard

Standby you rehearse

Physical standby in a second zone with switchover tested on a schedule — the shape core enterprise applications should be on.

Best for

Core enterprise appsFinance systemsRegulated workloads

Where it runs

Dubai AZ1RiyadhBahrainMumbaiDubai AZ2Nairobi

Plans

Data GuardPrimary + physical standby · tested switchoverSign in →Data Guard PlusCross-zone standby · read-only reporting standbySign in →CustomAny topology, protection mode and drill cadenceSign in →

SHAPE 03

Licence-Aware Estate

Your agreement, respected

Placement and core allocation designed around your existing Oracle agreement, with the position tracked and documented.

Best for

Existing Oracle estatesDatacentre exitsConsolidation programmes

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

BYOLYour licences · pinned core allocationSign in →BYOL PlusPinned placement · Data Guard · position trackedSign in →CustomAny licence model and placement constraintSign in →

Two ways to run it

Managed instance, or database operations

Both are licence-aware by design. The difference is who owns performance and change.

Managed InstancePlatform levelWe run the host, storage, backups and standby; your DBAs keep schema, tuning and application change.

RMAN backups with tested restore

Patch cycles planned with you

Standby health monitored

Best for:Estates with Oracle DBAs

Explore Managed Instance plans

Database OperationsEngine levelDatabase Operations owns tuning, patch and upgrade programmes, capacity planning and switchover rehearsals.

Performance and AWR review cycles

Quarterly switchover rehearsals

Licence-position reporting

Best when:Oracle skills are scarce

Explore Database Operations plans

Who decides, who runs it

What each group gets from Oracle

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“Oracle stopped being a special case”

The Oracle footprint is operated on the same sovereign platform and the same commercial model as everything else.

GovernedSovereignPredictable

FAQs

Can we bring our own Oracle licences?

Yes — that is the usual model. Placement and core allocation are designed around your agreement and tracked.

Do you support Data Guard?

Yes, with physical standby in a second sovereign zone and switchover rehearsed on an agreed cadence.

How are backups run?

RMAN to sovereign object storage with tested restores and retention mapped to your compliance calendar.

Can you take on an existing estate?

Yes. Assessment, licence mapping, landing zone and cutover are run by our team with your DBAs.

Will resizing affect our licence position?

Not without your approval — core allocation is pinned, and any change that touches licensing is raised before it is made.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together