•Comparing Arbiter with other automation and integration tools

Examples: Low-code, no-code, RPA(Robotic process automation) etc.

Tools like these allow you to automate arbitrary jobs, connect to APIs, and do a large variety of things with limited development resources. Arbiter is inspired by the problems they solve.

Arbiter similarly uses this approach where developers create applications in a model-driven, drag-and-drop graphical interface, but it goes further by being the first strongly typed and compiled low-code framework. This combined with the built-in composability enables Arbiter to be well-suited for building much more than simple integrations with several nodes. You could create complex backends with hundreds of nodes in a reliable, secure, and maintainable manner and deploy them with confidence that everything will work as expected.

Another well-known problem of other tools is the lack of flexibility and customization options. With the support of built-in serverless functions, you could basically build anything that Arbiter does not support yet.

Regarding integrations, one major selling point of Arbiter, except everything above, is that all of the builtin integrations are created with the same tools that are available to you i.e they are not sandboxed and you can change them, or use them as a learning resource.