Google Cloud Software / SaaS Cyprus

Quarks

Marketing Personalization · Risk Management

Quarks needed to personalize social-discovery experiences and scale safety moderation for millions of users without the idle GPU costs, operational friction, and inflexibility it hit while trying to run open-weight models for unpredictable traffic.

Moderation coverage increased from 17% to 100%
the team now able to respond to critical safety incidents in under one minute

Reported impact

Business outcome

Quarks improved personalization and platform safety at the same time, expanding moderation coverage to the entire service, cutting incident response to under a minute, and avoiding the GPU inefficiency that previously limited scale.

  • Customer Experience
  • Risk Reduction
  • Scalability

Solution

Quarks standardized its AI stack on Gemini models and Gemini Enterprise Agent Platform so it could serve personalization, safety, and image-enhancement use cases from one production foundation. The company first evaluated Gemma models on dedicated GPU resources, but fluctuating day-and-night request patterns left expensive capacity idle and made scaling difficult. By moving to Gemini and Agent Platform, Quarks can swap models in seconds, keep customer-facing assistants responsive, and run moderation pipelines without rebuilding infrastructure. Gemini powers context-aware guidance in products such as Affemity, optional profile-photo enhancement, and large-scale content moderation workflows. The platform lets Quarks reserve human review for nuanced edge cases while using Google Cloud-managed AI infrastructure to increase coverage, respond faster to incidents, and sustain multimodal experiences at global consumer scale.

Data flow

User profile data, prompts, and content enter Gemini Enterprise Agent Platform, which invokes Gemini models for recommendation guidance, profile-photo enhancement, and moderation. Outputs either return directly to the user experience or escalate to human moderators when a case needs nuanced review.

Solution architecture

2 components · 2 layers
  1. Compute
    • Gemini Powers personalized assistants, image-enhancement features, and moderation reasoning across Quarks consumer experiences.
  2. Orchestration
    • Gemini Enterprise Agent Platform Hosts and orchestrates the production AI workloads so Quarks can scale multimodal features and switch models quickly.

Architecture clues

  • Gemini Enterprise Agent Platform powers several core customer-facing use cases
  • Human moderators now focus on cases that require nuanced judgment
  • Quarks can swap models in seconds without rebuilding the system
  • The team previously evaluated Gemma 2 and Gemma 3 on dedicated GPU resources before standardizing on Gemini

Evidence from the source

Gemini powers sophisticated AI assistants across Quarks' platforms, such as Affemity.
Gemini supports Quarks' content moderation workflows by helping review profile content at scale.
The integration of Gemini models and the Gemini Enterprise Agent Platform has driven massive quantitative and operational success for Quarks.
We standardized on Gemini across every product because it offered the best balance of cost, performance, and multimodal capability.
profile moderation coverage increased from 17% to 100% with the team now able to respond to critical safety incidents in under one minute.
Transparency Evidence & methodology 80/100 reference value · 82% confidence · 2 sources

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 value80/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 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 transparency9/10
    2 source references 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

    Quarks customer story

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

    Quarks Technosoft Company Profile (2026)

    Independent secondary
    https://getlatka.com/companies/quarks-technosoft

    The profile says Quarks Technosoft has 700 employees (September 2026), which falls in the 250-999 Mid-market range.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

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