Alibaba Cloud Software / SaaS Japan

Lightblue Co., Ltd.

Lightblue needed a base model and cloud platform that could support high-quality Japanese-language foundation-model development. Popular public models performed well in English, but the company needed stronger Japanese understanding, scalable training infrastructure, and a path to productize generative AI services.

Reported impact

Business outcome

Alibaba Cloud helped Lightblue ship Japanese-language foundation models and strengthen the technical base for its RAG assistant product. Qwen gave the company a better Japanese starting point than other public alternatives, while the surrounding cloud stack supplied the compute, storage, and availability controls needed to turn model research into a productized service.

  • Customer Experience
  • Scalability
  • Speed to Market

Solution

Lightblue used Alibaba Cloud to build and operate Japanese-language generative AI systems rather than relying on generic chatbot APIs. The company evaluated prominent open models such as Llama 2 and Mistral Large, then chose the open-source edition of Tongyi Qianwen (Qwen) as the base model for its Karasu and Qarasu models because Qwen handled Japanese materially better. Elastic Compute Service provides the scalable compute needed to deploy virtual servers for model and application workloads, Server Load Balancer distributes traffic to keep the service available, and Object Storage Service stores large volumes of unstructured data used across training and product workflows. On top of that stack, Lightblue is improving Lightblue Assistant, a RAG-based SaaS product intended to replace reliance on third-party APIs and eventually support customer-friendly local deployment.

Data flow

Training and application data is stored in OSS, processed on ECS-backed workloads, and routed through Lightblue's Qwen-based model stack. Generated responses are served through load-balanced application endpoints, while Lightblue Assistant layers RAG retrieval on top for downstream enterprise use cases.

Solution architecture

5 components · 3 layers
  1. Compute
    • Tongyi Qianwen (Qwen) Serves as the base model Lightblue fine-tuned to build Japanese-language foundation models.
    • Elastic Compute Service (ECS) Supplies the on-demand compute used to deploy Lightblue virtual-server workloads.
  2. Storage
    • Object Storage Service (OSS) Stores large volumes of unstructured data for model and application workflows.
  3. Serving
    • Server Load Balancer (SLB) Distributes traffic across backend servers to keep the application highly available.
    • Lightblue Assistant Provides the customer-facing RAG application Lightblue is improving on top of its model stack.

Architecture clues

  • Lightblue Assistant is a RAG-based downstream application layered on the same model and data estate.
  • Lightblue used Qwen as a base model for fine-tuning rather than only as an inference API.
  • The cloud design separates compute, load balancing, and object storage so model work and SaaS delivery can scale independently.

Evidence from the source

"Lightblue employed several other Alibaba Cloud solutions," including ECS for scalable virtual servers, SLB for high availability, and OSS for large volumes of unstructured data.
"The support of Alibaba Cloud's Tongyi Qianwen (Qwen) was crucial for the release of its Karasu and Qarasu models around December 2023."
"We chose Qwen because our LLM's accuracy significantly improved when fine-tuned with a base model capable of understanding Japanese."
Transparency Evidence & methodology 71/100 reference value · 77% 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 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 traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 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 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. Alibaba Cloud

    lightblue - Alibaba Cloud

    First-party
    https://www.alibabacloud.com/customers/lightblue
    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
  2. 株式会社Lightblue

    Lightblueについて|Lightblue

    First-party
    https://www.lightblue-tech.com/about/

    The company profile lists "従業員数 37名".

    Source type
    Official company website
    Supports
    • Company size
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.