Vela Tools ship in two editions. The FOSS edition is under EUPL 1.2 and published in the vela-context organisation on GitHub. The Pro edition adds clustering, SSO, audit trails, multi-tenancy and premium connectors and is licensed for the contract term.

Who owns what we commission?

You do. Anything built under your contract is released under EUPL 1.2 in your own repository and listed as yours in the IP annex. Vela never develops Pro features on customer money.

Can we export our data at any time?

Yes. Every entity as NGSI-LD, full history as Parquet or CSV, catalogue as DCAT-AP, on any day, at no cost.

Under which terms is the Pro edition licensed?

Under the buyer’s own procurement framework: EVB-IT in Germany, GIBIT 2025 or ARBIT in the Netherlands, with no deviations. A two-page schedule lists the modules, the term and the audit rights.

Does Vela meet GIBIT 2025?

Commissioned software is released under EUPL 1.2 on a public repository, Pro editions are standard software licensed under GIBIT 2025 for the term, and the exit clause and IP annex are in every contract. The buyer’s legal team confirms compliance for its case.

Can Vela be used in a German MPSC-funded project?

Yes, with the FOSS edition and commissioned work under EUPL 1.2, publishable on OpenCoDE. Pro editions cannot be part of an MPSC-funded deliverable.

Which context brokers does Vela support?

Scorpio, Orion-LD and Stellio. All open source. The buyer chooses.

Who operates the system?

In Managed, Vela runs the platform under an SLA. In Hybrid and Sovereign FOSS, the buyer’s team runs it with Vela as the vendor behind them. The buyer always has someone to call.

Where is our data hosted?

In Managed and Cloud Services, in the EU, in a region the buyer chooses, under the buyer’s jurisdiction. Vela is the custodian, never the owner. At the edge, data stays on the buyer’s device or site.

What happens if we leave?

Everything tagged Yours and Open moves with the buyer. Pro editions and Cloud Services end with the contract. Exports made during the term stay the buyer’s. Migration is available as a fixed-price service, or the buyer’s team does it with the public documentation.

VELA TOOLS / DATA PIPELINE

CASSIOPEIA

AVAILABLE

Adaptive pipeline that maps any source to validated NGSI-LD Smart Data Models - automatically.

LICENSE

FOSS · PRO · HUB

STANDARDS

NGSI-LD, SMART DATA MODELS

TYPE

MAPPER + TRANSFORMER

CLUSTER

DATA PIPELINE

THE PROBLEM IT SOLVES

Every sensor vendor, every city department, every data feed speaks a different format.

FOSS: CSV, JSON, GeoJSON, KML/KMZ, XML, ESRI Shapefiles, and GRIB

PRO: everything in FOSS + GTFS, GTFS-RT, GBFS and Excel workbooks.

Without a transformation layer, every new data source means weeks of custom integration code that breaks the moment a vendor updates their feed.

CASSIOPEIA replaces all of that with a single, repeatable pipeline. Map a source once, validate it against ETSI Smart Data Models, and run it continuously - as a CLI batch job, a server-mode stream processor, or a graphical mapping wizard. When sources change, you update a config, not your codebase.

try the foss version on github

WHAT YOU GET

Stop writing custom mappers

Validate at the edge

Run anywhere

TECHNICAL DETAILS

CAPABILITIES

Transforms multiple input formats: CSV, JSON, GeoJSON, GBFS, GTFS, and others.
Outputs NGSI-LD entities in different representation modes (normalized/concise/simplified).
Advanced mapping configuration: templates, conditional logic, nested objects, relationships, list relationships.
Synthetic entities: create referenced entities on-the-fly when source data only contains partial references.
Smart Data Model integration: download/search/list schemas and validate outputs when schemas exist.
Flexible writers: write to files (default) or push directly to a Context Broker via HTTP.

Standard feed shortcuts: pre-built configurations for common GTFS and GBFS entity types.

SCOPE

CASSIOPEIA is a focused mapping engine. It's designed to do one thing well and integrate cleanly with the rest of the Vela suite for everything else:

Mapping, validation, and output → CASSIOPEIA
Real-time context API → a Context Broker (protected by LIBRA)
Schema versioning and registry → LYNX
Workflow orchestration → Node-RED, or your existing orchestrator
Time-series storage and history queries → HOROLOGIUM
Anomaly detection and analytics → CENTAURUS, or your stack

ARCHITECTURE

Inputs
- Source files or feeds: CSV / JSON / GeoJSON / GBFS / GTFS.
- Mapping config files: JSON5 (recommended) or JSON.
Processing
- Applies mapping rules using Tera templates with support for conditionals, filters, and nested navigation.
- Generates entity IDs using dataModel + entityName.
- Performs type transformations (string/int/float/bool/datetime/geo types).
- Optionally validates against Smart Data Model schemas or custom data model schemas.
Outputs
- NGSI-LD entities written as files, or pushed to a Context Broker (--writer-type context-broker --broker-url ...).
- Output representation modes: normalized, concise (default), simplified.
- Null handling: include or skip null values.

OPERATING MODES

Cassiopeia provides five interfaces for different stages of the data integration workflow:

CLI - Command line: Batch jobs, CI/CD, one-off conversions
SERVER - REST + WebSocket: Centralized hub, live data streams
EXPLORER - Terminal (TUI): Schema discovery, model inspection
WIZARD - Terminal (TUI): Interactive mapping creation
CONFIGURATOR - Web browser: Same as Wizard, graphical UI

TECH STACK

Language: Rust, TypeScript
Config format: JSON5/JSON mapping configs
Templating: Tera template engine
Interfaces: CLI (cassiopeia ...) + server mode (cassiopeia server)
Outputs: File writer or Context Broker writer (HTTP)
Validation dependencies: Smart Data Model schemas downloaded by tool command

SCREENSHOTS / UI

Data Model Selection

Attribute Mapping

Save Mapping Configuration

GET STARTED

BUILD FOR DATA ENGINEERS - WORKS WITH: ALL VELA TOOLS

three ways to use cassiopeia

Open core. Pick the path that matches your stage — from free download to fully managed integration.

OPEN SOURCE

FOSS

Free

Self-hosted

GET ON GITHUB

Full mapping engine

Many common input data formats

CLI + TUI mode

Community support

RECOMMENDED

COMMERCIAL

PRO

From €100/month

Per instance

Talk to sales

Everything in FOSS

Web Configurator UI

Support for transit/mobility feeds and

spreadsheet inputs

Priority support, SLA

*Server mode

Commercial licence

FULL SUITE

hub

From €1,999/month

Vela Context Data Hub

Talk to sales

Everything in Pro

Fully managed

Integrated with broker, gateway, starter packs

10h/month consulting included

Pro is for running many transformations as managed infrastructure instead of individual commands. You self-host it on your own machines, the same as the FOSS edition.

*Server mode runs Cassiopeia as a long-lived background service. It manages multiple jobs, schedules them, and exposes an HTTP API to submit, inspect, and control runs. The FOSS scheduler keeps one manifest alive in the foreground; server mode manages a fleet of manifests and tracks their state.

Vela Context Data Hub · ANY FORMAT IN, NGSI-LD OUT · EU OPEN STANDARDS · YOUR INFRASTRUCTURE, YOUR RULES