temphia VS el-cptn

Yeah, i hate and admire WordPress at the same, in my brief exposer I quite like its hooks/action/plugin system. In a weird way my current project[0] is inspired by wordpress. (its not a exact CMS thing but), what if someone build a wordpress like pluggable system but plugin donot run in same eval/execution context, maybe inside wasm containers.

[0]: https://github.com/temphia/temphia

iframe related code would here.

https://github.com/temphia/temphia/blob/main/code/frontend/l...

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.