Google Cloud Media and Entertainment Australia

Orbx

Application Refactoring · IT Operations Automation · Real-time Analytics

Orbx needed to re-architect its simulation and tracking platforms for elasticity, real-time data handling, and faster release cycles while lowering cloud spend enough to reinvest in new AI capabilities.

4x faster releases
Boosts release velocity 400%
Cuts costs 30% to reinvest in AI

Reported impact

Business outcome

Orbx shipped updates faster, reduced cloud cost, and created a more elastic real-time media platform that can support both current experiences and future AI-assisted development workflows.

  • Cost Reduction
  • Scalability
  • Speed to Market

Solution

Orbx rebuilt its environment on Google Cloud with help from partner Sakura Sky so its immersive-content and live-tracking products could operate as cloud-native services. Google Kubernetes Engine provides the elasticity behind titles such as Volanta, automatically scaling when thousands of users log in at once and shrinking during quiet periods to control cost. Bigtable ingests heavy streams of real-time positional data, Cloud SQL stores player inventories, and BigQuery analyzes flight-cost and operational data. Around that core, Cloud Vision API, Cloud Storage, Pub/Sub, Cloud Build, Cloud Logging, and Cloud Monitoring help Orbx process assets, automate infrastructure pipelines, and observe platform behavior. Gemini Code Assist and broader Gemini experiments now sit on top of the same foundation, giving Orbx a platform that improved release velocity, reduced spend, and created room to explore coding agents and workflow summarization.

Data flow

Gameplay and platform events are ingested into Bigtable and moved through Pub/Sub-backed workflows while GKE scales the application tier. Transactional inventory data lives in Cloud SQL, analytics flow into BigQuery, and Cloud Build plus observability services support release and operations workflows.

Solution architecture

7 components · 4 layers
  1. Ingest
    • Pub/Sub Moves platform events through the re-architected cloud-native environment.
  2. Storage
    • Bigtable Ingests massive real-time positional-data streams generated by live platform activity.
    • Cloud SQL Stores player-inventory and other transactional application data.
    • BigQuery Analyzes flight-cost and operational data for the business.
  3. Serving
    • Gemini Code Assist Supports developer productivity on the modernized platform.
  4. Orchestration
    • Google Kubernetes Engine Scales Orbx's simulation and tracking services up and down with player demand.
    • Cloud Build Automates infrastructure and release pipelines for faster delivery.

Architecture clues

  • Bigtable ingests real-time positional data
  • GKE handles elasticity for Volanta when thousands of players log in simultaneously
  • Partner Sakura Sky re-architected the environment to be cloud-native
  • The team is exploring Vertex AI coding agents on top of the same platform

Evidence from the source

Boosts release velocity 400% with Google Kubernetes Engine
Cuts costs 30% to reinvest in AI with Google Kubernetes Engine autoscaling
Meanwhile, the team needs to process heavy write loads. Orbx implemented Bigtable to ingest massive streams of real-time positional data.
Orbx engaged Partner Sakura Sky to re-architect its environment to be cloud-native
for the Volanta flight tracking platform, Orbx uses Google Kubernetes Engine (GKE) to handle massive elasticity.
Transparency Evidence & methodology 95/100 reference value · 82% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Google Cloud

    Orbx customer story

    First-party
    https://cloud.google.com/customers/orbx
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. LinkedIn

    Orbx | LinkedIn

    Independent secondary
    https://www.linkedin.com/company/orbx/

    LinkedIn's Organization JSON-LD lists addressLocality 'Essendon Fields', addressRegion 'VIC', addressCountry 'AU', and numberOfEmployees value 37.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • First archived Apr 12, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Mar 30, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.