Priced by where it runs.

The same engine and the same workflow definitions either way. What changes is whose infrastructure it runs on — and everything above the licence is delivered by an engineer, not by a plan.

Whether a self-hosted environment has outbound internet access is your network policy, not a different product. Both are the same licence.

Cloud

Runtara operates your instance on dedicated compute — its own runtime, its own database, its own network. Not a shared tenant, and not a shared database.

$250/ Month

Per instance. Unlimited workflows and runs inside it, billed monthly.

Talk to us
  • Dedicated runtime and databaseYour own runtime process and your own database on dedicated compute. Isolation is a property of the deployment, not a permission setting.
  • Unlimited workflow runs — no per-task fees, no run-count limitsA workflow run is one execution of an automation, including the trigger and all downstream steps. Capacity is bounded by invocation time and operational usage, not run count.
  • Your own model endpoint and credentialsOn every plan. Runtara calls models through your credentials against your endpoint, billed to your account at your rates. There is no Runtara-operated inference layer in the path.
  • Standard and premium integrationsStandard covers Shopify, HubSpot, Slack, Teams, S3-compatible storage, Mailgun, PostgreSQL, OpenAI, and more. Premium adds Business Central, NetSuite, SharePoint, and other systems needing custom field mappings or extended auth flows.
  • API and MCP accessStart runs, read results, and manage triggers over the API. Connect an MCP client to author, debug, and deploy workflows using your preferred AI tools.
  • Interactive reportsReports that query your operational data, allow inline edits, and trigger workflows straight from the interface.
  • Email support, 24h response
Most common

Self-hosted

Runtara runs on infrastructure you own — your cloud account, your own hardware, or an environment with no route to the public internet at all.

From$2500/ Month

Per deployment. One isolated instance, with unlimited workflows and runs inside it.

Talk to us
  • Everything in Cloud
  • Deployed to your AWS, Azure, GCP, private cloud, or bare metalThe same engine and the same workflow definitions, running inside your own environment under your own network policy.
  • Your VPC, your network policy, your backups, your residency guaranteesThe deployment sits inside your own controls. Runtara has no standing access to it and no route into your network.
  • Runs fully offline, with an update path that requires no inbound accessSuitable for environments with no route to the public internet. Updates are delivered as artifacts you apply; nothing dials in.
  • SSO / SAML via your identity provider, append-only execution logSign-in federated to your identity provider through our Auth0 identity layer, configured as part of your deployment. Every execution is written to an append-only log you can query and export.
  • Architecture documentation and security-review supportData-flow diagrams and architecture documentation for your review, and we fill in the security questionnaire your process runs on.
  • Named support contact, 8h responseA named technical contact rather than a shared queue. Includes a Slack-shared channel on request.

Forward-deployed engineering

Getting workflows into production

Workflow design, build, and rollout are delivered by a Runtara engineer working inside your team, against your systems, on your infrastructure. Not a ticket queue and not a handover document — an engineer who knows the runtime, embedded for as long as the work needs.

Priced as a monthly engagement, separately from the licence.

Talk to us about scope
  • Discovery and process mapping against your existing systems
  • Production build, with your team learning the platform alongside it
  • Security review support, architecture documentation, and audit evidence
  • Ongoing workflow development as the process changes

Frequently asked questions.

Are there limits on the number of workflow runs?

No. There are no per-task fees or run-count limits on any plan — capacity is bounded by total invocation time and operational usage, not run count.

Can we run Runtara with no outbound internet access?

Yes. A self-hosted deployment runs fully offline, with no route to the public internet in either direction. Updates are delivered as artifacts you apply on your own schedule; nothing dials in or calls home.

Do you process our data?

Not on a self-hosted deployment. The runtime executes inside your infrastructure, using your model credentials, and transmits no customer data to Runtara. Managed Cloud is a different arrangement, covered by a DPA.

How that changes a vendor review

Can I change plans?

Yes. Plan changes can be handled at the start of the next billing cycle.

Do you offer a trial?

Not a self-serve trial. We scope a paid pilot instead: one real process, built end to end on your systems, on a fixed scope and a fixed fee. You finish with a workflow in production rather than an expired sandbox.

What does the engineering engagement cost?

It is quoted as a monthly engagement after a scoping call, with a minimum term. It depends on the systems involved and the complexity of the process, and is never bundled into the licence.

Where is our data hosted?

On Cloud, in the EU with data kept in-region. On self-hosted, wherever you put it — your cloud account, your own hardware, or an environment with no external route at all.

Not sure which plan fits?

Tell us what you're trying to automate and which constraint you are under. We'll point at the plan that matches — or tell you the workflow needs a different shape before pricing applies.

Book a free 30-minute callRead about security