Google Cloud Healthcare Global

Hexis

Customer Service Automation

Hexis needed to translate dense exercise physiology and nutrition science into instant, personalized athlete guidance while synchronizing wearable data globally and shipping new product features much faster.

10x faster feature development with
<50 milliseconds to deliver nutritional insights
Hexis uses Google Cloud and Gemini to scale its nutrition OS for human performance globally and ship features 10x faster.

Reported impact

Business outcome

Hexis delivered near-instant nutritional guidance, accelerated feature development, and built the basis for an automated digital coach that can scale beyond elite sports organizations.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Hexis uses Google Cloud to address this challenge: Hexis needed to translate dense exercise physiology and nutrition science into instant, personalized athlete guidance while synchronizing wearable data globally and shipping new product features much faster. Compute Engine processes training, meal, and wellness data and runs the stateless application instances that power real-time coaching, serving as the compute layer. Cloud SQL for PostgreSQL stores the multi-regional athlete data that stays synchronized across Europe, the US, and Australia, serving as the storage layer. Gemini interprets natural-language, image, and voice inputs and converts them into structured nutrition data and coaching explanations, serving as the serving layer. Gemini Notebook centralizes scientific research into an internal knowledge base that accelerates onboarding and feature work, serving as the serving layer.

Data flow

Workout and wellness signals from connected devices sync into a multi-regional Cloud SQL store, Compute Engine processes the data for the Carb Coding system, and Gemini turns photos, voice notes, and natural-language questions into structured nutrition outputs and coaching responses.

Solution architecture

4 components · 3 layers
  1. Compute
    • Compute Engine processes training, meal, and wellness data and runs the stateless application instances that power real-time coaching
  2. Storage
    • Cloud SQL for PostgreSQL stores the multi-regional athlete data that stays synchronized across Europe, the US, and Australia
  3. Serving
    • Gemini interprets natural-language, image, and voice inputs and converts them into structured nutrition data and coaching explanations
    • Gemini Notebook centralizes scientific research into an internal knowledge base that accelerates onboarding and feature work

Architecture clues

  • A new Nutrients feature shipped in three days instead of an estimated 30
  • Application instances run statelessly across Europe, the US, and Australia behind global load balancing
  • Gemini returns nutrition breakdowns in under 50 milliseconds

Evidence from the source

10x faster feature development with
<50 milliseconds to deliver nutritional insights
Hexis engineers used Gemini to design, build, and launch a new Nutrients feature in just three days, 10x faster than the estimated 30 days.
Hexis uses Compute Engine-managed instance groups and a multi-regional Cloud SQL for PostgreSQL database to continuously sync live workout and wellness data from connected fitness devices.
Hexis uses Google Cloud and Gemini to scale its nutrition OS for human performance globally and ship features 10x faster.
Taking a picture of a plate of food or recording a quick voice note triggers Gemini.
Transparency Evidence & methodology 96/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 value96/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/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
    6 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

    Hexis customer story

    First-party
    https://cloud.google.com/customers/hexis
    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

    Hexis | LinkedIn

    Third-party
    https://www.linkedin.com/company/hexis-performance/

    The public company page's embedded Organization metadata includes numberOfEmployees value 27.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • First archived Sep 25, 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 Sep 7, 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.