Live data from Hacker News

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

trigger.dev

161–170 of 196 posts

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

#161
post #154

Would love it if there was an email list I can subscribe to so I can keep up to date with development. I don't have a use for Trigger right now, but it seems like a cool tool that I want to keep up with.

We don’t have a newsletter at the moment so the best way to stay up to date is via Discord where we’ll be posting all our updates: https://discord.gg/hYmCPJRDcb

I can't accept the invite. Has it expired?

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

#162
post #75

Earlier quoted context omitted.

And if you don't store much inside the workflows themselves - it's quite cheap even if you have hundreds of thousands invocations.

1M invocations looks like $25, which is really cheap

I meant daily, but it's still cheap.

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

#163
As someone who got burned by past "Open Source" projects, yours raises all redflags:

- Advertised as "Open Source", yet this is actually a paid product with a pricing page.

- You don't even have a guide on how to install this thing... euh, I mean what's the point of this if I can't use it?

- You have a complicated license: https://github.com/triggerdotdev/trigger.dev/blob/main/LICEN.... You might have an "open" source as anyone can see the source but it's not as open as say an MIT license for the whole project.

- Your pricing conflicts with your open source users. You need them to build and improve the product but you also want them to have a worse experience otherwise your cloud-hosted solution will not prevail.

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

#165
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 :)

When you look at self-hosting instructions then it would be great if it would be one that does not require Docker in your stack. Installation shell script would be even better.

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

#166
post #163

As someone who got burned by past "Open Source" projects, yours raises all redflags: - Advertised as "Open Source", yet this is actually a paid product with a pricing page. - You don't even have a guide on how to install this thing... euh, I mean what's the point of this if I can't use it? - You have a complicated license: https://github.com/triggerdotdev/trigger.dev/blob/main/LICEN... . You might have an "open" sour…

self hosting feels like an afterthought. That's a red flag, it means they actually don't have any open source users or ecosystem.

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

#167
post #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.

n8n is also great about this. It retains the visual “easy mode” environment but lets you drop in a JavaScript node whenever you need to do something more complex

I found the JavaScript nodes to be quite annoying. Specifically -

1. I want a proper IDE

2. Proper typing so the feedback cycle is faster.

3. Being able to use external packages

4. Being able to quickly test my custom node across old runs.

Their JavaScript nodes take me an absurd amount of time to get right. And I've needed to use them far more often than I would like.

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

#168
‘Developer-first Zapier alternative’ is an odd positioning, I think the point of Zapier is that it’s for non-developers mainly. Looking at the comments, though, it seems like there’s a need for something like this. Keen to see how you iterate and improve your positioning. Good luck!

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

#169
post #163

As someone who got burned by past "Open Source" projects, yours raises all redflags: - Advertised as "Open Source", yet this is actually a paid product with a pricing page. - You don't even have a guide on how to install this thing... euh, I mean what's the point of this if I can't use it? - You have a complicated license: https://github.com/triggerdotdev/trigger.dev/blob/main/LICEN... . You might have an "open" sour…

self hosting feels like an afterthought. That's a red flag, it means they actually don't have any open source users or ecosystem.

Right? They advertise as an "Open-Source", MIT and self-host. But then they make it difficult (you need to figure out how to install this thing, lol). That would be understandable if this was done pro-bono (the paid service didn't exist). But they have a team and a paid service behind me.

It's not the model that bothers me (if you want to mix OS with SaaS/Paid, then it's all good) but the false and dark-pattern advertising.

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

#170
post #163

As someone who got burned by past "Open Source" projects, yours raises all redflags: - Advertised as "Open Source", yet this is actually a paid product with a pricing page. - You don't even have a guide on how to install this thing... euh, I mean what's the point of this if I can't use it? - You have a complicated license: https://github.com/triggerdotdev/trigger.dev/blob/main/LICEN... . You might have an "open" sour…

I always check the license first and this is not too nice. These mixed licenses are a real nightmare for companies and their lawyers. Keep it clean & simple or there won't be a lot of adoption really.
Post reply on HN