Multi-tenant orchestration for managed deployments.
⚪ Concept · Scale & Twins cluster · Part of Vela Tools
HYDRA 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.
System integrators and managed service providers don't run one NGSI-LD platform — they run dozens, one per client. Each tenant needs isolation, separate data, separate access control, separate billing — but operating dozens of independent platforms is unsustainable.
HYDRA would be the multi-tenant control plane: provision a new client tenant in minutes, manage them all from one console, isolate data and identity, meter usage. Built for SIs, MSPs, and SaaS-style Vela deployments.
- Tenant provisioning — Spin up a new client deployment in minutes, not weeks.
- Unified console — Operate dozens of tenants from one place. SLA-aware.
- Usage metering — Per-tenant billing data without custom instrumentation.
System integrators, managed service providers, white-label resellers.
⚪ 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 "HYDRA Use Case"
If built, HYDRA would integrate with the rest of the Vela suite as follows:
| For this | Use this |
|---|---|
| Multi-tenant orchestration | HYDRA |
| Per-tenant access control via API gateway | LIBRA |
| Per-tenant resilience and failover | PHOENIX |
| Per-tenant compliance evidence | NORMA |
| Per-tenant digital twins for SI deployments | CARINA |
When (and if) HYDRA 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 HYDRA?
- 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, HYDRA 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.
HYDRA 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.