Release

Overview

In Tensor9’s model, a Release represents a versioned deployment of a vendor’s App to customer Appliances. A release captures the current state of the vendor’s Origin Stack and packages it for continuous synchronization with customer environments. Vendors can focus on releasing their software as they normally would, while Tensor9 handles propagating updates across different Form Factors.

Releases ensure that vendors can push updates and fixes seamlessly, with minimal operational overhead, while maintaining alignment with customer requirements for security, privacy, and control.

Key Concepts

Versioned State: Each release corresponds to a specific version of the vendor’s app, including code, configurations, and infrastructure changes.
Continuous Synchronization: Once a release is created, Tensor9 continuously synchronizes the app to all connected appliances, ensuring customer environments stay up-to-date.
Granular Rollouts: Vendors can control when and how releases are applied, either globally or for specific buyers.
Audit-Logged Updates: All updates are logged in the customer’s audit log, providing transparency and traceability.

Release Workflow

Create a Release: The vendor makes changes to their origin stack (e.g., updating the app’s code or configurations) and triggers a release.
Continuous Deployment: Tensor9 propagates the release to connected appliances, adapting the deployment to the customer’s specific form factor (e.g., cloud account, on-prem Kubernetes).
Validation and Monitoring: Vendors can monitor the deployment using the Digital Twin for logs, metrics, and state changes.
Update and Rollback: If an issue is detected, Tensor9 allows vendors to roll back to a previous release version or apply hotfixes as needed.