Google Cloud Software / SaaS Australia

Sonic Labs

Data Lake / Data Warehouse Modernization · IT Operations Automation · Real-time Analytics

However, in a competitive landscape, it’s not enough for a blockchain to be “fast and cheap,” according to Seg Rashid, Head of AI and Developer Relations at Sonic Labs. The company recognized that to sustainably attract Web3 developers, it needed to shift its focus to simplifying development with AI resources. Before adopting cloud solutions, system scalability and limited flexibility were major bottlenecks.

, a Google Cloud partner, builds elite Web3 and AI solutions. It provides expert cloud delivery, IaaS, blockchain analytics, AI and managed services to a global clientele.
Eliminates manual pre-processing of support logs with Gemini 2.5 Pro
Enables functional dApp development from concept to launch in 15 minutes with Gemini
Industry: Web3

Reported impact

Business outcome

Enables functional dApp development from concept to launch in 15 minutes with Gemini; models in Vertex AI; Full availability blockchain operations on Google Cloud during market disruptions; Eliminates manual pre-processing of support logs with Gemini 2.5 Pro.

  • Productivity Improvement
  • Revenue Growth
  • Risk Reduction
  • Scalability

Solution

To manage this data stream, Sonic Labs built a robust, cloud-native data pipeline on Google Cloud for analysis. The architecture uses Google Kubernetes Engine for orchestration, Cloud Pub/Sub for scale ingestion, Dataflow for transformation, and BigQuery as its enterprise data warehouse. The same AI principles power internal workflow orchestration. The team uses to process unstructured tech support logs and other submissions. The large context window of Gemini models drastically reduces engineering time by eliminating the need to build complex data pre-processors. It then employs its structured output feature to instantly transform the raw data into nicely formatted, actionable tech support tickets, saving time for support staff and streamlining information handover.

Data flow

Source data is captured through Cloud Pub/Sub, stored or unified in BigQuery, Cloud Storage, processed with Vertex AI, orchestrated via Google Kubernetes Engine, Cloud Composer, and surfaced through Gemini

Solution architecture

7 components · 5 layers
  1. Ingest
    • Cloud Pub/Sub Moves events between services so the platform can process updates asynchronously at scale.
  2. Compute
    • Vertex AI Hosts and orchestrates machine learning and generative AI capabilities inside the solution.
  3. Storage
    • BigQuery Stores and queries the analytics and AI-ready datasets that power the workload.
    • Cloud Storage Stores large files, lake data, or static assets that feed downstream analytics and applications.
  4. Serving
    • Gemini Powers natural-language reasoning, summarization, generation, or assistance inside the workflow.
  5. Orchestration
    • Google Kubernetes Engine Orchestrates the platform's containerized services and high-concurrency workloads.
    • Cloud Composer Schedules and orchestrates data pipelines across Google Cloud services.

Architecture clues

  • # Sonic Labs: Redefining developer experience for dApp growth with Gemini models
  • Eliminates manual pre-processing of support logs with Gemini 2.5 Pro
  • Enables functional dApp development from concept to launch in 15 minutes with Gemini
  • Full availability blockchain operations on Google Cloud during market disruptions
  • Sonic Labs uses Google Cloud for reliability and data analytics, improving AI devX with Gemini models in Vertex AI to enable its app builder, Spawn.
  • models in Vertex AI

Evidence from the source

Eliminates manual pre-processing of support logs with Gemini 2.5 Pro
Enables functional dApp development from concept to launch in 15 minutes with Gemini
Full availability blockchain operations on Google Cloud during market disruptions
Sonic Labs uses Google Cloud for reliability and data analytics, improving AI devX with Gemini models in Vertex AI to enable its app builder, Spawn.
models in Vertex AI
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
    2 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
    5 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

    Sonic Labs customer story

    First-party
    https://cloud.google.com/customers/soniclabs
    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 Apr 30, 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 Apr 22, 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.