Tracecat Self-Hosted

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

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Terraform; Docker / Compose

  2. 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 methodTerraform; Docker / Compose
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

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.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Documented self-hosted platform-user SAML path; not OAuth credentials used by workflow integrations · Source ↗ · Self-hosted Fargate authentication defaults ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Tracecat Self-Hosted deployment example; review the full linked installation instructions · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-19

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

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.

Docker Compose reference sizing, not Fargate task sizing or a 100-user/1-TB HA guarantee · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

Tracecat Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

Tracecat Self-Hosted upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 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.

Scope & considerations

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.

Community & 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.

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.

Compare within Incident & investigation management

  • ArkCase Enterprise (self-managed)Configurable case management platform with FOIA and investigative solutions.
    • AWS
    Customer-operated · Not specified
  • Darktrace Forensic Acquisition and InvestigationCommercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • 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
    Customer-operated · Commercial Only
  • Sandfly SecurityCommercial self-hosted Linux threat-hunting and investigation platform.
    • DigitalOcean
    Customer-operated · Commercial Only
  • SAP S/4HANA EHS — Customer-OperatedCustomer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • TheHive Self-HostedSelf-hosted security incident-response case management for investigations and analyst collaboration.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • TimesketchOpen-source collaborative forensic timeline analysis application.
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • TinesCommercial self-hosted automation platform with an AWS Fargate deployment guide.
    • AWS
    Customer-operated · Commercial Only

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

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. 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.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory