[dylburger]

I hear you! We're tracking this in a couple of issues:

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

[Ataraxy]

Cool. Hope it comes to fruition.

My other pipedream in addition to this would be multi tenancy (including integrations).

A perfect world scenario is a drop in multi tenant zapier alternative that enables SaaS providers to either create workflows for their users so all they need to do is authenticate integrations for the most part or allow for them to build their own workflows from scratch.

I realize this is probably out of scope of the services aim but it doesn't hurt to throw it out there since all of the alternatives that exist are sorely lacking in various ways.

[dylburger]

We hear this a lot from devs and we do plan to tackle it. I was building productivity tools (mostly for Gmail / Google Calendar) at my last startup and would have loved to have Pipedream manage OAuth / token refresh, kick off workflows on behalf of my users, etc.

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

[toomuchtodo]

Could you use OpenFAAS as an execution environment for the integrations/functions? This would allow you to run this without Lambda as well.

[dylburger]

Yes we're thinking a lot about this. The vision would be let you execute workflows on whatever function runtime you use. So you'd have one definition of a workflow on Pipedream, but that could be serialized to e.g. a Google Cloud Function, an OpenFAAS function, etc. And you'd get to run it in your own VPC, with access to your own internal resources, without relying on Pipedream's infra.

Still in the idea phase, but let me know if that resonates.