Kovca vs. Pipedream

Workflow automation built for developers and AI agents

Pipedream Workflows is in maintenance mode and shuts down on March 31, 2027, as Pipedream focuses on Connect, its integration layer for AI. If you're moving your workflows, Kovca is a managed platform for programmable workflows you build, deploy, and execute through APIs, webhooks, and AI coding agents.

For developers who ship automation as part of their product, and the coding agents they build with.

Start Building View Documentation

Why developers choose Kovca

A home for workflows after Pipedream Workflows

Pipedream gave developers code-first workflows. Kovca keeps the developer focus (APIs, versions, agents) and replaces code steps with typed nodes your AI agent can build and test.

Workflows your AI agent can operate

Connect Claude Code, Cursor, or VS Code to Kovca's remote MCP server and your agent can find nodes, build and edit drafts, validate, test, publish, run, and turn automations on. The API key sets the limit (Run, Author, or Publish), so an agent can build and test freely while publishing stays with a person. Every edit lands on the same draft you see in the Studio.

The MCP server

Workflows as application infrastructure

Every published workflow is an endpoint with a typed input and output contract. Call it with a bearer key and an Idempotency-Key, pin a version so a later publish never changes what your code receives, and look up any run and its steps by ID. The same workflow can also start from a schedule, an inbound webhook, or an app event.

Workflows API

Structured AI decisions

Decision AI nodes classify, score, and decide from outcomes you define, and return typed fields you branch on. There's no model to choose, no AI provider account to connect, and no output parser to configure: a successful evaluation is 5 credits. Generative AI nodes cover writing, summarizing, and extraction when you need words instead.

Decision AI

One experience for developers and agents

The Studio canvas and its assistant, the kovca CLI, your AI agent over MCP, and the API all edit the same drafts, run the same validation, and publish the same immutable versions. Sketch on the canvas, script it from the terminal, or hand it to an agent, without switching tools or formats.

The Studio

Feature comparison

Kovca and Pipedream, side by side

Both platforms cover the basics. The differences are in how each one does it, so every row says how, not just whether.

Kovca and Pipedream capabilities, last reviewed November 6, 2026
Capability	Kovca	Pipedream
Visual workflow builder	Studio canvas, with tests on saved examples Docs	Step-based workflow builder, part of Workflows (shuts down March 31, 2027)
AI-assisted building	Studio assistant on the web and kovca agent in the terminal, included within free daily limits Docs	String and AI code generation, both shutting down with Workflows
MCP server for coding agents	Remote MCP server on every plan; each API key is Run, Author, or Publish Docs	Pipedream MCP servers expose app actions as tools with managed auth, as part of Connect
Agent-managed lifecycle	Build, edit, validate, test, publish, run, and turn automations on or off over MCP Docs	MCP servers run app actions; they don't build or deploy workflows
Workflows as agent tools	Expose a published workflow as its own wf_ tool with its input schema Docs	Pre-built app actions as MCP tools
Call a workflow from your code	Every published workflow is an execute endpoint with typed input and output, idempotency keys, and run lookup Docs	HTTP trigger URL per workflow, with custom responses from $.respond() and an SDK to invoke workflows
Inbound webhooks	Webhook triggers with signature verification and de-duplication Docs	HTTP triggers with optional authorization
Schedules and app events	Schedule trigger and 400+ app events Docs	Schedule trigger and app event sources
Structured AI decisions	Decision AI nodes: typed outputs from outcomes you define, model included, fixed credits per evaluation Docs	No dedicated decision step; AI provider actions or code, with your own provider accounts
AI agents and generation	Generative AI nodes for writing, summarizing, extracting, and analysis, model included Docs	AI provider actions and code steps, with your own provider accounts
Custom code	No code step: built-in logic and data nodes, and HTTP actions	Node.js, Python, Go, and Bash code steps with npm and PyPI packages
Human approval and waits	Approvals, delays, and callbacks; a run can wait up to 90 days Docs	$.flow.suspend() in a code step pauses a run until its resume URL is called
Versioning	Every publish is an immutable version, on every plan; callers can pin one Docs	GitHub Sync for workflow projects: branches, pull requests, and a production branch
Workflows as code	kovca CLI export and apply, for review in pull requests Docs	GitHub Sync, and the pd CLI for custom components
Integrations	34 apps, plus any HTTP API Docs	3,000+ apps and 10,000+ pre-built tools; components are open source
Hosting	Managed service only	Managed service; Workflows ends March 31, 2027, and its data is deleted by April 30, 2027
Pricing	Credits for steps that succeed: 5,000 free a month, then $0.001 per credit, no monthly fee Docs	Credits by compute time (1 credit per 30 seconds); Workflows no longer accepts new subscriptions

Last reviewed November 6, 2026, from each product's public documentation and pricing. Pipedream features and availability vary by plan and change over time; check Pipedream's documentation for current details.

Pipedream sources

Choose Kovca when

Automation is part of what you ship

You're moving off Pipedream Workflows before March 31, 2027 and want a managed platform built for developers and actively developed.
Your application calls workflows like functions: typed input and output, idempotent retries, and pinned versions.
You want an AI coding agent to build, test, publish, and run whole workflows over MCP, not just call app actions.
You need classification, scoring, or yes/no decisions as typed fields, without managing an AI provider account or parsing model output.
Some cases need a person: a run pauses for an approval, a delay, or a callback for up to 90 days, then continues on the same version.

Pipedream may be a better fit when

You're embedding integrations, or your workflows are code

You're adding integrations to your own product for your users. Pipedream Connect handles their sign-ins and accounts; Kovca's connections belong to your workspace, not your end users.
You want your AI agent to call actions in thousands of apps. Pipedream's MCP servers cover 3,000+ apps; Kovca's MCP server builds and runs your workflows.
You depend on an app Kovca doesn't connect to. Kovca connects 34 apps, plus any HTTP API you configure yourself.
Your workflows are mostly custom code. Kovca has no code step, so code-heavy workflows may move more easily to another code-first platform.

See the difference

An agent builds, tests, and runs a workflow

Claude Code connects to Kovca's MCP server and builds a GitHub issue triage workflow while it appears in the Studio.

1
Connect
Add Kovca's MCP server to Claude Code with an Author key.
2
Ask
Describe the workflow. The agent finds nodes, builds the draft, and tests it, and you watch it appear in the Studio.
3
Review and publish
An Author key can't publish, so a person reviews the workflow, publishes it, and exposes it as an agent tool.
4
Run
The agent calls the published workflow as its own tool, and the run is recorded in Executions.

MCP setup guide More about the MCP server

Connect Claude Code

claude mcp add --transport http kovca https://kovca.io/api/v1/mcp \
  --header "Authorization: ******"

FAQ

Questions about Kovca and Pipedream

Is Pipedream shutting down?

Pipedream Workflows and String shut down on March 31, 2027. They're in maintenance mode, closed to new signups and subscriptions, and their data, including connected-account credentials, is deleted by April 30, 2027. Pipedream Connect, its MCP servers, and the API proxy aren't affected.

Is Kovca an alternative to Pipedream Workflows?

Yes, for workflows that start from an API call, a webhook, a schedule, or an app event, make decisions, and act. Kovca is managed, versioned, and built for developers and their AI agents. It doesn't replace Pipedream Connect, which embeds integrations in your own product for your users.

Can I import my Pipedream workflows into Kovca?

Not directly. Pipedream's export tool downloads each project's workflow structure as JSON, and you rebuild the workflow in the Studio, from the CLI, or by asking a coding agent to build it over MCP. Kovca has no code step, so custom code becomes built-in logic, data, and AI nodes, or an HTTP action that calls a service you run.

Does Kovca support MCP?

Yes. Kovca is a remote MCP server over Streamable HTTP, on every plan. Each API key is Run, Author, or Publish, and tools above the key's level are refused, so an agent can build and test without being able to publish. Pipedream's MCP servers expose app actions instead; the comparison table shows the difference.

Can I build workflows using Claude Code or other coding agents?

Yes. Claude Code, Cursor, VS Code, and other MCP clients that connect to a remote server with an API key header can list nodes, create and edit drafts, validate, test, publish, and run workflows. Hosted chat apps that require an OAuth sign-in to connect aren't supported yet.

Can I call Kovca workflows from my application?

Yes. Every published workflow has an endpoint, POST /v1/workflows/{id}/execute, that takes a bearer API key and typed JSON input. Send an Idempotency-Key so a retry returns the original run, pin a version so later publishes don't change your contract, and look up any run with GET /v1/runs/{id}. Outbound webhooks tell you when runs finish or wait.

Can I self-host Kovca?

No. Kovca is a managed service, and there is no self-hosted edition. Pipedream Workflows is a managed service too.

How does Kovca pricing compare with Pipedream?

They measure different things. Kovca charges credits for what succeeds: 5,000 free credits a month, then $0.001 per credit with no monthly fee. A Decision AI step is 5 credits and a run started by the API is 1; logic steps, tests, and simulated actions are free, and there's no separate AI provider account to pay. Pipedream bills credits by compute time, 1 credit per 30 seconds, and Workflows no longer accepts new subscriptions.

Build your next automation with Kovca.

Create workflows visually, manage them with AI agents, and integrate them directly into your applications. 5,000 free credits a month, no card required.