
# Incident & investigation management

Incident intake, evidence, investigations and corrective actions.

Canonical page: https://launchinyourcloud.com/categories/incident-investigation-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


Incident intake, evidence, investigations and corrective actions.

11 listings.


## ArkCase Enterprise (self-managed)

Configurable case management platform with FOIA and investigative solutions.

- Listing: https://launchinyourcloud.com/directory/arkcase-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Enterprise licensing and module terms require a vendor quote; a separate open-source core edition exists.
- Licensing model: unspecified
- Installation: Arrange the enterprise on-premises deployment to physical or virtual machines in your data center.
- Architecture: Persistent case-management application and integrated document/workflow services.
- Operations: Agree the installation, support, security, storage and upgrade responsibilities for the self-managed deployment.
- Product website: https://www.arkcase.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The Enterprise product page documents on-premises operation and the FOIA guide lists self-managed options. The pricing page emphasizes cloud plans; confirm the contracted deployment and modules.

The vendor distinguishes free Open Source and licensed Enterprise Gold/Platinum tiers. The reviewed sources do not establish the complete license grant for every module in the listed Enterprise FOIA/investigations configuration; do not assume all enterprise code is OSI-licensed.

The Enterprise product explicitly supports physical or virtual machines in the customer data center; classified as servers.


### Category fit

- freedom-of-information: FOIA/public-records solution with request tracking, redaction, workflow and reporting.

- incident-investigation-management: Configurable investigative case workflows and document/task management; not a dedicated industrial safety or EHS module.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/ArkCase/ark_helm_charts (checked 2026-11-12). 


### Cloud deployment evidence

- ArkCase vendor-maintained Helm deployment tested on EKS (aws): https://github.com/ArkCase/ark_helm_charts
  The vendor Helm repository explicitly lists Amazon EKS among its tested Kubernetes environments. It supports licensed Enterprise or Community backing components based on supplied licenses. Confirm the ArkCase Enterprise package, component entitlements, storage, secrets and supported chart/release combination; this is a self-managed stack rather than ArkCase SaaS.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Enterprise capabilities and physical/virtual on-premises deployment: https://www.arkcase.com/product/enterprise/

- FOIA solution: https://www.arkcase.com/solutions/arkcase-foia/

- Current solution guide, deployment and licensing: https://www.arkcase.com/wp-content/uploads/2022/01/ArkCase-FOIA-Solution-v3.pdf

- Edition and license pricing: https://www.arkcase.com/pricing/

- 2026 maintenance: https://www.arkcase.com/release-25-09-02/

### Licensing sources

- https://www.arkcase.com/pricing/

- https://www.arkcase.com/wp-content/uploads/2022/01/ArkCase-FOIA-Solution-v3.pdf

### Infrastructure sources

- https://www.arkcase.com/product/enterprise/


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The Enterprise feature page states SSO and PIV/CAC authentication capabilities. It does not specify protocol or current identity-provider entitlement in that statement; confirm the selected implementation. Scope: ArkCase Enterprise feature statement; not a protocol-compatibility certification. Source: https://www.arkcase.com/product/enterprise/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The current public Enterprise and support material does not establish a release-matched self-managed installation artifact. Historical dependency-specific instructions and the open-source distribution do not establish the complete current Enterprise delivery stack; obtain vendor package and installation instructions. Scope: Current ArkCase Enterprise customer-managed delivery artifact remains unconfirmed. Source: https://www.arkcase.com/about/eula/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Sources checked — unresolved. The EULA assigns hardware and supported-stack obligations to the customer but does not publish quantitative Enterprise production sizing. Obtain application, content repository, database, search, transformation and HA resource requirements for the selected release/workload. Scope: ArkCase Enterprise production capacity remains unconfirmed. Source: https://www.arkcase.com/about/eula/ (reviewed 2026-11-21).

- License pricing: Documented. The vendor EULA defines commercial software/support rights and requires operation on an ArkCase-supported stack, timely updates and customer-provided equipment. Pricing distinguishes named-user and enterprise offerings. Obtain the selected self-managed order and support terms rather than applying a cloud price to every installation. Scope: ArkCase commercial Enterprise software/support framework; order-specific entitlements. Source: https://www.arkcase.com/about/eula/ (reviewed 2026-11-21). Supporting source: Public plan distinctions — https://www.arkcase.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Darktrace Forensic Acquisition and Investigation

Commercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.

- Listing: https://launchinyourcloud.com/directory/cado-response/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: CloudFormation; Terraform
- Architecture: Provider-specific CloudFormation or Terraform application stacks and evidence storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Provider-specific CloudFormation or Terraform application stacks and evidence storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Commercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy (checked 2026-11-19). 


### Cloud deployment evidence

- AWS CloudFormation (aws): https://docs.cadosecurity.com/cado/deploy/aws/cloudformation
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Deploy (azure): https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Deploy (gcp): https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS CloudFormation: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation

- Azure Deploy: https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy

- GCP Deploy: https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy

- Licensing Docs: https://docs.cadosecurity.com/cado/deploy/licenses

- Product Page: https://www.darktrace.com/forensic-acquisition-investigation

- Darktrace News: https://www.darktrace.com/news/darktrace-unveils-automated-forensics-capabilities-in-its-activeai-security-platform

### Licensing sources

- https://docs.cadosecurity.com/cado/deploy/licenses

- https://www.darktrace.com/forensic-acquisition-investigation

### Infrastructure sources

- https://docs.cadosecurity.com/cado/deploy/aws/cloudformation

- https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy

- https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The customer-deployed guide documents an Okta SAML integration, explicitly marked beta, with application callback/audience and email/group mapping. It excludes SaaS deployments and points those to a different identity guide. Validate the selected release, beta suitability, IdP and administrator-group handling. Scope: Darktrace customer-deployed Forensic Acquisition and Investigation; documented beta Okta SAML path. Source: https://docs.cadosecurity.com/cado/manage/users-authentication/sso/okta_saml (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies CloudFormation templates for public/private, existing-VPC and GovCloud deployment, with IAM/network parameters and sales/trial delivery access. Obtain the entitled template and licence, review permissions/TLS/storage, and choose the appropriate account/region topology. Scope: Vendor Cado/Darktrace customer-deployed AWS CloudFormation delivery. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (reviewed 2026-11-21). Deployment artifact: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation. Artifact reference: Current vendor CloudFormation guide reviewed on this date.

- Minimum footprint / sizing: Documented. The CloudFormation guide recommends m5.4xlarge as the enterprise minimum for the main EC2 server. Acquisition/processing workers, evidence volumes, network transfer and standby/recovery resources are additional. This is a vendor main-server recommendation, not a whole-system cost or HA workload guarantee. Scope: Customer-deployed Darktrace/Cado main-server recommendation; worker and evidence capacity separate. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Darktrace Forensic Acquisition and Investigation; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.cadosecurity.com/cado/deploy/licenses (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## FormKiQ Incident and Investigation Management

Manage document-centric intake, investigation, and resolution of incidents, complaints, and regulatory matters with structured workflows and audit trails.

- Listing: https://launchinyourcloud.com/directory/formkiq-incident-investigation-management/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/incident-investigation-management/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- incident-investigation-management: Incident intake, evidence, investigations and corrective actions.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Edition: FormKiQ platform; solution configuration and entitlement must be agreed separately.


### Sources

- Incident and Investigation Management solution: https://formkiq.com/solutions/incident-investigation-management/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://formkiq.com/pricing/

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/incident-investigation-management/

- https://docs.formkiq.com/docs/platform/overview


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Incident and Investigation Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/incident-investigation-management/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Sensitive statements and evidence retain document-level permissions throughout the investigation; closure and control changes require authorised review. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Incident and Investigation Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/incident-investigation-management/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Incident and Investigation Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/incident-investigation-management/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Incident and Investigation Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/incident-investigation-management/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Advanced or Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Incident and Investigation Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/incident-investigation-management/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Sandfly Security

Commercial self-hosted Linux threat-hunting and investigation platform.

- Listing: https://launchinyourcloud.com/directory/sandfly-security/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: VM image
- Architecture: Sandfly application services and database on a customer DigitalOcean Droplet.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://marketplace.digitalocean.com/apps/sandflysecurity
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The reviewed provider package and current upstream major are different versions. Follow the vendor's database-schema upgrade instructions rather than replacing an image blindly. A database search finding no CVEs is not a security-assurance claim.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Sandfly application services and database on a customer DigitalOcean Droplet. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Commercial self-hosted Linux threat-hunting and investigation platform.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/sandflysecurity (checked 2026-11-19). 


### Cloud deployment evidence

- DigitalOcean 1-Click (digitalocean): https://marketplace.digitalocean.com/apps/sandflysecurity
  Sandfly application services and database on a customer DigitalOcean Droplet. The reviewed provider package and current upstream major are different versions. Follow the vendor's database-schema upgrade instructions rather than replacing an image blindly. A database search finding no CVEs is not a security-assurance claim.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- DigitalOcean 1-Click: https://marketplace.digitalocean.com/apps/sandflysecurity

- License & EULA: https://docs.sandflysecurity.com/docs/license-eula

- Docs & v6.0.1: https://docs.sandflysecurity.com/

- Upgrade Notes: https://docs.sandflysecurity.com/docs/upgrade-notes

### Licensing sources

- https://docs.sandflysecurity.com/docs/license-eula

### Infrastructure sources

- https://marketplace.digitalocean.com/apps/sandflysecurity


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The vendor documents SAMLv2 using Redirect requests/Post responses, configured NameID/IdP metadata and optional request signing. SSO requires an upgraded plan. Confirm the purchased entitlement, provider attributes and account/role policy; host scanning credentials are separate. Scope: Current Sandfly application-user SAML; upgraded-plan entitlement. Source: https://docs.sandflysecurity.com/docs/sso-configuration (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Sandfly supplies setup tooling that generates Compose configurations for PostgreSQL, server and scanning nodes. Use the supported Compose v2 path and matching setup/image versions; the vendor distinguishes it from the separate Docker/Podman installation method. Configure TLS, secrets, persistence and backups. Scope: Vendor Sandfly Compose-generated application deployment; supported runtime/tool versions required. Source: https://docs.sandflysecurity.com/docs/sandfly-install-docker-compose (reviewed 2026-11-21). Deployment artifact: https://docs.sandflysecurity.com/docs/sandfly-install-docker-compose. Artifact reference: Current guide updated 2026-11-17.

- Minimum footprint / sizing: Documented. The current guide recommends a dedicated server with at least 8 GB RAM and two CPU cores, plus separate scanning-node capacity (4 GB RAM per node host recommended). Scanned-host count, scan concurrency, database retention and redundancy change requirements; protected endpoints have separate prerequisites. Scope: Sandfly server and scanning-node recommendations; whole estate/HA sizing separate. Source: https://docs.sandflysecurity.com/docs/installation-requirements (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Sandfly Security; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.sandflysecurity.com/docs/license-eula (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAP S/4HANA EHS — Customer-Operated

Customer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.

- Listing: https://launchinyourcloud.com/directory/sap-s4hana-ehs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SAP S/4HANA on-premise licensing; verify EHS component entitlements
- Licensing model: commercial-only
- Installation: Install the licensed SAP S/4HANA on-premise edition and configure the selected EHS components using SAP implementation guides
- Architecture: SAP S/4HANA application stack with SAP HANA database and EHS Fiori applications
- Operations: Customer manages the application and database infrastructure, installation, upgrades, access, backups and EHS configuration; agree implementation and support arrangements.
- Product website: https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The on-premise edition is explicitly customer-installed and customer-operated. This entry covers its EHS components, not SAP-managed Cloud Private Edition or Public Edition. Check the selected release, component entitlements and implementation scope. Environmental reporting still requires configured requirements and reliable source data.

The listed on-premise edition uses SAP commercial software licensing. The official deployment comparison describes its perpetual-license model; the customer agreement defines the exact component rights.

Customer-operated SAP application and HANA database services run on provisioned infrastructure. This is the on-premise edition, separate from SAP-managed cloud services.


### Category fit

- energy-environmental-compliance: Environmental requirements, emissions calculations, compliance scenarios, deviations and reports for environmental authorities.

- incident-investigation-management: Safety incident and near-miss capture, investigations, root-cause classifications and follow-up actions. This is industrial EHS scope, rather than a general legal investigation platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp (checked 2026-11-12). 


### Cloud deployment evidence

- Customer-provided SAP S/4HANA deployment on AWS (aws): https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html
  AWS Launch Wizard provisions customer resources and can install customer-provided SAP S/4HANA software. Evidence covers the underlying S/4HANA platform; confirm EHS licensing, supported sizing, database and SAP release before deployment.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- SAP S/4HANA infrastructure deployment on Azure (azure): https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana
  Microsoft documents S/4HANA infrastructure in a customer Azure subscription. Evidence covers the platform hosting option; confirm EHS modules, SAP licensing, supported operating systems and software installation separately.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- SAP S/4HANA reference architecture on Google Cloud (gcp): https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp
  Google documents S/4HANA on SAP-certified Compute Engine infrastructure. This is platform hosting evidence; EHS functionality, licenses and supported SAP configurations still require confirmation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Customer-operated on-premise installation and operations: https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest

- Environment Management scope: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/1b3596cc5dd5428d887966a4193ddc29/6d08555321d77d77e10000000a441470.html

- Current incident-investigation configuration: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/f5d3e1005efd4e86acf9a65abf428082/96e81bbdc3c54a70b3b374b182bb87c0.html?locale=en-US&version=2025.000

- Commercial model and deployment responsibilities: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Licensing sources

- https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Infrastructure sources

- https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed EHS and deployment material does not establish the selected application UI, release and complete identity configuration. SAP platform authentication options require the actual Fiori/ABAP/GUI entry points and compatible identity components; do not infer a ready EHS federation setup from a generic SAP capability. Scope: Customer-operated S/4HANA EHS identity deployment remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. AWS Launch Wizard can provision SAP landscapes and install customer-provided supported S/4HANA software, including separate multi-instance/HA patterns. Supply licensed installation media and validate supported releases. This is underlying S/4HANA platform automation; EHS activation, business configuration and data migration remain separate. Scope: Provider-documented S/4HANA deployment supporting the EHS parent platform; not a packaged EHS solution. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21). Deployment artifact: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html. Artifact reference: Current AWS Launch Wizard supported SAP deployment guide.

- Minimum footprint / sizing: Sources checked — unresolved. Launch Wizard selects resources from supplied SAP requirements; it does not establish an EHS-specific capacity baseline. Obtain certified S/4HANA/HANA sizing for application/database memory, batch/analytics, data volume and HA rather than interpreting supported maximum memory as a minimum. Scope: S/4HANA EHS workload sizing remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- License pricing: Documented. SAP distinguishes customer-managed S/4HANA on-premise perpetual licensing from subscription-based Private Edition with SAP technical managed services. Do not substitute a cloud subscription for the customer-operated scope; EHS module rights and implementation pricing require the actual agreement. Scope: S/4HANA on-premise deployment model; not a module-specific EHS quote. Source: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5 (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## TheHive Self-Hosted

Self-hosted security incident-response case management for investigations and analyst collaboration.

- Listing: https://launchinyourcloud.com/directory/thehive/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial plans; verify current Community Edition limitations and terms
- Licensing model: commercial-only
- Installation: Docker Compose, packages or Kubernetes installation.
- Architecture: Customer-operated incident-response application and supporting data services
- Operations: Customer manages infrastructure, backup and version upgrades; optional vendor support depends on the plan.
- Product website: https://strangebee.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosted TheHive. Its investigation scope is cybersecurity, so it is an adjacent alternative to broader business-incident workflows. Current licensing and Community use restrictions should be checked before procurement. AWS and Azure offer documented vendor v5 images; the evidence notes identify the applicable release and maintenance policy.

The current listed TheHive product uses vendor license plans and activation. Community is a restricted free non-commercial edition, not the historical open-source release; free availability is not an open-source license grant. This label concerns proprietary licensing, not whether every plan has a fee.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


Deployment qualification: Official current TheHive6 documentation publishes Docker Compose installation instructions and operational requirements. Suitable portable self-hosting, without inferring cloud-account support from vendor-managed cloud marketing. The provider-specific evidence separately covers the vendor v5 AWS image; it does not extend v6 container portability into a cloud-image claim.

### Category fit

- incident-investigation-management: Dedicated cybersecurity incident-response and investigation case platform. Relevant to security cases, tasks and observables; not a general HR, regulatory-complaint or physical-safety investigation product.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.strangebee.com/resources/iaas/aws/thehive/ (checked 2026-11-12). Source: https://aws.amazon.com/marketplace/pp/prodview-gcjij3iscupae (checked 2026-11-12). Source: https://docs.strangebee.com/thehive/installation/release-and-maintenance-policy/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.strangebee.com/thehive/installation/release-and-maintenance-policy/ (checked 2026-11-12). Source: https://docs.strangebee.com/resources/iaas/azure/thehive/ (checked 2026-11-12). 


### Cloud deployment evidence

- StrangeBee official TheHive v5 AMI deployment instructions (aws): https://docs.strangebee.com/resources/iaas/aws/thehive/
  StrangeBee documents the TheHive v5 AMI, EC2 launch, dedicated EBS volumes, initialization and restoration in the customer VPC. This badge covers that version-specific cloud distribution, not a verified TheHive v6 image. Select a maintained release and its current patch, confirm license entitlement, and provide the documented HTTPS reverse proxy or load balancer.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Official TheHive AWS image release and customer licensing scope (aws): https://aws.amazon.com/marketplace/pp/prodview-gcjij3iscupae
  The StrangeBee listing identifies an EC2 AMI, a v5.6.1 image and separately obtained vendor licenses. Infrastructure is launched through the customer AWS account. The displayed image is not proof of the newest patch or of v6 availability; follow the vendor maintenance policy and confirm the image/version before use.
  Source type: marketplace-offer; reviewed: 2026-11-12; vendor support: not-assessed.

- TheHive maintained releases and patch policy (aws, azure): https://docs.strangebee.com/thehive/installation/release-and-maintenance-policy/
  The vendor still maintains the 5.6, 5.7 and 5.8 series as of this review and requires the latest patch within a maintained series. This release policy qualifies the v5 image path; it does not establish a separate provider deployment or certify the displayed marketplace image as fully patched.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- StrangeBee TheHive v5 Azure image deployment (azure): https://docs.strangebee.com/resources/iaas/azure/thehive/
  StrangeBee documents launching its TheHive v5 Azure VM image, attaching the required data disks and initializing or restoring the application, with a Terraform option. This is the same maintained v5 distribution scope as the AWS image path; select a maintained series and current patch, with the required license and HTTPS configuration. It does not establish a v6 image.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker deployment guide: https://docs.strangebee.com/thehive/installation/docker/

- Product and self-hosting overview: https://strangebee.com/thehive-community-edition/

- Current plan and license options: https://strangebee.com/thehive-pricing/

- Licensing and edition terms: https://docs.strangebee.com/thehive/installation/licenses/about-licenses/

- StrangeBee TheHive v5 Azure image deployment: https://docs.strangebee.com/resources/iaas/azure/thehive/

### Licensing sources

- https://docs.strangebee.com/thehive/installation/licenses/about-licenses/

- https://strangebee.com/thehive-community-edition/

### Infrastructure sources

- https://docs.strangebee.com/thehive/installation/docker/

- https://strangebee.com/thehive-community-edition/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. StrangeBee sells an official AWS AMI; the reviewed offer packages TheHive 5.6.1 with Cassandra 4 and Elasticsearch 7. The software license is purchased outside AWS Marketplace, and infrastructure charges are separate. Do not substitute TheHive 6 requirements for this image. Scope: Vendor-published TheHive v5 AMI; not a current-upstream-version or commitment-credit claim. Source: https://aws.amazon.com/marketplace/pp/prodview-gcjij3iscupae (reviewed 2026-11-14). Offer prodview-gcjij3iscupae: StrangeBee; AMI; external software license; package v5.6.1-1; https://aws.amazon.com/marketplace/pp/prodview-gcjij3iscupae.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The current authentication guide requires a paid plan for non-local providers and Platinum or ONE for Active Directory, OAuth2, OpenID and SAML. Configure the selected provider and account lifecycle explicitly; Community/local login does not grant the paid federation options. Scope: Current TheHive user federation; paid Platinum/ONE entitlement. Source: https://docs.strangebee.com/thehive/administration/authentication/configure-authentication/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. StrangeBee publishes Docker Compose production profiles in its deployment repository. These are single-server deployments with supporting services; demo and clustered installations follow separate guides. Scope: TheHive 6 On-prem production Compose profiles. Source: https://docs.strangebee.com/thehive/installation/docker/ (reviewed 2026-11-14). Deployment artifact: https://github.com/StrangeBeeCorp/docker. Artifact reference: repository default branch (moving; select the matching profile/release).

- Minimum footprint / sizing: Documented. Current Docker deployment guidance distinguishes testing at 4 vCPU/8 GB RAM from standard production at 4 vCPU/16 GB and higher-performance production at 8 vCPU/32 GB. Package guidance separately allocates resources to TheHive, Cassandra and Elasticsearch. These profiles need workload/storage and cluster validation rather than representing every release or HA topology. Scope: Current TheHive 6 documentation profiles; not a version-5 or reference-workload capacity guarantee. Source: https://docs.strangebee.com/thehive/installation/system-requirements/ (reviewed 2026-11-21).

- License pricing: Documented. The vendor offers annual paid subscriptions with plan-specific authentication/support features and a separate Community licence with limits. Obtain the selected self-hosted plan, users/organisations, renewal and support terms; SaaS hosting and infrastructure are separate considerations. Scope: Current commercial self-hosted plans versus Community licensing. Source: https://strangebee.com/thehive-pricing/ (reviewed 2026-11-21). Supporting source: Licence framework — https://docs.strangebee.com/thehive/installation/licenses/about-licenses/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Timesketch

Open-source collaborative forensic timeline analysis application.

- Listing: https://launchinyourcloud.com/directory/timesketch/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: gcp, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Helm / Kubernetes operator; Kubernetes manifests; VM image
- Architecture: Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/google/timesketch
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Open-source collaborative forensic timeline analysis application.

### Deployment boundaries


- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://google.github.io/osdfir-infrastructure/docs/getting-started.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://secureanycloud.com/stacks/timesketch/ (checked 2026-11-19). 


### Cloud deployment evidence

- OSDFIR Getting Started (gcp): https://google.github.io/osdfir-infrastructure/docs/getting-started.html
  Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- SecureAnyCloud Azure (azure): https://secureanycloud.com/stacks/timesketch/
  Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes berggren, kiddinn, jaegeral, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/google/timesketch/graphs/contributors

- Upstream project: https://github.com/google/timesketch

### Sources

- OSDFIR Getting Started: https://google.github.io/osdfir-infrastructure/docs/getting-started.html

- SecureAnyCloud Azure: https://secureanycloud.com/stacks/timesketch/

- OSDFIR Timesketch: https://google.github.io/osdfir-infrastructure/charts/timesketch/

- Apache-2.0: https://github.com/google/timesketch/blob/master/LICENSE

- Releases: https://github.com/google/timesketch/releases

### Licensing sources

- https://github.com/google/timesketch/blob/master/LICENSE

### Infrastructure sources

- https://google.github.io/osdfir-infrastructure/docs/getting-started.html

- https://secureanycloud.com/stacks/timesketch/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The versioned configuration supports trusted web-server REMOTE_USER SSO and separately Google OIDC/Cloud IAP options, with actual token/authentication implementation. Configure the selected mode, trusted proxy boundary, identity claims and group policy; these mechanisms are not interchangeable and must not trust spoofed headers. Scope: Timesketch 20261014 configured user SSO/OIDC/IAP paths. Source: https://github.com/google/timesketch/blob/20261014/data/timesketch.conf (reviewed 2026-11-21). Supporting source: Google token validation — https://github.com/google/timesketch/blob/20261014/timesketch/lib/google_auth.py. Supporting source: Application authentication views — https://github.com/google/timesketch/blob/20261014/timesketch/views/auth.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Google maintains OSDFIR Helm charts with Timesketch values and production installation guidance. Select compatible chart/application/OpenSearch versions, expose ingress deliberately and configure secrets, persistent storage and backups. Local Minikube instructions and default port-forward access are not production deployment. Scope: Maintainer Timesketch Kubernetes/Helm deployment; chart and application versions separate. Source: https://google.github.io/osdfir-infrastructure/charts/timesketch/ (reviewed 2026-11-21). Deployment artifact: https://google.github.io/osdfir-infrastructure/charts/timesketch/. Artifact reference: Current OSDFIR Timesketch chart guide reviewed on this date.

- Minimum footprint / sizing: Documented. The upstream scaling guide gives at least 8 GB RAM for its described Ubuntu environment and stresses fast local storage and OpenSearch sizing/shard limits. This is an entry baseline, not capacity for arbitrary timelines/events or an HA cluster; separately size indexes, imports, workers, replicas and backups. Scope: Timesketch published entry baseline and search-scaling guidance. Source: https://timesketch.org/guides/admin/scaling-and-limits/ (reviewed 2026-11-21).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Timesketch; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/google/timesketch/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 20261014 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Timesketch upstream application; verify compatibility with the selected package. Source: https://github.com/google/timesketch/releases/tag/20261014 (reviewed 2026-11-19).







## Tines

Commercial self-hosted automation platform with an AWS Fargate deployment guide.

- Listing: https://launchinyourcloud.com/directory/tines-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Docker / Compose
- Architecture: Licensed Tines application containers and persistent backing services in customer AWS.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.tines.com/stories/docs/self-hosted/deploying-tines/aws-fargate/deployment-guide/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The self-hosted distribution and its release notes are separate from a hosted self-serve subscription. Confirm the customer's eligible self-hosting agreement and external integration access; platform hosting does not move connected services into the same account.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Licensed Tines application containers and persistent backing services in customer AWS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Commercial self-hosted automation platform with an AWS Fargate deployment guide.

- workflow-automation: Commercial self-hosted automation platform with an AWS Fargate deployment guide.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.tines.com/stories/docs/self-hosted/deploying-tines/aws-fargate/deployment-guide/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Fargate Guide (aws): https://www.tines.com/stories/docs/self-hosted/deploying-tines/aws-fargate/deployment-guide/
  Licensed Tines application containers and persistent backing services in customer AWS. The self-hosted distribution and its release notes are separate from a hosted self-serve subscription. Confirm the customer's eligible self-hosting agreement and external integration access; platform hosting does not move connected services into the same account.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Fargate Guide: https://www.tines.com/stories/docs/self-hosted/deploying-tines/aws-fargate/deployment-guide/

- Subscription Terms: https://www.tines.com/self-serve-subscription-terms/

- Release Notes: https://www.tines.com/stories/docs/self-hosted/release-notes/

### Licensing sources

- https://www.tines.com/self-serve-subscription-terms/

### Infrastructure sources

- https://www.tines.com/stories/docs/self-hosted/deploying-tines/aws-fargate/deployment-guide/


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted reference architecture explicitly supports SAML 2.0 and OIDC user sign-in through a customer-owned IdP reachable over HTTPS. The tenant guide explains configuration and notes that login alone does not provision users; invitations or automated provisioning are separate. Scope: Tines Stories self-hosted tenant user login; selected self-hosted subscription still requires agreement. Source: https://www.tines.com/stories/docs/self-hosted/reference-architecture/system-overview/ (reviewed 2026-11-20). Supporting source: Tenant SAML and OIDC configuration — https://www.tines.com/stories/docs/admin/single-sign-on/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official guides provide Helm installation with customer configuration and AWS Fargate deployment using CLI task definitions, private images and environment files. Provision PostgreSQL, Redis, networking, secrets and licensed optional components separately; select compatible chart/application versions. Scope: Customer-operated licensed Tines Stories installation; Fargate guide is a CLI recipe, not a supplied CloudFormation stack. Source: https://www.tines.com/stories/docs/self-hosted/deploying-tines/deploying-tines-with-helm/ (reviewed 2026-11-20). Supporting source: AWS Fargate deployment guide — https://www.tines.com/stories/docs/self-hosted/deploying-tines/aws-fargate/deployment-guide/.

- Minimum footprint / sizing: Documented. The Fargate example allocates 1 vCPU and 3072 MiB to each app and background-worker task; its command-runner example uses 2 vCPU and 2048 MiB. PostgreSQL, Redis, load balancer and replica counts are additional. These are sample task settings, not vendor-certified minimums or a complete HA system size. Scope: Example Fargate task allocations; workload, retention and availability require a separate sizing plan. Source: https://www.tines.com/stories/docs/self-hosted/deploying-tines/aws-fargate/deployment-guide/ (reviewed 2026-11-20).

- License pricing: Documented. The public self-hosted addendum grants use during the subscription term under the specific Order Form and provides the required licence key/file after execution. This establishes separate self-hosted commercial terms; the applicable order must still confirm price, usage limits and support rights. Scope: Public self-hosted subscription framework, not a negotiated quote or automatic applicability of self-serve SaaS terms. Source: https://www.tines.com/self-hosted-software-addendum-feb-2024 (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Tracecat Self-Hosted

Open-source security-workflow automation with an upstream customer AWS deployment.

- Listing: https://launchinyourcloud.com/directory/tracecat/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform; Docker / Compose
- Architecture: Tracecat services, Temporal, RDS and protected secrets on ECS Fargate.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://tracecat.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The deployment's default same-account AssumeRole deny is an intentional security boundary; follow the documented scoped trust/ExternalId design before changing it. Connected tools, agents and enterprise features have separate access and entitlement boundaries.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Tracecat services, Temporal, RDS and protected secrets on ECS Fargate. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Open-source security-workflow automation with an upstream customer AWS deployment.

- workflow-automation: Open-source security-workflow automation with an upstream customer AWS deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tracecat.com/self-hosting/aws-fargate (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Fargate Guide (aws): https://docs.tracecat.com/self-hosting/aws-fargate
  Tracecat services, Temporal, RDS and protected secrets on ECS Fargate. The deployment's default same-account AssumeRole deny is an intentional security boundary; follow the documented scoped trust/ExternalId design before changing it. Connected tools, agents and enterprise features have separate access and entitlement boundaries.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes daryllimyt, topher-lo, jordan-umusu, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/TracecatHQ/tracecat/graphs/contributors

- Upstream project: https://github.com/TracecatHQ/tracecat

### Sources

- AWS Fargate Guide: https://docs.tracecat.com/self-hosting/aws-fargate

- Fargate Terraform: https://github.com/TracecatHQ/tracecat/tree/main/deployments/fargate

- AGPL-3.0: https://github.com/TracecatHQ/tracecat/blob/main/LICENSE

- Releases: https://github.com/TracecatHQ/tracecat/releases

### Licensing sources

- https://github.com/TracecatHQ/tracecat/blob/main/LICENSE

### Infrastructure sources

- https://docs.tracecat.com/self-hosting/aws-fargate


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted SAML guide configures the authentication mode, IdP metadata, callback and attribute mapping. It requires both signed assertions and signed responses, and distinguishes existing membership/invitations from limited first-user bootstrap provisioning. Scope: Documented self-hosted platform-user SAML path; not OAuth credentials used by workflow integrations. Source: https://docs.tracecat.com/authentication/saml (reviewed 2026-11-20). Supporting source: Self-hosted Fargate authentication defaults — https://docs.tracecat.com/self-hosting/aws-fargate.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for Tracecat services, Temporal, RDS and protected secrets on ECS Fargate. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Tracecat Self-Hosted deployment example; review the full linked installation instructions. Source: https://github.com/TracecatHQ/tracecat/tree/main/deployments/fargate (reviewed 2026-11-19). Deployment artifact: https://github.com/TracecatHQ/tracecat/tree/main/deployments/fargate. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The Compose scaling guide gives an approximate default host total of 8 vCPU and 16 GiB RAM, including application services, Temporal, two PostgreSQL instances, Redis and MinIO. Its higher-throughput tiers use measured reference actions and separate executor replicas; benchmark throughput must be remeasured for the actual workflows. Scope: Docker Compose reference sizing, not Fargate task sizing or a 100-user/1-TB HA guarantee. Source: https://docs.tracecat.com/self-hosting/scaling (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Tracecat Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/TracecatHQ/tracecat/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 1.5.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Tracecat Self-Hosted upstream application; verify compatibility with the selected package. Source: https://github.com/TracecatHQ/tracecat/releases/tag/1.5.1 (reviewed 2026-11-19).







## Velociraptor

Open-source endpoint digital forensics and cyber incident response platform.

- Listing: https://launchinyourcloud.com/directory/velociraptor/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL version 3; distinguish the open-source server from Rapid7-hosted integrations.
- Licensing model: open-source
- Installation: Deploy your own Velociraptor server and managed endpoint clients using the production deployment guide.
- Architecture: Persistent server coordinating endpoint agents and collected forensic data.
- Operations: Manage server/client updates, authentication, certificates, storage, endpoint permissions and evidence access.
- Product website: https://docs.velociraptor.app/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The production guide distinguishes hardened ongoing deployments from short-lived quickstarts and separate Rapid7 Insight integrations.

The listed self-hosted project is AGPLv3. Rapid7 Insight platform integrations are a separate deployment/product scope.

The recommended ongoing deployment operates a persistent server with endpoint clients; classified as servers.


### Category fit

- incident-investigation-management: Cyber incident investigation through endpoint evidence collection, forensic analysis and response; an adjacent security tool, not industrial EHS case management.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.velociraptor.app/docs/deployment/resources/ (checked 2026-11-12). 


### Cloud deployment evidence

- Velociraptor server deployment and performance on AWS (aws): https://docs.velociraptor.app/docs/deployment/resources/
  The project describes its Velociraptor server deployments on AWS EC2 and provides workload observations. This establishes a server hosting path, not a sizing guarantee; choose current instances and configure TLS, access controls, datastore protection and capacity for the actual endpoint workload.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The project announced version 0.77.3 on October 5, 2026. Its official project statement records Rapid7 acquisition and stewardship of the open-source technology/community.

Reviewed 2026-11-10.

- 2026 maintenance: https://docs.velociraptor.app/announcements/

- Rapid7 stewardship: https://docs.velociraptor.app/blog/2021/2021-04-21-the-next-phase-of-velociraptor-bf696c2c3491/

### Sources

- Endpoint forensics and response capabilities: https://docs.velociraptor.app/docs/overview/

- Own-server deployment: https://docs.velociraptor.app/docs/deployment/server/

- Deployment scope: https://docs.velociraptor.app/docs/deployment/

- AGPL license: https://github.com/Velocidex/velociraptor/blob/master/LICENSE

- Current releases: https://docs.velociraptor.app/announcements/

### Licensing sources

- https://github.com/Velocidex/velociraptor/blob/master/LICENSE

- https://docs.velociraptor.app/docs/deployment/

### Infrastructure sources

- https://docs.velociraptor.app/docs/deployment/server/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The server deployment guide documents SSO providers for GUI login and recommends SSO for long-lived deployments. DNS, trusted TLS and authenticator configuration are required; the self-signed Basic-auth quickstart is separate. Scope: Velociraptor server GUI authentication. Source: https://docs.velociraptor.app/docs/deployment/server/key_concepts/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The current deployment example generates server/client configuration with the upstream binary and config wizard. Choose the supported Linux server, DNS/TLS and identity mode; the self-signed Basic-auth quickstart is for short-lived private evaluation. Scope: Server binary/configuration workflow, not a generic production Docker image. Source: https://docs.velociraptor.app/docs/deployment/server/deployment_example/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The quickstart suggests an 8 GB server for at least 1,000 clients as a limited-deployment starting point. Collections, concurrency and storage affect capacity; this is guidance, not a universal minimum or benchmark. Scope: Vendor quickstart capacity guidance; not a measured production SLA. Source: https://docs.velociraptor.app/docs/deployment/quickstart/ (reviewed 2026-11-14).

- License pricing: Documented. The v0.77.3 source is GNU AGPLv3 licensed. Dependency notices, commercial services, deployment support and any separately licensed integrations require their own review; no managed-service entitlement follows from the core licence. Scope: Versioned Velociraptor core source licence. Source: https://github.com/Velocidex/velociraptor/blob/v0.77.3/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v0.77.3, published 2026-10-05. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream Velocidex/velociraptor release record; commercial editions and deployment packages may differ. Source: https://github.com/Velocidex/velociraptor/releases/tag/v0.77.3 (reviewed 2026-11-14).







## VIDIZMO Digital Evidence Management

Commercial digital-evidence and redaction platform with customer-account AWS and Azure deployments.

- Listing: https://launchinyourcloud.com/directory/vidizmo-dems/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: AWS Marketplace CloudFormation/VM deployment or documented Azure deployment
- Architecture: Customer application VMs, SQL database, object storage and deployment templates.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://marketplace.microsoft.com/en-us/product/vidizmo.az-ama-vidizmo-dems
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This profile covers the documented Digital Evidence Management system and its licensed redaction workflows. A standalone Redactor entitlement is not inferred from a DEMS Marketplace offer. Review optional AI services, activation and managed-service terms separately from the customer-operated application.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Customer application VMs, SQL database, object storage and deployment templates. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Commercial digital-evidence and redaction platform with customer-account AWS and Azure deployments.

- freedom-of-information: Commercial digital-evidence and redaction platform with customer-account AWS and Azure deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20setup%20VIDIZMO%20Digital%20Evidence%20Management%20Virtual%20Machine%20on%20Azure%20Marketplace/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Cloud Guide (aws): https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/
  Customer application VMs, SQL database, object storage and deployment templates. This profile covers the documented Digital Evidence Management system and its licensed redaction workflows. A standalone Redactor entitlement is not inferred from a DEMS Marketplace offer. Review optional AI services, activation and managed-service terms separately from the customer-operated application.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure VM Setup (azure): https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20setup%20VIDIZMO%20Digital%20Evidence%20Management%20Virtual%20Machine%20on%20Azure%20Marketplace/
  Customer application VMs, SQL database, object storage and deployment templates. This profile covers the documented Digital Evidence Management system and its licensed redaction workflows. A standalone Redactor entitlement is not inferred from a DEMS Marketplace offer. Review optional AI services, activation and managed-service terms separately from the customer-operated application.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Cloud Guide: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/

- Azure VM Setup: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20setup%20VIDIZMO%20Digital%20Evidence%20Management%20Virtual%20Machine%20on%20Azure%20Marketplace/

- Azure Marketplace DEMS: https://marketplace.microsoft.com/en-us/product/vidizmo.az-ama-vidizmo-dems

- AWS Marketplace Guide: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20purchase%20VIDIZMO%20App%20on%20AWS%20Marketplace/

- FOIA Redaction: https://redactor.ai/use-cases/foia-public-records-redaction-software

- VIDIZMO SSA (BYOC): https://vidizmo.ai/subscription-service-agreement

- License Activation: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Installation%20and%20Configuration/VIDIZMO%20License%20Activation/

- Release Notes 12.3.368: https://help.vidizmo.ai/docs/Release%20Notes/Version%2012.3/Release%20Notes%2012.3.368/

- Press Releases RSS: https://vidizmo.ai/press-releases/rss.xml

### Licensing sources

- https://vidizmo.ai/subscription-service-agreement

- https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Installation%20and%20Configuration/VIDIZMO%20License%20Activation/

### Infrastructure sources

- https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/

- https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/How%20to%20setup%20VIDIZMO%20Digital%20Evidence%20Management%20Virtual%20Machine%20on%20Azure%20Marketplace/


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription AzureApplication offer from VIDIZMO LLC. The publisher package and upstream application have separate maintenance. Scope: VIDIZMO Digital Evidence Management selected Azure public offer. Source: https://catalogapi.azure.com/offers/vidizmo.az-ama-vidizmo-dems?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer vidizmo.az-ama-vidizmo-dems: VIDIZMO LLC; Azure application; https://marketplace.microsoft.com/en-us/product/vidizmo.az-ama-vidizmo-dems.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: vidizmo.az-ama-vidizmo-dems public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/vidizmo.az-ama-vidizmo-dems?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Documented. The vendor provides a portal SAML-P setup with Microsoft Entra/Azure and an application IdP, metadata/certificate and callback configuration. Configure the selected DEMS portal, users and entitlement; mailbox OAuth, host login and vendor workforce authentication are separate identity surfaces. Scope: VIDIZMO portal-user SAML-P deployment configuration. Source: https://help.vidizmo.ai/docs/Integration%20and%20Customization/SAML-P/How%20to%20Setup%20SAMLP%20SSO%20using%20Azure/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The AWS deployment guide describes application infrastructure and Marketplace delivery with separately configured application/database/processing services. Supply the appropriate VIDIZMO licence and release, configure network/storage and activation, and validate the chosen topology rather than treating one VM as the full production system. Scope: Vendor VIDIZMO AWS deployment procedure; DEMS licence and service configuration required. Source: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/ (reviewed 2026-11-21). Deployment artifact: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Deployment%20Options/Deployment%20of%20VIDIZMO%20in%20AWS%20Cloud/. Artifact reference: Current vendor AWS deployment guide.

- Minimum footprint / sizing: Documented. The prerequisite guide separates server roles: database minimum 8 cores/32 GB RAM with 150-GB OS and 256-GB data disks; application minimum 4 cores/16 GB with 150-GB OS and 100-GB data disks. Encoding, AI, broker/cache and storage roles are additional. These per-role minimums do not size a complete HA video/evidence workload. Scope: Current VIDIZMO role-specific minimums; full-system and workload capacity separate. Source: https://help.vidizmo.ai/docs/Deployment%20and%20Maintenance/Installation%20and%20Configuration/Prerequisites%20for%20VIDIZMO%20Application/ (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: VIDIZMO Digital Evidence Management; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://vidizmo.ai/subscription-service-agreement (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






