Skip to content

Case Study: Robotron

Delivering sovereign energy software without rebuilding its Oracle platform

How TEAM Cloud gave Robotron New Zealand data residency without forcing it to leave the Oracle technology its business is built on.

Robotron provides specialist energy data management software to energy retailers, gentailers, lines companies and generators across New Zealand. Its fully managed SaaS platform supports critical energy-market functions including metering data, reconciliation, customer switching, billing and market communications.

Robotron's technology was already working well on Oracle Cloud Infrastructure in Sydney. But as New Zealand data residency became increasingly important to customers — and, in some cases, a qualifying tender requirement — Robotron needed a way to host its platform in New Zealand without rebuilding it.

TEAM Cloud provided the answer.

“The biggest saving was the cost we didn’t incur. We didn’t need to re-engineer the platform and we didn’t need to retrain the team.”

 Mark Lovell, Robotron New Zealand

The Challenge

Oracle worked. New Zealand hosting didn't.

Robotron's existing OCI environment was hosted in Sydney and worked technically. The challenge was location: there was no commercial Oracle cloud region in New Zealand.

As customer expectations changed, New Zealand data residency began appearing in RFPs, security questionnaires and risk discussions. For some opportunities, it had become a qualifying requirement.

If Robotron couldn't offer New Zealand hosting, it couldn't bid.

The company therefore needed to solve a very specific problem: how to provide New Zealand sovereignty without abandoning the Oracle platform its entire product was built around.

 

Why not just change cloud providers?

Robotron's platform uses Oracle Database, WebLogic, ORDS and APEX end-to-end. Moving away from Oracle would have meant much more than changing where the platform was hosted.

It would have required:

  • Re-engineering the product
  • Retraining the technical team
  • Reworking operational runbooks
  • Rebuilding established automation and processes

For Robotron, the answer was to change where the platform was hosted — not what the platform was built on.

 

The Solution

Sovereignty without re-engineering

TEAM Cloud, powered by Oracle Cloud Infrastructure, gave Robotron access to the Oracle services, APIs, console and Database Cloud Service environment it already knew.

That meant Robotron could bring customer workloads into New Zealand while retaining its existing technology, skills and operating model.

What TEAM Cloud provided

 
TEAM Cloud_Web Icons_Revolution Infosec_1
OCI-based SaaS platform
With an Oracle-compatible cloud environment
TEAM Cloud_Web Icons
New Zealand data residency
With both primary and disaster recovery environments located in New Zealand
2_TEAM Cloud_Web Icons_REANNZ
Two New Zealand data-centre locations
Two locations for greater resilience
TEAM Cloud_Web Icons_
Scalable parent-child tenancy structure
Supporting multiple customer environments
TEAM Cloud_Web Icons Robotron_4
Four TEAM Cloud tenancies
With two customers live and a third in implementation
TEAM Cloud_Web Icons_Partner Portal_34
No major technical re-skilling required
Existing Oracle expertise & processes carried across

Built around the Oracle platform Robotron already knows

A key benefit of TEAM Cloud was that Robotron didn't need to redesign its existing technology stack.

The move allowed it to retain its:

  • Oracle Database environment
  • WebLogic application servers
  • ORDS and APEX architecture
  • Monitoring and provisioning patterns
  • Security group model
  • Operational knowledge and processes
  • Existing Oracle relationship

For Robotron, this meant sovereignty could be addressed without turning a hosting requirement into a technology transformation project.

 

Designed for a managed SaaS model

Robotron delivers its energy software as a fully managed SaaS service, covering hosting, software licensing, monitoring and management.

TEAM Cloud's parent-child tenancy model fits this structure by allowing Robotron to maintain central visibility and shared tooling while keeping individual customer environments isolated.

Robotron currently operates a parent tenancy for shared monitoring and tooling alongside child tenancies for individual customers.

Four TEAM Cloud tenancies are now in place, with two customer environments live and a third in implementation. The third will be Robotron's largest platform in New Zealand, supporting a major New Zealand gentailer across electricity and gas.

The model provides a repeatable foundation for onboarding additional customers without creating a completely separate cloud-management model for each environment.

 

The Business Impact

TEAM Cloud opened doors for Robotron. The strongest result of the move is commercial.

New Zealand data residency has become a qualifying requirement for some energy-sector customers. TEAM Cloud means Robotron can now meet that requirement and compete for opportunities that were previously unavailable.

Robotron's largest current implementation is with a major New Zealand gentailer and requires in-country hosting. For Robotron, sovereignty is therefore more than a compliance feature. It is helping create new business opportunities.

“Without TEAM Cloud that engagement was not available to us.”

Mark Lovell, Robotron New Zealand

New Zealand primary and disaster recovery

TEAM Cloud gives Robotron an in-country primary and disaster recovery model, with both environments located in New Zealand.

Both data-centre locations are operated by a New Zealand company under New Zealand jurisdiction.

For customers with strict security and risk requirements, this gives Robotron a clear answer not only on where production data is hosted, but where disaster recovery sits too.

 

Connecting sovereign and existing cloud environments

TEAM Cloud doesn't require Robotron to create an isolated technology environment.

Robotron has connected a TEAM Cloud environment back to OCI Sydney using site-to-site VPN for cross-platform integration.

This provides a practical way to connect sovereign New Zealand workloads with existing offshore infrastructure where required, while maintaining the benefits of in-country hosting for customers that need it.

 

The Results

Robotron's move to TEAM Cloud has delivered:

  • New business opportunities — enabling Robotron to pursue opportunities where New Zealand data residency is mandatory
  • No product re-engineering — its existing Oracle-based architecture remains in place
  • No major technical re-skilling — the team can apply its existing Oracle knowledge and operational patterns
  • New Zealand primary and DR — both environments remain in-country
  • Scalable customer architecture — parent-child tenancy supports multiple customer environments
  • Centralised management — shared monitoring and tooling can be managed through the parent tenancy
  • Simpler customer assurance — Robotron can clearly demonstrate where production data and disaster recovery reside

 

Why this matters for Oracle-based ISVs

Robotron's experience demonstrates a practical path for Oracle-based independent software vendors and managed service providers that need New Zealand data residency.

The choice doesn't have to be between keeping an established Oracle technology stack and meeting sovereignty requirements.

With TEAM Cloud, organisations can bring Oracle-based workloads into a sovereign New Zealand cloud without undertaking a wholesale technology transformation.

For businesses whose customers are increasingly asking where their data is hosted, that can turn sovereignty from a constraint into a commercial advantage.

 

Robotron's advice

Robotron's TEAM Cloud footprint is continuing to grow. Its largest current project is being implemented on TEAM Cloud, and the company expects further adoption if sovereignty requirements continue to strengthen across the New Zealand energy sector.

For organisations considering a similar move, Robotron recommends:

  • Plan the tenancy and commercial structure early: Design how customer environments will be structured before customers go live.

  • Understand your application dependencies: Confirm the specific cloud services and features your application relies on before migration.

  • Treat security assurance as its own workstream: Allow dedicated time for security testing and assurance requirements.

  • Bring engineering expertise in early: Particularly for tenancy, networking and service-specific requirements.

Is sovereign cloud becoming a requirement for your customers?

Speak with one of our team today to learn how to get started with TEAM Cloud.