Tines
Commercial self-hosted automation platform with an AWS Fargate deployment guide.
3 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Docker / Compose
Runs in
Documented customer environment
Licensed Tines application containers and persistent backing services in customer AWS.
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
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.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
AWS Fargate Guide ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Docker / Compose |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
| License | Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Tines Stories self-hosted tenant user login; selected self-hosted subscription still requires agreement · Source ↗ · Tenant SAML and OIDC configuration ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Customer-operated licensed Tines Stories installation; Fargate guide is a CLI recipe, not a supplied CloudFormation stack · Source ↗ · AWS Fargate deployment guide ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Example Fargate task allocations; workload, retention and availability require a separate sizing plan · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Public self-hosted subscription framework, not a negotiated quote or automatic applicability of self-serve SaaS terms · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
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.
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.
Compare within Incident & investigation management
- ArkCase Enterprise (self-managed)Configurable case management platform with FOIA and investigative solutions.
- AWS
- Darktrace Forensic Acquisition and InvestigationCommercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.
- AWS
- Azure
- Google Cloud
- FormKiQ Incident and Investigation Management Directory PublisherManage document-centric intake, investigation, and resolution of incidents, complaints, and regulatory matters with structured workflows and audit trails.
- AWS
- Sandfly SecurityCommercial self-hosted Linux threat-hunting and investigation platform.
- DigitalOcean
- SAP S/4HANA EHS — Customer-OperatedCustomer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.
- AWS
- Azure
- Google Cloud
- TheHive Self-HostedSelf-hosted security incident-response case management for investigations and analyst collaboration.
- AWS
- Azure
- TimesketchOpen-source collaborative forensic timeline analysis application.
- Azure
- Google Cloud
- Tracecat Self-HostedOpen-source security-workflow automation with an upstream customer AWS deployment.
- AWS
Showing 8 of 10 other listings in Incident & investigation management. These products address related workflows; read their category-fit notes before comparing scope. See all of Incident & investigation management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- AWS Fargate Guide ↗www.tines.com
- Subscription Terms ↗www.tines.com
- Release Notes ↗www.tines.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- AWS Fargate Guide ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- AWS Fargate Guide ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked