dylburger
Joined 7 years ago
Joined 7 years ago
We do a little work to create the shell of the app integrations, e.g. we add the logo, for OAuth apps we configure the details of the OAuth authorization / refresh process, etc. Then you can develop any sources or actions for the app and publish them for all Pipedream users.
The best place to chat is on our public Slack or GitHub, if you're interested. See https://pipedream.com/support .
We build our own containers and still run them on Lambda. The container base image contains the necessary language runtimes so that we can execute both Node.js and e.g. Python in the same workflow.
Do you think it would make sense to add an OpenFAAS integration to Pipedream? Then it would show up when users searched for it in workflows, and have a dedicated page at https://pipedream.com/apps . Even if we just end up wrapping HTTP requests to kick off a function, we've found it's helpful because users are often searching for FaaS platforms by name when they want to integrate with them in a workflow.
Still in the idea phase, but let me know if that resonates.
If you're interested, join our community and you'll get early updates on stuff we're working on (GitHub integration, TypeScript / other new language runtimes, etc.): https://pipedream.com/support
You can see our pricing at https://pipedream.com/pricing and a deeper overview / FAQ here: https://pipedream.com/docs/pricing/
1. We plan to publish an execution environment (as a container) that simulates the core Pipedream runtime. You could run this locally or as a container on whatever container service you'd like. 2. We get a lot of requests for a fully-self-hosted / open-source version, and we're considering how to approach that as well.
Please follow the issues below, and let us know if you have any more feedback!
[1] https://github.com/PipedreamHQ/pipedream/issues/1635 [2] https://github.com/PipedreamHQ/pipedream/issues/954