Technology foundation
The commercial distribution of the open BaseTwin digital twin foundation, with what operations need added: API gateway, authentication, observability, backup and restore, and an audit trail. Deploy it on premises or in the cloud.
Core and Enterprise
The digital twin features themselves are in the open core, BaseTwin. BaseTwin Enterprise depends on released versions of the core and extends it through its public extension points only. It never forks or patches the core, so core updates carry over as they are.
Open core · Apache License 2.0
The digital twin foundation, made of a data space tier and a twin tier.
Commercial distribution
The setup and the extensions for running the core in production.
Components
Instead of selecting and wiring the parts yourself, you deploy a setup that has been verified to work together.
Apache APISIX
One entry point from outside. Internal endpoints are not exposed.
OpenID Connect · Keycloak
Use the bundled Keycloak, or connect the identity provider your organisation already has.
OpenTelemetry · Prometheus · Grafana
Traces and metrics for job duration, store latency, API responses, plugin failures and the freshness of each dataset.
PostgreSQL PITR · object storage
Databases are restored to a point in time from continuous archiving, and object storage is protected by versioning. The restore order is a written procedure, and a restore test runs it automatically.
Structured log
Each operation on the platform is recorded as one machine-readable entry.
Pinned to a core version
Each release is pinned to one version of the core. The whole stack, the restore procedure and the Kubernetes setup are checked on a regular schedule.
Deployment
BaseTwin itself holds no state: the data lives in a database, object storage and a context broker. You can run these as part of the bundled setup, or connect the managed services you already have.
On one server
For evaluation and small installations. One command starts the whole stack, gateway and authentication included.
Everything bundled
A Helm chart installs the database (PostgreSQL/PostGIS), the NGSI-LD broker, object storage, authentication and the gateway.
Connects to managed services
Nothing stateful is bundled. It connects to managed PostgreSQL, S3-compatible storage, Redis, and your existing broker and identity provider.
In every form you choose between the data space tier alone (catalog, terms of use, provenance) and the setup that includes the twin tier.
Roadmap
The following features are planned. They are not part of the current release.
Planned
Workspaces assigned to several NGSI-LD brokers, so that an installation can grow with its load.
Planned
Job execution for large volumes, with retries and a place for failed jobs.
Planned
Provision workspaces, set usage limits and query the audit trail, through an API and console pages.
Planned
Usage aggregated per workspace, exported in a form usable for billing and cost allocation.
In use
BaseTwin Enterprise is what cyberkukan's own services run on. The same setup can be deployed as the base of your urban data platform or digital twin.
Contact us about the setup, the connection to your existing systems and licensing. Using BaseTwin Enterprise requires an agreement with us.
Product names are trademarks or registered trademarks of their respective owners. Our implementation follows the published specifications and is not officially certified by the respective bodies.