Live data from Hacker News

Show HN: We built a developer-first open-source Zapier alternative

trigger.dev

11–20 of 196 posts

Re: Show HN: We built a developer-first open-source Zapier alternative

#12
Would love this self-hosted.

The license says "All content that resides under any "ee/" directory of this repository, if such directories exists, are licensed under the license defined in "ee/LICENSE".", but there's no folder named ee? What is this referring to?

Re: Show HN: We built a developer-first open-source Zapier alternative

#13
post #9

Looking at the long delays, do I understand correctly that this is something similar to Temporal[0] or AWS Step Functions? My first sentiment was "when I'm already writing code, why not just use Lambda", but it looks like these delays are kind of the selling feature, and it looks like the UX is better than step functions. I'd be curious about your selling points over Temporal, as I can't seem to find any comparison.…

Yup I've done the AWS Step Functions thing in the past, and it usually was about 90% wrangling with AWS and 10% writing code... we wanted to flip that ratio around (that's the goal at least!)

As for temporal, we are pretty similar to them, although I think we have more of a focus on making it easy to trigger (sorry) the workflows from third party events (webhooks, etc.) and then making reliable requests once you are in a workflow.

Thanks for the feedback though, we'll try and add service comparison docs soon!

Re: Show HN: We built a developer-first open-source Zapier alternative

#14
post #12

Would love this self-hosted. The license says "All content that resides under any "ee/" directory of this repository, if such directories exists, are licensed under the license defined in "ee/LICENSE".", but there's no folder named ee? What is this referring to?

We haven't done any ee features yet, which is why we stuck that "if such directories exists" line in there. We're following the playbook from some other OSS companies such as PostHog and Cal.com. Features that will go in ee (off the top of my head) are the teams and billing features of our hosted option.

We'll be working on self-hosting instructions soon as well :)

Re: Show HN: We built a developer-first open-source Zapier alternative

#16
post #14
post #12

Would love this self-hosted. The license says "All content that resides under any "ee/" directory of this repository, if such directories exists, are licensed under the license defined in "ee/LICENSE".", but there's no folder named ee? What is this referring to?

We haven't done any ee features yet, which is why we stuck that "if such directories exists" line in there. We're following the playbook from some other OSS companies such as PostHog and Cal.com. Features that will go in ee (off the top of my head) are the teams and billing features of our hosted option. We'll be working on self-hosting instructions soon as well :)

A little while back, I was working with a startup that built an AI note taking app. They offered several integrations for their customers, and at the time I wished that there was a Zapier alternative that allowed for a multi-tenant approach (i.e. build a pipeline that each customer could independently hook into with their own external accounts).

I haven't had a chance to go through your site yet, but that would be a killer feature to have.

Re: Show HN: We built a developer-first open-source Zapier alternative

#17
At first I thought that a code alternative for a no-code solution like zapier was counterintuitive. But as an engineer using Zapier (for the first time) these past few months I got so frustrated by the lack of an option to just write some "if" or just 2 lines of code to make things work the way I want them.

I think trigger.dev nails it. This is exactly what I needed.

Re: Show HN: We built a developer-first open-source Zapier alternative

#18

How does this compare to Pipedream and Windmill, both of which are also open-source?

In Trigger.dev workflows are created completely in your code rather than in a node-based UI (which to be fair does allow you to write code sometimes). We found developers could actually put together workflows faster if the whole thing was code rather than a hybrid of UI / code (because you get to use your own IDE + Copilot).

Re: Show HN: We built a developer-first open-source Zapier alternative

#19
post #14

Earlier quoted context omitted.

We haven't done any ee features yet, which is why we stuck that "if such directories exists" line in there. We're following the playbook from some other OSS companies such as PostHog and Cal.com. Features that will go in ee (off the top of my head) are the teams and billing features of our hosted option. We'll be working on self-hosting instructions soon as well :)

A little while back, I was working with a startup that built an AI note taking app. They offered several integrations for their customers, and at the time I wished that there was a Zapier alternative that allowed for a multi-tenant approach (i.e. build a pipeline that each customer could independently hook into with their own external accounts). I haven't had a chance to go through your site yet, but that would be a…

Indeed we've had a few people who've requested this type of thing (they want to make requests authenticated as their customers, not as theirselves). Currently we only support making requests as yourself (e.g. post into your own slack channel), but our architecture will support making requests as your customers, and something we are very interested in doing eventually
Post reply on HN