Tines free edition limits: open-source alternatives

The main thing a paid Tines edition adds is the removal of the workflow cap. Tines lists its Free edition with unlimited users, spaces and connectors but only 3 live workflows, while its paid editions carry unlimited workflows and flexible deployment options. For a team that has outgrown three live workflows, that is the core change: the question shifts from which workflows fit the free tier to which deployment model and support level the organization needs. The Tines pricing page is the reference for current edition contents, so check it against what your team actually runs before you request anything.

Tines' pricing FAQ says flexible hosting options are available on request. That phrase matters if you need self-hosting, a dedicated environment or a specific region, because those options are not described as standard on the public pricing page. Ask for a written quote that states, for each paid edition: which deployment modes are included (cloud, self-hosted or hybrid), whether self-hosting is covered by the subscription or by a separate agreement, what support response levels apply, and who performs upgrades and backups in each mode. Do not treat a verbal answer as confirmation of any of these points.

Price is not stated here because no supplied figure exists. Your comparison should use the written quote alongside the cost of running a self-hosted alternative. Recurring costs in a Tines subscription are the license and support terms, while an open-source platform shifts recurring cost to servers, storage, maintenance and staff time. Confirm with Tines what is included in the quote, including any charges that depend on the number of stories, runs or environments.

Self-hosting Shuffle removes the workflow cap, but the cost moves to your team. The recurring costs are the servers and storage for the frontend, the Go backend on port 5001, and the OpenSearch document database, plus at least one Orborus node that starts a worker for each execution. The Shuffle install guide sets a minimum of 4 GB of RAM for a single host, but it also warns that the default Docker Compose setup is not scalable without changes. Production sizing depends on workflow volume, execution frequency and retention, so ask a partner to size these from your actual Tines story inventory rather than from a generic figure. Shuffle's high availability guidance adds an OpenSearch cluster, NFS for shared files and more than one Orborus node, each of which is another component to pay for and patch. The skills cost is less visible. Someone must own OpenSearch health, index growth and backups, and the SHUFFLE_ENCRYPTION_MODIFIER secret. That key encrypts saved app credentials with AES-256 in OpenSearch, and the Shuffle configuration docs warn that losing or changing it breaks every saved app authentication. Store it in a secrets manager, back it up separately from the database, and test a restore before you go live. Upgrades are a second recurring task. Shuffle v2.3.0 was published on September 28, 2026, and the docs recommend the latest Docker tag for stable use and the nightly tag only for experiments. Pin a version, test upgrades in a staging copy and plan a rollback path.

The largest one-time cost is the workflow rebuild. Tines stories do not port automatically, so each story needs its HTTP actions, credentials, webhooks and schedules recreated as Shuffle workflows and apps. Effort depends on how many stories you run, how many use custom HTTP calls rather than prebuilt connectors, and how many need a new app built with the App Creator from an OpenAPI specification. Ask a partner to estimate this per story, with a test plan for each one before triggers move, because a missed trigger fails silently in production. On-call coverage is the cost most teams underestimate. A self-hosted SOAR that runs containment playbooks is now an operational dependency, so someone must respond when Orborus stops polling or the backend fails. For a fixed-scope quote, ask for: sizing and architecture options, OpenSearch and backup setup, the secret handling and restore procedure, an upgrade runbook for tag changes, the story-by-story rebuild plan with acceptance tests, and the on-call model and hours included after handover. Compare that written scope with the Tines paid editions and their hosting options, which the Tines pricing page describes.

DeployOpen plans, implements, integrates, hardens, backs up, upgrades and documents self-hosted platforms inside the client's own infrastructure, including cloud accounts, data centers and air-gapped networks. For a team leaving the Tines Free edition, that work covers the platform itself, its identity integration, secrets handling and the operating runbooks that keep it running. Engagements are fixed-scope: the scope, deliverables and timelines are agreed in writing before any work starts, and ongoing support, upgrades and continuous testing are available as retainers. DeployOpen does not publish a price list, so a quote follows from the written scope rather than from a standard package.

In practice, the first decisions are architectural. For Shuffle, the reader needs to choose among a single server with Docker Compose, Docker Swarm, a hybrid with Shuffle Cloud and a local Orborus, or Kubernetes with Helm charts, and the install guide notes that the default Docker Compose setup is not scalable without changes. For Tracecat, the choice is between Docker Compose on one host, AWS ECS Fargate through Terraform, Kubernetes through a Helm chart, or an air-gapped Kubernetes deployment. Hardening work covers the SHUFFLE_ENCRYPTION_MODIFIER secret, which must be backed up and never changed, SSO configuration, and network paths for app containers. Confirm the current minimum resource and version requirements with each vendor before sizing hardware.

Backup and upgrade planning matter more once workflows run in production. Shuffle stores saved credentials in OpenSearch, so backup scope has to include the database and the encryption secret together. Tracecat depends on PostgreSQL, an S3-compatible object store and Temporal, so each needs its own recovery point. Ask any implementation partner, DeployOpen included, to document a tested restore procedure, an upgrade path between releases, and who on your side owns each runbook. DeployOpen prepares systems, controls and evidence for compliance assessments, but independent auditors and certification bodies issue any audit report or certification. DeployOpen is not an official partner, reseller or certified provider of Shuffle or Tracecat.