Centralized data modeling and Smart Data Model versioning.
⚪ Concept · Data Pipeline cluster · Part of Vela Tools
LYNX is an idea — a concept-stage Vela Tool that hasn't started development yet. This repository exists to gather demand signals, use cases, and feedback from the community before any code is written.
If this tool would solve a problem you have, vote and share your use case at velacontext.com/vela-tools. Tools with the most demand get built next.
Smart Data Models change. Vendors extend them, projects fork them, teams invent local variants. Without a registry, every tool that consumes models — CASSIOPEIA, the broker, validators, downstream apps — ends up with a slightly different version of the truth. Schema drift becomes invisible until something breaks in production.
LYNX would be the central registry where Smart Data Models live, version, and evolve. One source of truth that every other Vela Tool reads from.
- Single registry — All Smart Data Models in one versioned home.
- Track drift — See when a model diverges across projects or vendors.
- Feed every tool — CASSIOPEIA, the broker, validators — all read from LYNX.
Data architects, schema owners, integration leads managing more than one project.
⚪ Concept stage. No development yet.
This repository serves as the official home for the concept — README, license placeholder, and issue tracking are live. Source code, documentation, and releases follow only after demand justifies development.
To prioritize this tool above others in the Vela Tools roadmap, vote on the product page or share your use case.
→ Vote and share use case: velacontext.com/vela-tools → Email: info@velacontext.com — subject "LYNX Use Case"
If built, LYNX would integrate with the rest of the Vela suite as follows:
| For this | Use this |
|---|---|
| Schema registry and versioning | LYNX |
| Data ingestion and transformation | CASSIOPEIA |
| Real-time context API | a Context Broker (protected by LIBRA) |
| Semantic governance and SHACL validation | FORNAX |
| Open data publication based on registered schemas | PYXIS |
When (and if) LYNX is built, it will follow the same open-core model as other Vela Tools:
| Edition | What it is | Where |
|---|---|---|
| FOSS | Free, self-hosted, EUPL v1.2 | This repository (post-development) |
| Pro | Commercial license — advanced features, priority support, SLA | velacontext.com |
| Hub | Fully managed as part of Vela Context Data Hub | velacontext.com |
Final feature splits between FOSS and Pro will be announced ahead of development start.
In the concept stage, the most valuable contribution is demand signal:
- Vote for this tool at velacontext.com/vela-tools
- Share your use case — what would you build with LYNX?
- Suggest improvements to the concept — open a feature request
When development begins, see CONTRIBUTING.md for the full code contribution process. All contributions will require a Developer Certificate of Origin (DCO) sign-off (git commit -s).
- Issues: GitHub Issues — for concept feedback and use case discussions
- Discussions: GitHub Discussions
- Newsletter: velacontext.com/newsletter — get notified when development begins
- General contact: info@velacontext.com
- Security: security@velacontext.com (see SECURITY.md)
When built, LYNX FOSS edition will be licensed under the European Union Public Licence v1.2 (EUPL-1.2) — an OSI-approved, EU-developed open-source license available in 23 EU languages.
LYNX is part of Vela Tools — open-core infrastructure for the NGSI-LD ecosystem, built by SenLab d.o.o. in Ljubljana, Slovenia 🇸🇮.
Learn more at velacontext.com.