AWS Software / SaaS Taiwan

Riversoft

Enterprise Knowledge Search · Marketing Personalization

Riversoft needed a better way to support semantic travel search and automated travel product matching because its first-generation travel AI delivered slow inference, weak relevance, and too much manual effort when matching traveler requests to packages.

10 higher accuracy to boost customer satisfaction
75% lower costs for hosting llms
Claude 3
Riversoft Reduces Inferencing Time for Smart Travel System by 75% with Generative AI on AWS

Reported impact

Business outcome

Riversoft improved semantic travel search and automated travel product matching with measurable results including Riversoft Reduces Inferencing Time for Smart Travel System by 75% with Generative AI on AWS, reduction in inferencing time, from 20 to 5 seconds, and 75% lower costs for hosting llms, while giving teams a faster path from governed data to production decisions.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

Riversoft uses Serverless compute and Amazon Bedrock to support semantic travel search and automated travel product matching. The implementation replaced a legacy state where its first-generation travel AI delivered slow inference, weak relevance, and too much manual effort when matching traveler requests to packages. Travel catalog content and customer travel queries move through AWS Lambda and land in shared lakehouse datasets, giving teams one trusted data foundation. Central governance keeps access, lineage, and compliance consistent across downstream teams. Serverless compute, Amazon Bedrock, and Amazon SageMaker operationalize models, agents, and analytics that deliver semantic travel matches and itinerary and package recommendations.

Data flow

Travel catalog content and customer travel queries land on a shared platform, pipeline services clean and standardize them, governance controls enforce trusted access, and AI, model-serving, and analytics services deliver semantic travel matches and itinerary and package recommendations.

Solution architecture

4 components · 3 layers
  1. Compute
    • Serverless compute Serverless compute scales bursty data and model workloads behind semantic travel search and automated travel product matching without fixed infrastructure overhead.
    • Amazon SageMaker Amazon SageMaker handles model training, tuning, and deployment workflows for semantic travel search and automated travel product matching.
  2. Serving
    • Amazon Bedrock Amazon Bedrock runs foundation models for summarization, reasoning, and conversational steps inside semantic travel search and automated travel product matching.
  3. Orchestration
    • AWS Lambda AWS Lambda orchestrates low-latency functions and API workflows around semantic travel search and automated travel product matching.

Architecture clues

  • Operational AI workflows are deployed directly beside governed data and analytics assets.
  • Riversoft Reduces Inferencing Time for Smart Travel System by 75% with Generative AI on AWS
  • reduction in inferencing time, from 20 to 5 seconds

Evidence from the source

The support we received from AWS in deploying models on Amazon SageMaker made the learning curve much faster and more efficient than trying to work things out on our own,
We need reliable NER models to help our system identify domain-specific terms or word combinations a customer may type and how those are related to available travel offerings.
We use BERT models for diverse activities such as named entity recognition and document classification,
When we were using our previous AI provider, we couldn’t solve the problem. But when we started testing Claude models on AWS, we realized that Claude’s logical reasoning abilities are stronger.
Transparency Evidence & methodology 100/100 reference value · 87% 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
    5 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • 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
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • 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. AWS

    Riversoft customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/case-study-riversoft
    Source type
    Vendor-published customer story
    Published
    Jul 10, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.