Provisioning and configuration
We establish the environment, apply the deployment configuration and document the operating boundary.
Managed OrdinateDB
Managed OrdinateDB is not a separate edition or a preferred architecture. It is OrdinateDB operated for you, with responsibilities made explicit before the service starts.
We establish the environment, apply the deployment configuration and document the operating boundary.
We plan product upgrades and routine maintenance with an agreed change process and maintenance window.
We watch the service signals defined for the engagement and respond through the agreed operational contact path.
We operate the agreed backup policy and exercise its recovery procedure. The specific retention and recovery objectives belong in the service agreement, not in a generic website promise.
Your streams, models, calculations and visualisations
Who may access the instance and what each role may do
Change approvals and the maintenance windows that affect operations
The decision to continue managed operation or run OrdinateDB yourself
Deployment topology, replication, buffering, backup policy, recovery exercises and change history are the mechanisms. The service scope records which of them apply and how their evidence is reviewed.
Explore the architecture →topology
where instances run and forward
change
what changed, when and by whom
recovery
procedure, exercise and outcome
response
signals, contacts and escalation
Managed operation does not change the software or create a managed-only data format. The same documented interfaces and Parquet-based long-term storage support a move to self-hosted operation without buying a different OrdinateDB edition.
Tell us where OrdinateDB needs to run and which operating responsibilities you want to hand over.