AWS Software / SaaS Austria

MANZ

Enterprise Knowledge Search

MANZ , an Austrian company that provides information services for legal and tax professionals, sought to revolutionize how its registered users searched its vast repository of legal documents.

30% expected savings
50 million documents searched
The solution was designed to handle over 300 million documents efficiently, with the help of AWS products such as Amazon OpenSearch Service and Amazon Neptune .
Through tecRacer's implementation of IaC and fast, reliable data storage, MANZ was able to achieve processing times of 200 – 300 milliseconds to search 50 million documents.

Reported impact

Business outcome

MANZ , an Austrian company that provides information services for legal and tax professionals, sought to revolutionize how its registered users searched its vast repository of legal documents.

  • Productivity Improvement
  • Speed to Market

Solution

MANZ , an Austrian company that provides information services for legal and tax professionals, sought to revolutionize how its registered users searched its vast repository of legal documents. With over 300 million documents in its database, MANZ aimed to implement a cutting-edge solution using vector embeddings to enhance similarity searches and uncover deeper connections between documents. In collaboration with AWS Partner tecRacer Consulting , MANZ developed and successfully deployed a powerful solution, which reduced deployment times and empowered MANZ to independently develop and refine its solution. Opportunity Searching for a Better Strategy for Finding Similar Documents As a high-profile provider of legal information in Austria, MANZ needed a robust system to efficiently and intelligently search through an enormous database of legal documents.

Data flow

MANZ wanted to avoid significant performance issues that can result in prolonged query times, so tecRacer worked closely with them to optimize their infrastructure by: Correctly sizing the OpenSearch cluster: Ensuring that the cluster was appropriately sized to handle large-scale document searches efficiently. Fine-tuning queries: By improving the search query logic and structure, the performance was enhanced significantly. To automate and streamline the deployment process, tecRacer delivered a production-ready setup using Terraform.

Solution architecture

2 components · 2 layers
  1. Storage
    • Amazon Neptune Stores graph relationships used by the knowledge search and question-answering workflows.
  2. Serving
    • Amazon OpenSearch Service Indexes content and powers search or analytics for the knowledge search and question-answering workflows.

Architecture clues

  • A lack of experience in vector databases was the first challenge.
  • Solution Implementing Vector Search Capabilities With a Seasoned AWS Partner MANZ chose tecRacer Consulting, a 2023 AWS System Integrator Partner of the Year, to help the company overcome technical...
  • The switch to Amazon OpenSearch Service and the use of vector search are expected to deliver significant cost savings compared to MANZ's previous search solutions—up to 30 percent in the medium term....
  • While MANZ boasts a seasoned IT team, it had minimal prior experience building or managing a vector database entirely on its own, particularly one capable of handling 50 million documents.
  • With over 300 million documents in its database, MANZ aimed to implement a cutting-edge solution using vector embeddings to enhance similarity searches and uncover deeper connections between...

Evidence from the source

In collaboration with AWS Partner tecRacer Consulting , MANZ developed and successfully deployed a powerful solution, which reduced deployment times and empowered MANZ to independently develop and refine its solution.
Solution Implementing Vector Search Capabilities With a Seasoned AWS Partner MANZ chose tecRacer Consulting, a 2023 AWS System Integrator Partner of the Year, to help the company overcome technical and operational challenges, particularly...
The solution was designed to handle over 300 million documents efficiently, with the help of AWS products such as Amazon OpenSearch Service and Amazon Neptune .
This included automated deployment scripts for Amazon OpenSearch Service and Amazon Neptune Database, along with crucial configurations for backup and security roles.
While MANZ boasts a seasoned IT team, it had minimal prior experience building or managing a vector database entirely on its own, particularly one capable of handling 50 million documents.
With over 300 million documents in its database, MANZ aimed to implement a cutting-edge solution using vector embeddings to enhance similarity searches and uncover deeper connections between documents.
Transparency Evidence & methodology 86/100 reference value · 90% 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 value86/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 specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence90%
  • 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
    6 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • 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. AWS

    MANZ customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/manz-tecracer-consulting/
    Source type
    Vendor-published customer story
    Published
    Feb 14, 2025
    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
  2. German Wikipedia

    Manz AG raw page

    Independent secondary
    https://de.wikipedia.org/w/index.php?title=Manz_AG&action=raw

    The raw infobox states "Mitarbeiterzahl = 1.435 (2023)" and "Stand = 2023-12-31".

    Source type
    Structured reference
    Supports
    • Company size

Date evidence

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