Pipedream counts its catalog at 1,000+ apps in one paragraph and 500+ in another
Connect APIs, remarkably fast. Free for developers.
At a glance
- What is it?
- The PipedreamHQ/pipedream monorepo is where the component code for a hosted integration platform lives, plus the platform's own build and test tooling. It publishes no GitHub releases, declares its root package as MIT while the repository license field is unasserted, and its own copy gives two different figures for the size of the connector catalog.
- Who is it for?
- Pipedream fits developers who want to prototype against a hosted catalog of connected apps and drop into Node.js, Python, Go, or Bash the moment a pre-built action is not enough, with no per-developer fee. It does not fit teams that need a versioned artifact, a documented license signal, or a stable catalog count to make an architecture decision.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- PipedreamHQ/pipedream11,785 ★ · +84
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| PipedreamHQ/pipedream | 11.7k | 11.8k |
84 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The same page says 1,000+ integrations in three places and 500+ in one
Pipedream's own copy disagrees with itself about the size of its catalog. The opening paragraph says the platform has over 1,000 fully-integrated applications. The Key Features list repeats that figure as 1,000+ API integrations when it explains actions. The workflows paragraph says you can connect to any of the 1,000+ integrated apps. Then the Actions section further down the same page describes actions as pre-built steps you can use across Pipedream's 500+ API integrations. Same product, same component directory, two different counts, a factor of two apart, on one page. For a reader this number matters more than it first appears, because catalog size is how people decide whether a connector exists for their stack before signing up. A headline figure that varies that much within a single document cannot answer that question, and nothing in the repository says which one is current. The components directory is the ground truth, but no page explains whether the headline number is derived from it or refreshed on any schedule.
There is no release tag to pin and the default branch is master
This repository publishes no GitHub releases, so there is nothing to pin a checkout or a downstream build to. The root package.json carries version 1.2.1 with the description Pipedream Monorepo. That number describes this repository's package, not the hosted platform, and the platform's component behavior and API surface change independently of it. The default branch is master rather than main, which matters when you copy CI configuration from a repository that uses the other convention. For a team that needs a repeatable build, the consequence is that there is no supported way to record which components you validated. A commit hash is the only handle available, and no root file documents that as the intended practice. Change review happens through pull requests and a CONTRIBUTING.md rather than through release notes, because no changelog artifact is published from this repo.
The root package.json declares MIT while the repository license field is unasserted
Two sources disagree about licensing. The repository is indexed with no license assertion, meaning its license metadata does not resolve to a recognized identifier for tooling that reads it over the API. Inside the tree, the root package.json sets its license field to MIT and a LICENSE file sits at the top level. For anyone vendoring component code out of components/ into a closed-source product, that gap is the first thing to resolve, because what an automated license scanner reads and what your legal team reads may not be the same document, and no NOTICE file or scope statement clarifies whether the MIT terms in the root package are meant to cover the component directories individually. Read the LICENSE file and the contribution guide directly instead of trusting the API response.
The docs directory the intro points to is missing from the file tree
The opening section tells readers what this repo contains, and one of the items on that list is the Pipedream docs, linked to the master/docs directory. The file listing for the project shows no docs/ entry at the top level. The root package.json repeats the same mismatch in its directories field, which maps lib to components, doc to docs, and example to examples: components/ is present, while docs/ and examples/ are not. So the documentation lives on the website at pipedream.com/docs, and the checkout you get from GitHub does not contain the text you were sent to read. The consequence for a reader is that documentation version and code version drift independently. You can clone a component, run its tests, and still have no local copy of the guide describing its required configuration or its expected props. Keep your own copy of whatever documentation revision you rely on, because no tag in this repository ties the prose to a commit.
The build is one script and the toolchain is pinned to a single pnpm version
Contributing here is a pnpm monorepo exercise with an unusually tight pin. The root package.json sets packageManager to [email protected] and declares engines pnpm 10.28.2, so a different package manager version is a declared mismatch rather than a matter of taste. The install is tied together by pnpm-lock.yaml and pnpm-workspace.yaml, alongside the packages/, platform/, helpers/, and types/ directories. The build step is a single command, node scripts/build-components.mjs. Tests are split by area instead of run globally: the test script is jest --passWithNoTests components, and test-all expands to npm test && npm run platform-test && npm run types-test, the platform and types steps changing into their own directories first. Repository hygiene is enforced through husky, installed by a prepare hook, alongside an eslint flat config at eslint.config.mjs and a spellchecker configured by .spellcheck.yml with its own word list. The consequence is that a first-time contributor cannot bring a generic Node setup and start.
The platform-dist task creates a commit from your working tree
One of the root scripts is platform-dist, which changes directory into platform, stages the dist directory, and commits it if the tree differs from HEAD. That makes a distribution task carry a version control side effect: running it does not only produce files, it writes a commit whose message is update platform/dist. It also reveals how the project treats generated output, since the platform bundle is tracked content in a repository that publishes no releases. For a contributor the trap is obvious in hindsight. A task named like a packaging step can leave you with an unexpected commit sitting in the middle of unrelated work, and separating it from your feature commits becomes a manual step you have to remember. Alongside it sits a package validation family built on node scripts/generate-package-report.js, with verbose, report-only, and dry-run variants plus a single-package form. Those are safe to run while iterating. platform-dist is not, unless you actually intend to commit.
Publishing an action puts your code in front of everyone
Custom actions are described as reusable across your own workflows, and the same component model has a publish path: you can publish actions to the entire Pipedream community, making them available for anyone to use. That single sentence is the collaboration model, and it carries a consequence the pages do not spell out. Once a component is published it is no longer yours alone, and its code joins the shared catalog that other workflows are built on. Sources, actions, helpers, types, and platform code all sit in this repository under components/, sources/, helpers/, types/, and platform/, and contribution guidelines exist specifically to govern that flow. If your action embeds a credential handling pattern, an internal hostname, or a workaround that encodes knowledge about your own infrastructure, publishing it is a disclosure decision rather than a technical one. Make that call before running the publish flow.
No install command, so the first run is a component file you paste in
The entry points the README names are the workflow quickstart at pipedream.com/docs/quickstart/ and the component authoring guides under pipedream.com/docs. What you actually do first, when no pre-built source fits your case, is paste a component into the editor. The shortest possible source exposes an HTTP endpoint and prints whatever request hits it:
export default {
name: "http",
version: "0.0.1",
props: {
http: "$.interface.http",
},
run(event) {
console.log(event); // event contains the method, payload, etc.
},
};Four keys carry the whole model: name, version, props, and run on a default export object, with the platform binding an interface into props through the $.interface namespace. That binding is how a component receives an inbound endpoint without declaring a route itself. The first-use cost is therefore not a package install but learning this object shape and the namespace behind it. Once a source does emit, events leave the editor through Pipedream's REST API or a private, real-time SSE stream, and destinations deliver them asynchronously to Amazon S3, Snowflake, HTTP, and email. Real ceilings sit at docs.pipedream.com/limits.
Editorial conclusion
Pipedream fits developers who want to prototype against a hosted catalog of connected apps and drop into Node.js, Python, Go, or Bash the moment a pre-built action is not enough, with no per-developer fee. It does not fit teams that need a versioned artifact, a documented license signal, or a stable catalog count to make an architecture decision. Before committing, read docs.pipedream.com/limits for the real ceilings, read the LICENSE file rather than the repository metadata for terms, and confirm that a pinned commit, not a release tag, is acceptable as your reproducibility handle.
Frequently asked questions
What is Pipedream software?
Pipedream is a hosted integration platform for developers. Event sources watch services such as GitHub, Slack, Airtable, and RSS, workflows chain pre-built actions and custom code off those events, and custom steps can run Node.js, Python, Golang, or Bash. Individual developers pay no fees, with the limits published at docs.pipedream.com/limits.
What does Pipedream actually mean?
Pipedream is the product name of the integration platform. What the project states about itself is that it connects APIs, is free for developers, runs a hosted platform with over 1,000 fully-integrated applications, and has demonstrated SOC 2 compliance with a Type 2 report available on request by emailing [email protected].
What is the Pipedream API?
Events emitted by sources can be consumed through Pipedream's REST API or through a private, real-time SSE stream. Destinations deliver those events asynchronously to Amazon S3, Snowflake, HTTP, and email, and when no pre-built source fits, the docs show building your own, with the simplest case exposing an HTTP endpoint that prints the request contents when invoked.
What is Pipedream Connect?
Connect is not among the key features the README lists (workflows, event sources, actions, custom code, destinations, free tier). The README does describe custom code inside a workflow, where you can import any package from the language's package manager and connect to any Pipedream connected app, alongside pre-built sources and actions across the app catalog.
What is the Pipedream company?
The project points to its own site at pipedream.com, a support page at pipedream.com/support, a community page, and a jobs board hosted on wellfound.com/company/pipedreamhq/jobs. The monorepo's package.json names the author as Pipedream with the contact [email protected].
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pipedreamhq-pipedream)Star history chart for your README
[](https://hysenlabs.com/projects/pipedreamhq-pipedream)Was this useful?