Google Cloud Media and Entertainment Belgium

Inku

Marketing Personalization

Founded in 2026, Belgian company Inku relies entirely on Google Cloud to operate "Brand Engine", an AI layer that understands enterprise brands intimately and enables them to produce content at scale while maintaining total control over their image.

Campaign creation costs reduced by 70% to 75%
Global teams can build briefing, create campaign assets, comment and edit with the team, approve and ship in a matter of minutes, not months.
This enables companies to move from brief to campaign in just a few days, delivering significant gains in costs, speed, and quality.
Where creation costs once rapidly accumulated, the platform drives reductions of 70% to 75%, allowing companies to reallocate those budgets toward more strategic investments.

Reported impact

Business outcome

A Belgian company founded in 2026, aims to transform brand content creation by making it more consistent, faster, and easier to industrialize. Designed to meet the exploding visual needs of marketing teams, its platform relies on an AI trained on each brand's unique DNA, ensuring content is always faithful to its identity.

  • Productivity Improvement
  • Revenue Growth
  • Speed to Market

Solution

"The idea is to stop starting from a blank prompt, but rather from a system that already understands the brand," notes Gus Vanherf. "By injecting context from the information stored on our platform into the generation pipelines, we enable our clients to produce content that is not just fast to create, but above all consistent with their brand, accurate, and ready to use." Designed to manage the entire end-to-end process from the initial brief to asset production the platform offers a unified environment where teams no longer just generate content: they orchestrate complete campaigns faster and with an unprecedented level of control. To realize this vision, Inku built a sophisticated architecture entirely running on Google Cloud. "We needed an infrastructure capable of handling complex workloads, orchestrating different models, and scaling without compromising on performance or security.

Solution architecture

6 components · 3 layers
  1. Compute
    • Cloud Run Runs serverless application services and APIs with automatic scaling for bursty workloads.
  2. Storage
    • Cloud SQL Stores transactional state and application data for the operational workflow at low latency.
    • Cloud Storage Stores source documents, media, or raw files that feed the automated workflow.
  3. Orchestration
    • Gemini Enterprise Agent Platform Coordinates multi-agent workflows, tool calling, and governed automation across the application.
    • Gemini Enterprise Provides the reasoning or generation layer used for classification, orchestration, content generation, or analysis.
    • Agent Platform Coordinates multi-agent workflows, tool calling, and governed automation across the application.

Architecture clues

  • In practice, Inku relies on Google Kubernetes Engine (GKE) and Cloud Run to orchestrate its services and intelligently distribute workloads, continuously adapting resources to actual needs.

Evidence from the source

Campaign creation costs reduced by 70% to 75%
Google Kubernetes Engine (GKE) Cloud Run Gemini Enterprise Agent Platform Cloud SQL Cloud Storage Firebase Authentication
Inku regains control over marketing creation with Google Cloud
On the AI front, Inku uses Gemini Enterprise Agent Platform to orchestrate all its models and seamlessly integrate them into its workflows. "By smoothing out the integration and orchestration of various models within our
Production time for campaigns reduced from several months to a few days
Transparency Evidence & methodology 90/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 value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth15/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 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

    Inku customer story

    First-party
    https://cloud.google.com/customers/inku
    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 Sep 11, 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 Aug 31, 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.