This software offers a flexible solution for managing and resolving links associated with various identifiers like GTINs (Global Trade Item Numbers).
It enables identity registry operators and identifier owners to register links to more information about a product, while allowing value chain actors to resolve and access information linked to these identifiers across various identifier schemes, enhancing traceability and data accessibility.
- Identifier scheme management (registering and configuring permitted identifier schemes for link registration)
- Link registration and management (allowing registry operators or identifier owners to add and update links to product information)
- Link resolution (enabling value chain actors to access additional information linked to identifiers across various identifier schemes)
- ISO 18975 for link resolution
- RFC 9264 for link sets
- GS1 Digital Link for resolving GS1 identifiers
- Anonymous users can resolve link information without authentication
- Authenticated users via API endpoints can:
- Register and manage identifier schemes
- Register and manage supported link types for identifier schemes
- Register and manage links for specific identifiers within permitted identifier schemes
To quickly set up and run the Identity Resolver using the docker-compose.yaml file, execute the following command:
docker compose up -dFor more detailed setup and configuration options, refer to the documentation site.
Pre-built Docker images are available on GitHub Container Registry. Two variants are provided:
| Image | Use Case |
|---|---|
| Default (no suffix) | Standard deployment, local development |
-serverless |
AWS Lambda / serverless deployments |
Both images support linux/amd64 and linux/arm64 architectures.
# Standard image (default)
docker pull ghcr.io/pyx-industries/pyx-identity-resolver:3.0.0
# Serverless image (Lambda deployment)
docker pull ghcr.io/pyx-industries/pyx-identity-resolver:3.0.0-serverlessFor more details on available tags, see the CI/CD Pipeline page on the documentation site.
We use Semantic Line Breaks in our documentation. Please follow this convention when contributing to the project.
We follow Semantic Versioning with the format MAJOR.MINOR.PATCH.
For the full release process, refer to the Release Process page on the documentation site.