Hi, I'm Maksym from Etlworks

Hey everyone,

I’m a founder of Etlworks and Toolsverse. As many of you I’ve spent a few years on BOS and thought is was time to introduce myself to this group.

We just launched our new SaaS project Etlworks Integrator. It is a data integration service which has been in development for quite some time, was soft-launched in August and we actually have a few “enterprisy” customers already.

Happy to be a member of the living community of the bootstrappers again. As usual, any feedback on site and our live demo is very much appreciated.


1 Like

Welcome! I’m curious about a company that charges a significant monthly fee… ($250/month) I WISH I could charge that!

Thanks. Well, our competitors charge much more!

This - $250/mo - is a pocket change. Some of our integration projects cost us $10k/wk. Not all of the cost is the hardware and implementation, of course; in fact, I think the biggest part is the 24/7 support, but still.

Maksym, your site is all broken in Firefox. Just to let you know.

Thanks! Just noticed

Bad commit deleted all css. Fixed now

Looking at the demo, and I don’t get it. Your SaaS is in the cloud. When I setup a connector – how do I connect to a DB in my corp network?

For this we have on site agent which runs as a service behind the firewall. It can push data to the Integrator (or back) over http or cloud storage: https://www.toolsverse.com/products/integration-agent/index.html

The alternative is to install Integrator on premise and run it on your own network. We offer several installation options including docker container.

Updated FAQ to explain how Integrator can work behind the firewall. Thanks for feedback.

My primary daily responsibility is ESB - a integration via web services, that is. Interesting enough, I do not see WSs as a source or a target in your integrations. Your customers do not have a demand for that?

I’ve seen a demo by CA recently where they roll out a product that connects to an arbitrary database and without coding allows to expose its content as WS (SOAP or REST). Kind of CRUD over WS. They felt very optimistic about it.

WSs (REST and SOAP) handled by http connector. You point to the endpoint, specify auth type, payload type and format (json, xml, etc) and Integrator handles the rest. There is a simple example in demo called “Save my GitHub repos into the Excel”. Do you think the message in the web site is not clear?

Well, in reality you cannot update one table without touching a bunch of others. But interesting use-case indeed.

I think the biggest pain points for db<->ws integration are change replication and ability to push data to the “integration service” (in opposite to pulling from the db). We natively support first using “change replication” flow and we are working on “listeners” to support the second.