ASAM ODS is valuable because it standardizes how tools access test data—but many enterprises don’t store all data in one place anymore. Alongside classic ODS repositories you’ll often find data lakes and buckets, indexing services, legacy databases, and domain-specific APIs that are better suited for specific workloads.
Janus ODS6 Platform keeps the ASAM ODS toolchain stable while enabling a federated architecture: it can virtualize and unify multiple sources into one ASAM ODS project view without forcing a “store everything twice” approach.
Janus is built around a modular handler architecture. Instead of coupling the ASAM ODS API to a single persistence design, Janus composes a project from independent services—for example identity and access, modeling, mapping, metadata access, mass data access, and file/artifact handling. This enables targeted scaling, module-level isolation, and cloud-native operations.
Designed for enterprise reliability, Janus can be operated in a stateless mode where module restarts don’t break long-running usage patterns, and only the required APIs need to be deployed for a given environment.
AReS Libertas ODS6 Server is the standard ASAM ODS system of record: one governed backend that implements the full ODS API against a conventional metadata + mass data architecture. Janus Test Data Management Platform is a platform layer that virtualizes and federates multiple sources behind a consistent ASAM ODS API—optimized for cloud and enterprise integration..
Use Janus when you need more than one repository, for example:
you must expose multiple silos as one project,
you want hybrid storage (hot/cold, lake/bucket + ODS),
you need cloud-native scaling and modular deployment,
you want to integrate enterprise systems (e.g., PLM) into the same API context,
you want to modernize without a big-bang migration or forced data transformation.
Janus can replace Libertas, run alongside other ODS servers, or act as the federating platform that unifies them.
Janus virtualizes heterogeneous sources—classic ODS repositories, homegrown APIs, and legacy databases (SQL or non-SQL)—into a single ASAM ODS project view using dedicated handler services for mapping and adaptation. This lets teams keep a stable ASAM ODS toolchain without forcing a “transform first” or “store everything twice” approach.
Janus is built for architectures where object storage and data lakes (buckets), Parquet/columnar analytics, and search/index backends coexist with governed ODS systems. It enables hot/cold storage, retention, and scalable analytics while keeping access consistent through the ASAM ODS API—so pipelines and client integrations don’t need rewrites as storage and compute evolve.
Janus can consolidate multiple parallel projects—across domains, sites, or model variants—into a unified project view. It also supports integrating higher-level systems such as PLM so ASAM ODS-based applications can consume that information consistently, with the right governance and context.
Janus is designed to run stateless at the platform layer: requests are handled without relying on long-lived in-memory server sessions. This improves availability because individual modules can be restarted, upgraded, or rescheduled without taking the overall platform offline. It also enables elastic scaling, since additional instances can be added or removed dynamically based on load, without session “stickiness” or fragile failover behavior.
For enterprise and cloud deployments, the result is lower operational cost and more predictable performance: capacity can be scaled on demand, failures are isolated, and rolling updates become routine. Stateless operation also helps avoid session-related bottlenecks and reduces the risk of timeouts in distributed environments—especially when users and tools access the platform across sites or through restricted networks.
Global Enterprise Test Data Management with HighQSoft products and services
In many enterprises, PLM is the “super-system” around testing programs. Janus can virtualize PLM context into the ASAM ODS world so ODS-based applications, automation, and reporting can consume consistent project context without duplicating that information.
Enterprises often operate multiple ODS projects (different domains, models, or generations) plus non-ODS silos. Janus can federate these into a consolidated view—supporting cross-program reporting, global search, and unified downstream workflows.
Janus supports architectures where new data stays in performant storage for fast access, while older or less-used data moves to lower-cost storage. The project remains accessible through the same standardized API, supporting retention and archiving without “losing” the toolchain.
A primary reason to rely on the ASAM ODS API is that the toolchain and the ecosystem built on top may remain stable. Often, ASAM ODS systems integrate with many other systems, have many users with different applications, and analysts develop many scripts, which makes adaptations complicated and labor-intensive. With ASAM ODS, this is resolved.
With ASAM ODS, organizations obtain a neutral and transparent API layer that allows them to choose from various compatible tools and solution providers. This avoids being locked into a single vendor, format, or other and provides flexibility in technology selection.
Adopting standardized interfaces helps organizations remain adaptable to future technology changes, as new tools that comply with these standards can be integrated with minimal disruption. ASAM ODS is widely used and supported in the industry by suppliers and OEMS. The interface is downward compatible. With Janus, HighQSoft also incorporates non-ODS data from legacy sources into the system.
Janus supports containerized deployment to simplify rollout and operations. In orchestrated environments, services can be scaled, deployed, and managed predictably—supporting enterprise-grade availability and growth.
All software provided by HighQSoft can run in cloud environments, including AWS, GCP, Azure, and Alibaba. Janus fits Kubernetes-based operations (including OpenShift). Common cloud storage options can be integrated, and OAuth-based authentication can be used where supported.
HighQSoft GmbH
Black-und-Decker-Straße 17b
D-65510 Idstein
