Alibaba Cloud Software / SaaS China Translated from Chinese

Linkedcare (领健)

Linkedcare had to run orthodontic AI inference for dental clinics on infrastructure that was expensive when idle and too slow when demand spiked. Fixed GPU servers stayed underused in quiet periods, yet peak loads still caused long request queues and weak visibility during model iteration.

GPU utilization was only about 5% before the redesign
fault troubleshooting time was reduced by more than 50%
more than 20 branch offices nationwide
resource cost dropped about 90%

Reported impact

Business outcome

Linkedcare cut the cost of running orthodontic AI while improving responsiveness and observability for dental customers. The company no longer has to keep underused GPU fleets online, peak queues are eliminated, and the team can troubleshoot inference problems through built-in logs and alerts instead of waiting for clinics to notice failures.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Linkedcare moved its orthodontic AI inference stack from fixed GPU servers to Alibaba Cloud Function Compute so clinic demand could determine capacity instead of long-lived infrastructure guesses. The team packages the orthodontic model as a standard container image in ACR, and Function Compute pulls that image, attaches GPU resources, and starts the inference runtime only when requests arrive. Pre-reserved GPU instances provide a low-latency floor for real-time use, while elastic scale-out handles demand spikes without keeping large monthly GPU fleets online. The platform also contributes built-in monitoring, logs, and alerts, which matters because the model is under ongoing iteration and failures need to be caught before clinics report them manually. In practice, a front-end dental request triggers GPU-backed inference, returns a result for review, and then lets resources scale back after demand drops.

Data flow

Clinic-facing applications submit orthodontic requests, Function Compute pulls the algorithm image from ACR, attaches GPU resources, runs the inference workload, and returns the diagnostic output. Metrics, logs, and alerts from the same runtime give the team visibility into model behavior and scaling events.

Solution architecture

4 components · 3 layers
  1. Compute
    • Function Compute Runs the orthodontic inference service on demand instead of on permanently provisioned GPU hosts.
    • Reserved GPU instances Provide warm GPU capacity for low-latency inference when real-time requests arrive.
  2. Storage
    • Container Registry (ACR) Stores the standard container image that packages Linkedcare's orthodontic algorithm.
  3. Uncategorized
    • GPU cloud servers Represent the earlier fixed-capacity deployment model that Function Compute replaces.

Architecture clues

  • Linkedcare deploys the AI algorithm as a container image rather than managing long-lived inference VMs directly.
  • Observability is part of the managed runtime, which matters because model iterations can introduce intermittent failures.
  • Reserved GPU instances are used to hide cold-start effects for real-time dental inference.

Evidence from the source

After moving to Function Compute, Linkedcare reported about 90% lower resource cost and said clinics no longer experienced long waiting queues. (original: 相比早前的按月持有 GPU 资源,资源费用降低了 90% 左右... 门店再也没有出现长时间排队的情况。)
Linkedcare said its monthly GPU fleet stayed at only about 5% utilization during normal periods, yet peak loads had caused individual requests to queue for as long as 10 minutes. (original: 平峰期利用率不高,总体资源利用率维持在 5% 左右... 在业务最高峰,曾经出现单个请求排队 10 分钟的情况。)
The new flow packages the orthodontic algorithm into ACR, lets Function Compute initialize GPU instances from that image, and then runs inference on the newly created application. (original: 客户将正畸算法做成标准镜像放入阿里云镜像仓库 ACR... 函数计算通过拉取 ACR 中镜像以及底层 GPU 资源完成实例的初始化工作... 正畸计算请求发送至新创建的 GPU 应用上进行计算。)
Transparency Evidence & methodology 100/100 reference value · 88% 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 value100/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 impact25/25
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence88%
  • 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 evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • 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. Alibaba Cloud

    函数计算助力领健信息为“看牙”注入AI活力_医疗健康_阿里云客户案例

    First-party
    https://www.aliyun.com/customer-stories/health-care-2024-linkedcare
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Published on source page Jun 20, 2024 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.