4 ms·
This looks really interesting! As someone who's tried Zapier, IFTTT, Parabola, Actiondesk, Airtable, Unito and a few more tools whose names escape me right now
by tekacs 7y ago
This looks really interesting!
As someone who's tried Zapier, IFTTT, Parabola, Actiondesk, Airtable, Unito and a few more tools whose names escape me right now, it's exciting to see a tool focusing on code as the way of stitching services together.
In my case I've been fed up and have ended up building a stitching service at each company and for my personal use, but I would have preferred a solution that saved from the initial setup and hassle.
I wasn't expecting the 'internal tools' aspect to come up as I read through the page -- I'm curious about that -- how does the intended use-case compare to something like Retool.io (which is also available on-prem)?
- bpodgursky 7y agoThanks! To answer with respect to Retool directly, we actually wrote that up a bit here https://www.cloudwright.io/blog/retool-backend https://www.cloudwright.io/blog/retool-backend -- the short answer is, Retool is great for putting together UIs and database queries, but our focus is on the backend. One of the things we want is to make it easy to put together robust, lightweight APIs, with more complexity or connection requirements than you can embed in a frontend. We also aim to be an easy way to set up scheduled or programmatic jobs -- stuff like scheduled file transfers or email notifications, where the primary interface isn't a web UI (when you aren't monitoring, developing, or debugging)
- tekacs 7y agoThat makes perfect sense -- for a lot of the use-cases that I've experienced, I would have wanted to either hook the interface ('trigger button', 'view past runs' or similar) into an existing app or just iframe-d in your solution to that piece. Sounds really interesting -- I think we'll give it a go.