Low-code with Linx 

Low-code means many things to many people. Various tool types exist under this umbrella term: website generators, form builders, API connectors, database builders, workflow automation, and more, each targeting different domains and requiring varying levels of technical proficiency. The only common theme is that they have a graphical user interface that enables a user to build and/or configure something.

What is Linx

Linx is a general-purpose low-code platform for building backends like APIs, automations and integrations. It is an abstraction of programming itself and not domain, process or tooling specific. This means it can be used for any backend application in any domain with no limitations on connections to other tools and services.

What makes Linx different

The use of a programming abstraction makes Linx extremely powerful. It is not constrained by a domain or use-case driven paradigm and is often used in conjunction with other low-code tools to provide the API or integration services that those tools are not designed for.

How does Linx compare with other low-code tools

Low-code tools that can be used to build APIs, automations and integrations fall into several broad categories. Most low-code tools make working in a specific domain very easy but have difficulties working with systems and concepts that do not form part of the main use-case the tool was designed for. Linx can fill the gaps when domain-specific low-code tools hit their limits.

Tool Category

Example Tool

Best Use Case

Not Suitable For

Combine with Linx to do 

General-purpose low-code platform


Building APIs, any backend automation or integration

Building user interfaces


Consumer Application Integration

Zapier, IFTTT

Simple automations by non-technical users

Anything slightly complex or building APIs

Complex automations or integration with legacy or on-premise systems.
Robotic Process Automation
UIPath, Automation Anywhere
Automating business processes by automating the user interface
Automation or integration where APIs are available, Building APIs
Hosting APIs or Microservices for use by the RPA
Business Process Management (BPM)
Kissflow, Creatio
Automating business processes
Integrating systems or building APIs
Hosting APIs or Microservices for use by the BPM. Integration to legacy or unsupported systems or high volume processing
Enterprise Low-code Platform
Mendix, Outsystems
Building applications
Integrating systems or businesses on a budget
Integration to legacy or unsupported systems, building microservices or high volume processing
Enterprise Application Integration
Mulesoft, Boomi
Large scale enterprise integration
Small to medium automations and integrations or getting something done quickly
Integration to legacy or unsupported systems, fast prototyping or high volume processing

Low-code vs pro-code

The development of backend applications – such as APIs, microservices, automations and integrations – is time-consuming, complex and requires highly skilled developers. Linx was designed to enable more developers to build backend applications and to shorten development time.


Low-code (Linx)

Pro code

Getting started

Install Plugins for the functionality you want to use (e.g. REST, Database). Installation is point and click.
Time spent: Minutes.
Select a framework to use and install the dependencies for any additional tech you want to use.
Time spent: Minutes to hours, depending on the technology selected, dependency compatibility and team conventions.
Understanding concepts
Use of Functions, Services and Types.
Ease of use: Easy for anybody with programming experience. It is challenging for non-programmers.
Functions, Types and any concepts the framework or dependencies introduce.
Ease of use: Easy for programmers that’s used the selected tech before. Challenging for programmers that haven’t. Impossible for non-programmers.
Adding functionality
Drag Functions and Services from Plugins to create your own. Fill in properties and use editors to configure them.
Write code. Use the functions and types in the dependencies as building blocks.
Time spent: Hours to days, needs to deal with much more finely grained code, language, framework and dependency concerns.
Hitting roadblocks
Use generic drag-and-drop Functions or code it.
You willl need to code it.
Similar to most programming IDEs with the addition of Function and Service level debugging, e.g. write a Function and then immediately debug it.
Mostly standardised across IDEs.
One-click directly from the IDE, deployed in minutes.
Compile, install on host, run or set up continuous deployment.
Time spent: Hours.
Management, logging & metrics
Built-in as standard, no additional time required to implement.
Decide what tooling to use, build it into the code, set up the dependencies.
Time spent: Hours to days.