Tencent Cloud Healthcare Brazil

Biodoc

Fraud Detection · Risk Management

Biodoc needed a more scalable, cost-efficient, and resilient platform for real-time healthcare service authorization and facial-recognition-based patient validation as its customer base grew.

30% lower infrastructure costs compared to its previous setup.

Reported impact

Business outcome

Biodoc reduced infrastructure cost by 30% while gaining more scalable, elastic, and resilient support for facial-recognition and healthcare authentication workloads, improving business continuity and the reliability of real-time patient validation.

  • Cost Reduction
  • Customer Experience
  • Risk Reduction
  • Scalability

Solution

Biodoc modernized its healthcare authentication stack by extending its previously AWS-only environment into a multi-cloud architecture that uses Tencent Cloud for AI-heavy identity workflows. The deployment centers on Kubernetes (TKE) to run production and sandbox environments, with GPU-backed compute accelerating facial-recognition models and other AI workloads. PostgreSQL and MongoDB store operational and scalable data, while messaging services support real-time healthcare processing. Tencent Cloud eKYC adds 1:1 and 1:N liveness checks so patient validation can combine facial recognition with stronger anti-fraud identity verification. Rather than replacing everything at once, Biodoc integrated Tencent Cloud with its existing AWS stack to improve elasticity, business continuity, and secure real-time authorization for clinics, hospitals, and healthcare operators.

Data flow

Healthcare operators send patient-validation workloads into Biodoc services running on TKE. GPU-backed facial-recognition models process the checks, messaging services keep the workflow real time, PostgreSQL and MongoDB persist operational data, and Tencent Cloud eKYC applies 1:1 and 1:N liveness verification before authorization results are returned to clinics, hospitals, and healthcare payers.

Solution architecture

6 components · 4 layers
  1. Compute
    • GPU resources Provide accelerated compute for facial-recognition models and other AI workloads.
  2. Storage
    • PostgreSQL Stores structured application data for the healthcare authorization environment.
    • MongoDB Stores scalable operational data used by Biodoc's authentication services.
  3. Orchestration
    • Kubernetes (TKE) Runs Biodoc's production and sandbox environments for the new healthcare authentication platform.
    • Messaging services Coordinate real-time processing across the healthcare validation workflow.
  4. Governance
    • Tencent Cloud eKYC Applies 1:1 and 1:N liveness-based identity verification to strengthen healthcare authentication.

Architecture clues

  • GPU-backed compute is used to optimize facial-recognition models and AI workloads.
  • PostgreSQL, MongoDB, and messaging services support real-time healthcare processing.
  • The Tencent Cloud environment includes separate production and sandbox deployments.
  • The solution is explicitly multi-cloud and integrates with Biodoc's existing AWS footprint.

Evidence from the source

Biodoc adopted Tencent Cloud's eKYC services, utilizing 1:1 and 1:N liveness APIs to strengthen identity verification and elevate its core healthcare authentication services.
Biodoc is a Brazilian health tech company specializing in healthcare service authorization through facial recognition and artificial intelligence.
Biodoc needed to ensure availability, performance, and scalability in its healthcare data processing and facial recognition services.
By migrating to Tencent Cloud, Biodoc achieved 30% lower infrastructure costs compared to its previous setup, while gaining greater scalability and processing power to support AI and facial recognition workloads.
The new environment includes production and sandbox deployments on Tencent Cloud, PostgreSQL and MongoDB databases for scalable data management, and messaging services enabling real-time processing.
With Tencent Cloud, Biodoc built a modernized architecture centered on Kubernetes (TKE) for efficient container management, leveraging GPU resources to optimize facial recognition models and AI workloads.
Transparency Evidence & methodology 90/100 reference value · 85% 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 value90/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 specificity20/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 confidence85%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 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 transparency10/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. Tencent Cloud

    Biodoc | Tencent Cloud

    First-party
    https://intl.cloud.tencent.com/customers/detail/3530
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Industry
    • Region
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • Business outcome
    • Metrics
    • Architecture
    • evidence quotes
  2. LinkedIn

    BIODOC | LinkedIn

    Independent secondary
    https://www.linkedin.com/company/biodoc-sol/

    The public company page's Organization JSON-LD includes numberOfEmployees value 17.

    Source type
    Structured company profile
    Supports
    • Company size