Google Cloud Software / SaaS Vietnam

Filum

Real-time Analytics

In the early stages, the team managed data pipelines using manual Python scripts and spreadsheets.

Looking ahead to 2026, Filum is adopting an AI-first product strategy. The team plans to integrate Vertex AI into internal workflows, empowering every department — from design to engineering — to accelerate development.
Manages 100+ integrations with just 2 staff using Cloud Run
With Google Cloud acting as an incubator that provides early access to technology and strategic guidance, Filum is well-positioned to release an overhaul of its product in 2026, bridging the gap between raw data and actionable business…

Reported impact

Business outcome

Manages 100+ integrations with just 2 staff using Cloud Run; Cuts infrastructure maintenance to zero with Cloud Run functions

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Revenue Growth

Solution

In the early stages, the team managed data pipelines using manual Python scripts and spreadsheets. Generates instant customer insights with Build with Gemini 3 Incoming messages enter Pub/Sub , which queues the traffic to prevent data loss during sales rushes. Key components include Gemini provides the reasoning or generation layer used for classification, orchestration, content generation, or analysis; Vertex AI provides the reasoning or generation layer used for classification, orchestration, content generation, or analysis; BigQuery stores and queries the analytics and AI-ready datasets that power the workload; Looker provides the governed semantic layer, dashboards, and self-service analytics used by business teams; Pub/Sub moves high-volume events and API traffic between services so the workflow stays decoupled and resilient. Incoming messages enter Pub/Sub , which queues the traffic to prevent data loss during sales rushes. Reported outcomes include Manages 100+.

Data flow

Incoming messages enter Pub/Sub , which queues the traffic to prevent data loss during sales rushes.

Solution architecture

6 components · 4 layers
  1. Ingest
    • Pub/Sub Moves high-volume events and API traffic between services so the workflow stays decoupled and resilient.
  2. Compute
    • Gemini Provides the reasoning or generation layer used for classification, orchestration, content generation, or analysis.
    • Vertex AI Provides the reasoning or generation layer used for classification, orchestration, content generation, or analysis.
    • Cloud Run Runs serverless or virtualized application services with elastic scale for production AI workloads.
  3. Storage
    • BigQuery Stores and queries the analytics and AI-ready datasets that power the workload.
  4. Serving
    • Looker Provides the governed semantic layer, dashboards, and self-service analytics used by business teams.

Architecture clues

  • Filum turns fragmented data into unified customer insights with zero DevOps overhead.
  • Filum was founded to help Asian enterprises — from retailers to banks — transform fragmented customer data into actionable business intelligence to ultimately build deep customer loyalty.
  • In the early stages, the team managed data pipelines using manual Python scripts and spreadsheets. As the startup onboarded large retailers such as ZUS Coffee and GS25, data volumes surged. The manual approach failed to…
  • Lacking specialized DevOps engineers in-house, Filum sought to adopt a fully-managed solution to address this issue. It selected Google Cloud for its serverless architecture, specifically adopting to handle schema-less…
  • To eliminate the need for infrastructure management, Filum adopted a fully serverless stack. By leveraging and , the team treats each of the hundreds of client integrations as a standalone function that auto-scales…

Evidence from the source

Cuts infrastructure maintenance to zero with Cloud Run functions
Filum turns fragmented data into unified customer insights with zero DevOps overhead.
Generates instant customer insights with Build with Gemini 3
In the early stages, the team managed data pipelines using manual Python scripts and spreadsheets. As the startup onboarded large retailers such as ZUS Coffee and GS25, data volumes surged. The manual approach failed to…
Manages 100+ integrations with just 2 staff using Cloud Run
The serverless architecture significantly reduced development time, saving us weeks of integration effort.
Transparency Evidence & methodology 73/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 value73/100
  • Problem clarity12/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 specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric 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

    Filum customer story

    First-party
    https://cloud.google.com/customers/filum
    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 Feb 7, 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 Jan 19, 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.