activepieces VS el-cptn

Activepieces - Build automation flows to connect several apps together in your app's backend. For example, send a Slack message or add a Google Sheet row when an event fires in your app. Free up to 5,000 tasks per month.

As per its description on github: N8n is a Free and source-available fair-code licensed workflow automation tool.

Not really OSS.

Check out: https://www.activepieces.com/

MIT open source.

There's also https://github.com/windmill-labs/windmill and https://github.com/activepieces/activepieces depending on which parts of retool and tooljet you care about.

I wonder how cptn compares with ActivePieces. AP's been declared the "Open Source Zapier" and I have been having a blast with it.

https://www.activepieces.com/pieces

https://github.com/activepieces/activepieces

There is an issue about this on our GitHub, you can comment on it with your specific use case to give it a push up, our piece building roadmap changes upon demand from users: https://github.com/activepieces/activepieces/issues/670

I use n8n to handle simple automations like this - and currently testing Activepieces too.

It was requested by someone, I'll appreciate it if you put some emphasis on the GitHub issue here: https://github.com/activepieces/activepieces/issues/438

Hi, I am Krishna Thota. I am building an open-source integration and data platform(https://cptn.io). The product is MIT licensed and the repo is at https://github.com/cptn-io/el-cptn.

Hi, I am Krishna Thota. I am building an open source integration and data platform(https://cptn.io). The product is MIT licensed and the repo is at https://github.com/cptn-io/el-cptn.

I have started on my startup journey an year ago and launched a monitoring platform called DevRaven. Unfortunately the product did not takeoff as expected. That story is for another day.

But during the course of building the product, I have built several integrations leveraging MQs and Cloud Functions. While building and deploying Cloud Functions for happy paths is easy, I had to monitor logs for failures, build retry mechanisms or manually process failed events, keep instances running to prevent cold start timeouts. It can also get expensive with charges for MQs, server time for running cloud functions etc and costs can be unpredictable.

I thought of building a platform where I can build integrations quickly, have the ability to look at incoming/outgoing events, look at logs, retry any failed events etc. And finally, predictable costs for running the infrastructure. cptn.io provides all these capabilities and more. You can build pipelines to integrate with any cloud services, send data from your backend to data warehouses, listen to web hook events etc. The platform can be integrated into any stack by sending events to HTTP end points.

Instead of trying to build a business first or launch an open source product under restrictive licenses, the platform will be available under MIT license so any user or customer can use it. There is no ee folder or complex dual licensing and I am also committing to releasing SSO under MIT. The plan is to offer a managed service in the cloud at a later time, accept sponsors for prioritizing features for enterprise customers and charge for enterprise support.

It should take less than 5 minutes to get the platform running on your machine. Welcome any feedback, feature requests, PRs and bug reports.