Google Cloud Software / SaaS France

Beamy

IT Operations Automation

Large enterprises could not see how employees actually used applications and business processes across thousands of SaaS tools, which made it hard to control shadow IT, rationalize licenses, and prioritize AI initiatives with the highest business impact.

6,000 applications in use on top of those officially tracked by IT (Veolia)
Billions of unique behavioral data points processed through Google Cloud managed services
Efficient AI prioritization among 1,000+ initiatives
the analysis caused an initial 'electric shock': we thought we had a catalog of about 4,000 applications; Beamy revealed that over 10,000 solutions were actually being used across the company.

Reported impact

Business outcome

Beamy revealed thousands of previously untracked applications, helped customers rationalize licenses and negotiate spend, and gave enterprises a fact-based way to choose among more than 1,000 candidate AI initiatives.

  • Cost Reduction
  • Productivity Improvement
  • Speed to Market

Solution

Beamy built an AI-driven business transformation platform on Google Cloud to reconstruct how people, technologies, and business processes actually interact inside large organizations. A browser extension captures real-time employee activity such as opening tickets, editing CRM fields, or validating invoices, then transforms those interactions into structured logs. Vertex AI models analyze those logs to identify process patterns across a sprawling application estate, while Cloud Run executes Beamy's serverless application services, BigQuery stores and analyzes large-scale behavior data, and Looker exposes the resulting insights through dashboards for business and IT leaders. This architecture lets customers such as Veolia see the gap between official inventories and real usage, negotiate software spend with evidence, and prioritize more than a thousand AI opportunities based on actual work patterns instead of assumptions.

Data flow

A browser extension observes employee actions across enterprise applications, turns those events into structured logs, analyzes the logs with Vertex AI to reconstruct real business process sequences, stores the behavioral data in BigQuery, and serves prioritized insights to customers through Looker dashboards and Beamy's platform services.

Solution architecture

4 components · 3 layers
  1. Compute
    • Cloud Run Executes Beamy's application services in a serverless architecture.
    • Vertex AI Runs the AI models that identify processes and patterns across the application estate.
  2. Storage
    • BigQuery Stores and analyzes large-scale behavioral and application-usage data.
  3. Serving
    • Looker Delivers dashboards and actionable visibility to business and IT teams.

Architecture clues

  • Beamy uses serverless Cloud Run services with BigQuery storage and Looker dashboards.
  • Structured events are reconciled to rebuild business process sequences rather than simple app inventories.
  • The company plans to use Google Cloud Marketplace to accelerate international expansion.
  • The platform begins with a browser extension that observes real-time activity.

Evidence from the source

Beamy also uses Cloud Run to execute its application services in a serverless architecture, BigQuery for large-scale data storage and analysis, and Looker to deliver actionable dashboards to its clients.
Beamy leverages Google Cloud to analyze real application usage within large organizations.
Beamy utilizes AI models deployed by Vertex AI.
The system uses a browser extension to observe real-time employee activity. Interactions (opening a ticket, modifying a CRM field, validating an invoice) are transformed into structured logs.
we thought we had a catalog of about 4,000 applications; Beamy revealed that over 10,000 solutions were actually being used across the company.
Transparency Evidence & methodology 71/100 reference value · 77% 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 value71/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence77%
  • 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 specificity8/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

    Beamy customer story

    First-party
    https://cloud.google.com/customers/beamy
    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 May 13, 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 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.