I'm excited to show off ExecAPI, a zero-infrastructure background job runner as a service. It's a bit like a hosted Sidekiq (if you're from the Ruby world), except that you can write your job workers in any language that has a Docker image available.
Background jobs (aka workflows) are triggered by either a Cron schedule or an on-demand HTTP request, which then executes one or more actions. Each action is user-submitted code that runs a Docker image of your choosing, and is run in a secure sandbox (currently gVisor, perhaps Firecracker VM in the future).
It's a bit rough around the edges right now, but I'd love to get some feedback on the direction I'm going with this. The plan is to build a low/no-code experience consisting of triggers and actions that can be be used to build automation workflows, a bit like Zapier, IFTT, et al. and to provide an on-prem/private VPC solution.
I'm excited to show off ExecAPI, a zero-infrastructure background job runner as a service. It's a bit like a hosted Sidekiq (if you're from the Ruby world), except that you can write your job workers in any language that has a Docker image available.
Background jobs (aka workflows) are triggered by either a Cron schedule or an on-demand HTTP request, which then executes one or more actions. Each action is user-submitted code that runs a Docker image of your choosing, and is run in a secure sandbox (currently gVisor, perhaps Firecracker VM in the future).
It's a bit rough around the edges right now, but I'd love to get some feedback on the direction I'm going with this. The plan is to build a low/no-code experience consisting of triggers and actions that can be be used to build automation workflows, a bit like Zapier, IFTT, et al. and to provide an on-prem/private VPC solution.