frankgrecojr

About time someone does this.

You should take a look at Superblocks. I think you'll find our building blocks both flexible and extensible to solve you use cases.

Our of curiosity, which specific point does it violate? Would it help to remove the "Show HN: " prefix?

Another way to maybe approach this is to consider programming constructs that are "hard" to understand. Imagine you want to "do n things in parallel". If your company uses Java (or any language where it's no trivial to do concurrency), this is not straight forward. A visual way to do this makes it much easier.

Perhaps. Those who want to do that can leverage our Javascript and Python blocks to write whatever code they'd like.

Most of our platform is centered around "integrations". For example, You'd have a visual block for an S3 integration (that would have been previously configured) that you'd use rather than initializing an S3 client in code for example.

We want to meet people where they're at though. If you want to write code, you can do that but if you want to use a more visual approach, you can do that as well.

Superblocks can absolutely be used to build something to solve this use case.

Each one of these "APIs" has a json/yaml DSL that could be constructed with any builder pattern. We just haven't released a public API for this yet.

The UI executes APIs against this agent which talks to Superblocks to fetch API definitions to run. These definitions will be "signed" by a key that only the agent is the authority of so customers can guarantee that it hasn't been tampered with.

Thanks for this! I personally wrote a significant portion of this feature am very excited about this new tech!

Unfortunately we require email to signup but have a free trial. Users are able to test end to end in just a few clicks.

We provide an agent deployment model that allows your data to never leave your network. We do not however offer an air-gapped solution.

Superblocks, Retool, and Airflow provide different approach to solve similar problems. We've found that lots of customers prefer Superblocks.

n8n AFAIK is a workflow builder whereas at Superblocks, we are an Application builder (in addition to a workflow builder). We enable developers to build user interfaces that "bind" to APIs that they build with this feature.

TIL! That syntax reminds me of Ruby a little bit.