[fasteo]

I see the "visual" aspect of the low-code movement in the frontend, but not on the backend.

For the backend, my pain point is setting up a whole project for a small task (for example, I need to process a webhook from provider X; it is just saving some fields of the payload to a given DB table). In this case, I would prefer a "platform" to quickly code and deploy these tasks.

The value here is not the ease of coding, but the ease of spinning up a new project and having some basic development services available (versioning, JSON parsing, orm, some form of temporal storage, some form of cache, maybe some work queue mechanism, ability to run periodic jobs, etc) glued together in a consistent API available in some scripting language (Javascript, Lua). On top of this, basic DevOps features (deployment, observability, monitoring, etc).

Just my 2 cents.

Congrats on the launch!

[ushakov]

I see it the same way. Instead of no-code, give me a framework with batteries-included that allows me to start and iterate faster

Temporal, trigger.dev, encore.dev and SST are the one’s I look up to

[troebr]

I can confirm, we use Temporal and used Tray.io for a bit. They're not operating at the same level at all, Tray/Zapier kind of drag and drop wire things together can be great to solve some quick pain points, but I would not build a product on top. Temporal has been great, it's also allowed us to significantly simplify our infra around workflows and made it a lot easier to understand what's going on, especially when things go wrong.

[cschreiber]

Thank you for your insights & appreciate the suggestions!

We absolutely agree that a large part of the value prop is about the ease of the project setup and deployment rather than just simplifying the coding process.

That said, we do believe that the visual aspect brings benefits to backend development as well. While traditional coding requires a level of abstract thought to envisage data flow and logic, visual tools offer a concrete representation that can make this process more intuitive. This can help developers to better understand and manage complex workflows, data relationships, and API structures, which in turn can boost productivity and reduce errors.

Additionally, our hypothesis is that it offers a way for non-technical team members like PM & BI roles or even clients, to contribute more effectively. By visualizing workflows, logic, and data models, people can improve communication, minimize misunderstandings, and contribute to a better final product.

However if you still prefer coding, we have a Custom Code Action on the roadmap that will let you do exactly that and still benefit from some of the guardrails we provide.