
# Tines

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

Canonical page: https://launchinyourcloud.com/directory/tines-self-hosted/
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.


1 listing.


## 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.






