Go services, PostgreSQL persistence, Docker Compose examples, and documented configuration give teams a pragmatic path from local evaluation to managed rollout.
Eclipse BaSyx Go Components 1.0.0
BaSyx Go for Eclipse BaSyx, AAS and enterprise Digital Twins.
Asset Administration Shell infrastructure for Digital Twin Registry, Dataspace, Catena-X, Manufacturing-X, Tractus-X, security, and auditability.
v1.0.0Release
A 1.0.0 milestone for enterprise AAS infrastructure
From AAS pilots to reusable Eclipse Digital Twin infrastructure.
BaSyx Go packages core Asset Administration Shell services, Digital Product Passport APIs, controlled access, queryable product data, and evidence-oriented history.
The Digital Product Passport is treated as part of the AAS world, so product data can remain reusable across portals, data spaces, and compliance processes.
OIDC, ABAC, audit history, WORM-oriented evidence storage, SBOMs, and signed artifacts support technical controls without claiming automatic compliance.
What arrives with 1.0.0
Eclipse BaSyx components for scalable AAS and DPP use cases.
Open building blocks for Asset Administration Shell repositories, registries, discovery, and Digital Product Passport APIs.
Registries and Discovery
AAS and Submodel registries make digital twins discoverable across products, plants, partners, and data-space scenarios.
Repository services
AAS and Submodel repositories provide the runtime layer for structured product, asset, document, and sustainability data.
Digital Product Passport
The DPP API exposes product pass data as a standards-based view on AAS and Submodels instead of a detached data silo.
AASX exchange
AASX file handling supports exchange scenarios where portable digital twin packages and documentation matter.
Security and audit
OIDC, ABAC, visibility rules, and history functions support controlled access and traceable changes.
Cloud-native operation
PostgreSQL, Docker Compose, Helm-oriented deployment paths, SBOMs, and signatures help evaluation move toward operation.
Why BaSyx Go
Why BaSyx Go for modern Asset Administration Shell platforms.
A pragmatic Eclipse BaSyx runtime with AAS API 3.2, PostgreSQL, ABAC, auditability, SBOMs, and MIT-licensed open-source delivery.
| Capability | BaSyx Go | BaSyx Java |
|---|---|---|
| Query LanguageServer-side search | ||
| Part 4 SecurityScalable access control | ||
| Metamodel VersionCurrent AAS model | 3.2 | 3.1 |
| API VersionNewer service contracts | 3.2 | 3.0 |
| Database TechnologyEstablished persistence | PostgreSQL | MongoDB |
| IDP IndependenceOAuth 2.0 capable IDPs | ||
| SBOMSoftware bill of materials | ||
| WORM StorageTamper-resistant evidence | ||
| AuditabilityTraceable operations | ||
| ABACAttribute-based access | ||
| AAS HistoryHistorical shell data | ||
| Signed DataVerifiable artifacts | ||
| EventingStandard path planned | Planned standardized | Proprietary |
| Full API CoverageIDTA-aligned coverage |
Strategic value
Open, modular and ready to connect across regulatory waves.
For strategic decision makers, open source is not an end in itself. What matters is whether open technology reduces dependencies, lowers integration risk, and supports an architecture that remains viable through NIS2, ESPR, DPP and dataspace requirements.
No vendor lock-in
BaSyx Go is MIT licensed, making evaluation, adaptation, and integration easier without forcing companies early into proprietary platform logic.
Start with a bounded use case
The services cover central AAS runtime functions, while examples shorten the path from technical evaluation to a focused rollout.
Connect security & audit evidence
Release artifacts with SBOMs, provenance, and signatures support traceable operation for teams preparing DPP, NIS2, ESPR, and dataspace scenarios.
Enterprise platform shift
Professional AAS infrastructure for regulated Digital Twin product data.
BaSyx Go helps teams organize product, asset, and security information so it can be found, governed, reused in dataspaces, and audited across product lifecycles.
FoundationAAS runtime servicesRepositories, registries, discovery, and AASX services form a reusable backbone for AAS-based product and asset information.
FindabilityQueryable product dataServer-side query capabilities help applications find relevant shells, descriptors, and submodels without loading the full data set first.
ControlGoverned accessOAuth 2.0 capable identity providers, OIDC, and ABAC align access control with enterprise identity, partner visibility, and audit-sensitive data handling.
Dataspace-ready orientation
Digital Twin Registry and Dataspace-ready BaSyx infrastructure.
Built for discoverable Digital Twins across company boundaries in Catena-X, Manufacturing-X, Tractus-X, and federated dataspace scenarios.
Digital Twin Registry
The Digital Twin Registry combines discovery and registry ideas into an entry point that fits dataspace patterns known from Catena-X and Tractus-X.
Catena-X, Tractus-X, Manufacturing-X
BaSyx Go reflects the need to connect AAS infrastructures across company boundaries without turning every integration into a custom portal.
Company-level discovery
Company Lookup helps partners find the technical entry point to an organization’s AAS infrastructure, not only a single shell.
Digital Product Passport and auditability
Digital Product Passport data as a governed AAS Digital Twin view.
BaSyx Go connects DPP access with AAS and Submodels, while OIDC, ABAC, history, signed artifacts, WORM storage, and SBOMs support enterprise evidence trails.
Security and audit
Technical controls instead of compliance promises.
BaSyx Go supports auditability, integrity, and traceability for AAS and DPP infrastructure. Operating a BaSyx Go stack does not replace NIS2 compliance review, legal assessment, or organizational security processes.
NIS2 changes the discussion around production IT. It is no longer enough to expose interfaces and store data somehow. Companies must assess risks, control access, handle incidents, secure evidence, and operate technical and organizational measures. Fraunhofer IESE provides a broader overview in its article on the NIS2 directive and implementation in Germany .
For BaSyx Go, the technical role is the important part: software can support these requirements, but cannot fulfill them alone. History Evidence can support NIS2-adjacent technical controls by preserving change evidence and integrity signals, but it does not make an operator automatically NIS2 compliant.
Technical building blocks
- OIDC token validation and ABAC authorization
- Data visibility rules down to relevant data areas
- AAS and Submodel history plus recent-change functions
- Optional S3-compatible WORM Evidence Storage
- SBOMs, provenance, and signed release artifacts
Operator responsibilityOrganizational duties remain with the company operating the stack.
- Risk management
- Incident handling
- Backup and recovery
- Key management
- Retention periods
- Monitoring
- Training
- Supply-chain assessment
- Legal review
Learn, evaluate, connect
Follow Eclipse BaSyx, BaSyx Go and the AAS ecosystem.
Use the official project channels for source code, documentation, Eclipse BaSyx context, Digital Twin guidance, and the Fraunhofer IESE release article.
SourceGitHub repository
Source code, examples, releases, issues, and contribution entry point for BaSyx Go Components.
EclipseEclipse BaSyxOfficial Eclipse BaSyx project page for the open-source AAS middleware ecosystem.
Projectbasyx.orgProject website for BaSyx, use cases, background, and ecosystem orientation.
DocsBaSyx WikiDocumentation and operational guidance for BaSyx users and evaluators.
InstituteFraunhofer IESEFraunhofer IESE context for applied research, industrial software engineering, and BaSyx expertise.
BlogRelease articleRelease article covering BaSyx Go 1.0.0, Digital Product Passport, AAS, and auditability.
1.0.0Stable BaSyx Go release for AAS infrastructure
DPPDigital Product Passport API mapped into the AAS world
OIDCIdentity and attribute-based authorization for governed access
SBOMSoftware bills of materials and signed release artifacts
Developer team
The people building BaSyx Go Components for Eclipse BaSyx.
Developers and contributors behind Go-based BaSyx services, AAS integration, enterprise authorization, and release engineering.
Available now