Google Cloud Software / SaaS Global

Encord

Application Refactoring

Encord needed an infrastructure platform that could keep pace with rapid growth in data-intensive AI workloads while staying simple enough for a small startup team to operate efficiently across geographies.

35% reduction in customer dataset size, with optimized storage on Google Cloud
350% increase in
Encord delivers 60% faster model training for customers, with the help of

Reported impact

Business outcome

Encord simplified operations, improved customer training throughput, and created a globally scalable base for fast-growing AI data workloads.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Encord uses Google Cloud to address this challenge: Encord needed an infrastructure platform that could keep pace with rapid growth in data-intensive AI workloads while staying simple enough for a small startup team to operate efficiently across geographies. Cloud GPUs provide the training and inference horsepower customers need for faster model-development pipelines, serving as the compute layer. Compute Engine hosts the GPU-backed processing environment that can be placed near customer data for low-latency operation, serving as the compute layer. Cloud SQL stores the operational data that supports Encord’s data platform at scale, serving as the storage layer. Google Kubernetes Engine supports the broader scalable platform architecture as usage grows, serving as the orchestration layer. Gemini is being adopted to speed up Encord’s internal coding and development work, serving as the compute layer.

Data flow

Customer datasets are processed on regional GPU-backed Compute Engine infrastructure, Cloud SQL stores platform state, GKE supports the service runtime, and Encord can keep data close to where it is created so robotics and autonomy customers avoid excess latency and transfer cost.

Solution architecture

5 components · 3 layers
  1. Compute
    • Cloud GPUs provide the training and inference horsepower customers need for faster model-development pipelines
    • Compute Engine hosts the GPU-backed processing environment that can be placed near customer data for low-latency operation
    • Gemini is being adopted to speed up Encord’s internal coding and development work
  2. Storage
    • Cloud SQL stores the operational data that supports Encord’s data platform at scale
  3. Orchestration
    • Google Kubernetes Engine supports the broader scalable platform architecture as usage grows

Architecture clues

  • Global regional availability keeps data close to robotics and vehicle deployments
  • Google Cloud usage grew 350% in one year to support expansion
  • The team views Gemini as a next step for internal developer productivity

Evidence from the source

35% reduction in customer dataset size, with optimized storage on Google Cloud
350% increase in
Encord delivers 60% faster model training for customers, with the help of
Encord delivers 60% faster model training for customers, with the help of Cloud GPU pipelines.
Its powerful Cloud SQL databases and compute services provided the necessary infrastructure to process complex datasets.
This automation depends on the immense computing power of Cloud GPUs running on Compute Engine.
Transparency Evidence & methodology 95/100 reference value · 79% confidence · 1 source

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 confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 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 transparency8/10
    1 source reference 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

    Encord customer story

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

Date evidence

  • First archived Aug 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 Jul 16, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.