Talisman Platform Support Policy
Overview
Talisman Platform is committed to providing reliable, effective support for our customers. This policy defines our scope of support, configuration coverage, severity levels, and response and resolution commitments.
Scope of Support
What We Cover
- Talisman Platform Functionality: Assistance with Talisman Platform services, integration flows, and runtime behaviour.
- Talisman Platform Configuration: Guidance on correct configuration and deployment options of the Talisman Platform.
- Talisman Platform Compatibility: Ensuring integrations remain compatible with upstream Apache Camel releases.
- Talisman Platform Diagnostics: Log, trace, and configuration analysis to help identify issues.
What We Do Not Cover
- Code and integration services created by customers.
- Modified images and/or libraries
- Third-party software/drivers
- Uncertified hardware/hypervisors.
- System and network design or architecture consulting.
- Professional services such as consulting or training (available under a separate agreement).
Integration Framework
Talisman Platform builds integration microservices using the upstream Apache Camel framework.
What does “upstream” mean?
“Upstream” refers to the official open-source project of Apache Camel, maintained by the Apache Software Foundation. By relying on upstream rather than a custom fork, Talisman Platform ensures that all integrations remain compatible with the official, community-driven releases of Apache Camel.
- We do not maintain our own fork of Apache Camel.
- This guarantees alignment and compatibility with official releases.
- Customers benefit from continuous improvements, security updates, and long-term sustainability provided by the Apache Camel community.
Our Role as a Liaison
Although we do not fork Apache Camel, Talisman Platform actively collaborates with the Apache Camel community by:
- Reporting issues, tracking resolutions, and sharing feedback directly with the community.
- Making a best-effort commitment to help customers diagnose and resolve Camel-related issues.
- Advocating upstream when fixes or enhancements require contributions to the Apache Camel project.
Upstream Alignment
The upstream Apache Camel community maintains active support (security patches and bug fixes) strictly for the two (2) most recent Long-Term Support (LTS) releases. Because Talisman Platform does not maintain a proprietary fork of Apache Camel:
- Liaison Scope Limit: Talisman Platform’s role as an upstream liaison, along with our ability to escalate issues or obtain upstream fixes, applies exclusively to integrations running on one of the two currently supported Apache Camel LTS versions.
- Customer Migration Responsibility: While Talisman Platform provides tooling and compatibility with supported upstream releases, Customer is solely responsible for migrating, updating, and testing its integration code and Customer-Created Artifacts to remain on an actively supported Apache Camel LTS release. If an issue occurs on an End-of-Life (EOL) or non-LTS Apache Camel version, Customer must upgrade the affected integration to a supported LTS release to receive upstream resolution or continued Support.
Support Terms
- Support is available to customers with an active subscription under the agreed plan.
- Talisman Platform provides defined response times and communication commitments based on severity levels.
- While we commit to responding and managing issues within target times, final resolution may depend on upstream Apache Camel fixes, which are outside Talisman Platform’s direct control. In such cases, Talisman Platform will act as your advocate in the Apache Camel community and provide best-effort tracking and escalation.
Version Lifecycle
- N-1 Version Support Model. Talisman Platform’s Support (including troubleshooting, engineering escalations, bug fixes, and security patches) is strictly limited to the current major release of the Software ("N") and the immediately preceding major release ("N-1") (collectively, the "N-1 Support Model"). Talisman Platform has no obligation to provide Support for any environment running a Software version that falls outside the N-1 Support Model.
- 90-Day Upgrade Window. To maintain uninterrupted Support eligibility, Customer must upgrade all supported environments to a version within the N-1 Support Model within ninety (90) days of Talisman Platform’s general availability release of each new major Software version (the "Upgrade Window"). For the purposes of this policy, a "major Software version" means any release that causes a prior release to fall outside the N-1 Support Model.
- Release Notice & Extensions. Talisman Platform will provide Customer with advance written notice (including via email, release notes, or customer portal) of each new major Software release at least thirty (30) days prior to its general availability, together with applicable upgrade documentation. Where Customer’s demonstrable regulatory requirements or critical technical constraints prevent completing an upgrade within the Upgrade Window, Customer must notify Talisman Platform in writing prior to the expiration of the Upgrade Window, and the parties will agree in good faith on a reasonable extended timeline for Support continuity.
How the N-1 Model and Camel LTS Alignment Work Together
Each major Talisman Platform release is aligned with an upstream Apache Camel LTS release. Because both Talisman Platform (under the N-1 Support Model) and the Apache Camel community support only the two (2) most recent major/LTS releases, active support at any given time covers two versions:
- Current Release (N): e.g., Talisman Platform 26.16.x (based on Apache Camel LTS 4.22.x) — Supported
- Preceding Release (N-1): e.g., Talisman Platform 26.15.x (based on Apache Camel LTS 4.18.x) — Supported
- Older Releases (N-2 and earlier): e.g., Talisman Platform 26.14.x and earlier — End of Life (subject to the 90-Day Upgrade Window following the 26.16.0 release)
Consulting & Training
Talisman Platform Support covers product support only. Consulting and training services (such as solution design, custom development, and enablement workshops) are not included in Support and are available under separate statements of work and fees.
Severity Levels
| Severity | Description | Examples |
|---|---|---|
| High | Major functionality impaired or severe performance degradation; no workaround available. | Critical integration flows failing. |
| Medium | Partial loss of functionality; moderate impact with available workarounds. | Delays in data flow significantly impact development progress. |
| Low | Minor issues, general inquiries, or cosmetic defects with no significant operational impact. | UI cosmetic issue; documentation clarification. |
Response & Resolution
Talisman distinguishes between Response Commitments (time to first response) and Resolution Effort (best-effort work toward resolution; may depend on upstream Apache Camel).
| Severity | First Response | Resolution Effort |
|---|---|---|
| High | 4 business hours | Continuous effort until resolved. If an upstream Apache Camel fix is required, Talisman will advocate and track progress with the community. |
| Medium | 1 business day | Workaround or resolution targeted for the next planned release; may depend on upstream availability. |
| Low | 2 business days | Addressed in a future release or via documentation update. |
Support Availability
| Hours of coverage | Support channel | Number of cases |
|---|---|---|
| Standard business hours | Email and Slack channel | No limit |
Business Hours
Standard Business Hours are 9:00 AM to 6:00 PM (09:00-18:00) Eastern Time (ET).
Business Hours do not include weekends or local public holidays.
Supported Configurations
Talisman Platform is tested and supported in the following environments:
Talisman Server
| Name | Version | |
|---|---|---|
| Operating System | Red Hat Enterprise Linux | 8, 9 |
| Ubuntu Server | 24.04 | |
| Container management | Docker | 27+ |
| Kubernetes | 1.31+ |
Talisman Studio for VS Code
| Name | Version | Status | |
|---|---|---|---|
| Editor | Visual Studio Code | 1.106+ | Supported |
| Operating System | macOS | 14+ | Supported |
| Windows | 10, 11 | Preview | |
| Linux (Ubuntu Desktop) | 24.04 | Preview | |
| Container management | Docker Desktop, with Docker Compose v2 | 27+ | Supported |
| Docker Engine (Linux), with Docker Compose v2 | 27+ | Preview | |
Local Kubernetes: minikube, with kubectl |
1.31+ | Preview | |
Local Kubernetes: k3d, with kubectl |
1.31+ | Supported | |
| Other tools | Git | 2.x | Supported |
| CPU architecture | x86-64, ARM64 (incl. Apple Silicon) | – | Supported |
Preview configurations
Preview configurations are expected to work but are not yet fully tested. Support for them is best effort: issues are accepted and investigated, but severity response times do not apply. Podman is not supported. Studio for VS Code is supported in Microsoft Visual Studio Code only; VS Code–compatible editors (e.g. VSCodium, Cursor) are not supported.
Customer Responsibilities
To enable effective support, customers agree to:
- Provide diagnostic information (logs, configurations, reproduction steps).
- Keep Talisman Platform environments within supported versions (under the N-1 Support Model) and documented configurations.
- Actively migrate and maintain customer-built integrations on one of the two (2) latest upstream Apache Camel LTS releases.
- Acknowledge that some issues may require upstream fixes governed by Apache Camel’s release cycle, which are only issued for currently supported upstream LTS branches.
Exclusions
Notwithstanding anything to the contrary in this Support Services Policy, Talisman Platform is not obligated to provide Support Services to a customer if:
(a) the Supported Software has been changed, modified, or damaged;
(b) the Issue is caused by the customer’s negligence, hardware malfunction, platform or datacenter configuration, network latency, or causes beyond Talisman Platform’s reasonable control;
(c) the Issue is caused by third-party software not licensed through Talisman Platform;
(d) the customer is running a Software version outside the N-1 Support Model (after the applicable 90-day Upgrade Window), has not installed available Maintenance Releases, or is running integrations on an Apache Camel version outside the two (2) latest upstream Apache Camel LTS releases; or
(e) the customer has not paid the subscription fees when due.
Changes to Support Services
Support Services may be updated from time to time at Talisman Platform’s sole discretion, provided that the level of service will not be materially reduced during the customer’s subscription term.