OLIVE Platform Version 1.1.0
Release Date: 30 Jan 2026
Status: Public Development Release
This page is a record of what changed in OLIVE 1.1.0. It is not documentation for operating 1.1.0.
The rest of this manual documents OLIVE 1.3, and the procedures, values and version tables in it do not apply to 1.1.0. Anything on this page that reads like an instruction — configuration, supported components, environment notes — was true for 1.1.0 at the time and may since have changed.
For the current release see the 1.3.1 release notes, and for the components and versions in it, Platform Technology Overview.
Overview
This release of the OLIVE Platform (v1.1.0) introduces functional enhancements, usability improvements, and infrastructure optimizations.
Connectivity & Workflow Enhancements
Extended connectivity model: Connectivity is no longer limited to sequential execution. Workflows now support control logic such as branches and loops, enabling more expressive and flexible orchestration.
Scheduled execution: Connectivity can now be executed on a schedule, allowing periodic execution of connectable elements.
Platform & Infrastructure Improvements
Object storage migration: The platform now uses SeaweedFS instead of MinIO for object storage. This change was made due to reduced support and feature availability in MinIO’s community edition.
More efficient service invocation: Internal service communication has been optimized, resulting in reduced resource consumption.
Improved diagnostics: Additional diagnostic information is now available to support request-level debugging.
User Experience & Usability
New start page: A centralized start page provides easier navigation between:
- the connectivity editor,
- available templates,
- and instantiated applications.
Editor usability improvements:
- Improved grouping mechanisms
- Visual differentiation of instance types using colors and icons
- Enhanced validation when creating or editing entries
Documentation
Integrated API and type documentation is now included directly within the deployed OLIVE Platform.
Security & Authorization
New “Editor” role: Production deployments now support an additional authorization role.
Only users with Admin or Editor roles can modify connectivity configurations or access sensitive information.
Deprecations
The tenant lifecycle manager prototype has been decommissioned.
Current Status
| Area | Status | Notes |
|---|---|---|
| Core Services | Operational | Core connectivity, orchestration, and template services are available and stable for development use. |
| Microfrontends | Partial Support | The existing microfrontends used in OLIVE use cases are functional. The creation of new microfrontends is supported on a prototypical basis. Future changes are expected, and migrating to them will require manual effort. |
| Security | Not yet reviewed | A formal security audit has not been completed. Use only in isolated, non-production environments. |
| Documentation & Training Material | Available | Comprehensive documentation is provided, including the OLIVE Platform Handbook, and a developer package that includes simple examples and more complex business use case scenarios to support onboarding and practical learning. |
Security & Cost Considerations
Security
No formal security review has been completed. Assume no privacy or confidentiality when using OLIVE over public networks. Avoid deploying in production or connecting to sensitive environments.
Use only in controlled lab or development setups.
Costs
Running OLIVE in pay-as-you-go cloud environments (e.g., AWS, Azure, GCP) may incur compute, storage, and networking charges.
We recommend:
- Setting budget alerts and thresholds
- Regularly monitoring cloud resource consumption
- Reviewing connected third-party service usage
Testing & Environment Notes
| Test Category | Status | Remarks |
|---|---|---|
| Unit & API Tests | Passed | All automated unit and API tests succeeded. |
| Manual Release Tests | Passed | Basic manual validation of functionality completed. |
| Security Tests | Not performed | Security and penetration testing pending. |
| Performance / Load Tests | Not performed | To be included in future releases. |
Intended Use
This release is suitable for development and evaluation purposes.
It allows teams to:
- Explore and understand core OLIVE connectivity concepts
- Experiment with connectivity instance management
- Build and test proof-of-concept integrations
⚠️ Not recommended for production use at this stage.
Service Versions
Core Services
| Service Name | Version |
|---|---|
| cloud-function-registry | 2.0.159 |
| instantiator | 1.0.0 |
| data-orchestrator | 3.2.0 |
| file-storage-service | 1.0.104 |
| import-export | 1.0.24 |
| landing-service | 0.1.0 |
| ui-component-registry | 2.1.0 |
| microfrontend-interpreter | 2.1.0 |
| editor | 3.2.0 |
| repository | 1.2.0 |
| session-memory | 1.0.66 |
| scheduler | 1.0.17 |
| template-data-retriever | 0.0.23 |
Extension Services
| Service Name | Version |
|---|---|
| adoxx-embedder | 1.1.0 |
| agent-caller | 2.0.85 |
| aws-query-caller | 1.0.37 |
| cloud-function-executor | 1.0.41 |
| embed-indexer | 1.0.52 |
| mcp-server-caller | 0.0.48 |
| prompt-caller | 2.0.73 |
| temporal-caller | 0.0.1 |
| transcript-to-txt | 0.0.25 |
| vector-service | 1.0.59 |
| develop-support | 0.0.1 |
QA Services
| Service Name | Version |
|---|---|
| ping | 1.0.64 |
| simple-adder | 1.0.19 |
Infrastructure Charts
| Service Name | Version |
|---|---|
| auth-proxy | 0.2.12 |
| certificate | 1.1.10 |
| couchdb | 1.1.13 |
| keycloak-setup | 1.0.69 |
| seaweedfs | 0.0.21 |
| opensearch | 1.1.13 |
| tenant-setup | 1.0.76 |
| vault-secrets-setup | 1.1.31 |
| workflow-engine-postgres | 0.1.34 |
Third Party Dependency Versions
We tested the platform with these third party infrastructure versions:
| Component | Version |
|---|---|
| RKE2 Version | v1.31.8+rke2r1 |
| Hashicorp Version | hashicorp/vault:1.18.1 |
| Keycloak Version | keycloak:26.2.4 |
| ArgoCD | quay.io/argoproj/argocd:v2.14.2 |
| CloudNativePG (CNPG) operator | 1.27.1 |
With this release a new third party dependency was introduced: the CloudNativePG (CNPG) operator. The CNPG operator is a Kubernetes controller responsible for the lifecycle management of PostgreSQL clusters. OLIVE uses this operator to provision and manage the PostgreSQL database required by the workflow engine.
Please refer to Platform Setup & Deployment Guide — Development deployment for how to install it once in your cluster.
OLIVE 1.1.0 Documentation
The Metamodel documentation is now included in the OLIVE 1.1.0 — Documentation and no longer a separate entry.
The API and type documentation is now hosted inside your deployed OLIVE Platform version 1.1.0 — see also: OLIVE 1.1.0 — Documentation, section TechnicalDocumentation.1.
Guide for Migrating from 1.0.0 to 1.1.0
See: Migration & Upgrade — section Migratingfrom1.0.0to1.1.0.