Low-code with Linx 


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

What makes Linx different

A common concern for programmers considering low-code tools is the lack of flexibility. Most low-code tools are based on a workflow paradigm. Linx differs by following a programming paradigm, making it more of an all-rounder and easy for developers and IT professionals to pick up.

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.

Building applications with Linx

Linx abstracts programming concepts so our tools naturally work like common programming tools. The Linx Designer is an IDE that allows you to program and debug at a higher level and saves the program specification to files deployed to one or more Linx Servers to run the application. 

Building solutions in Linx should be no different to how you would do it with low-level programming, it’s just with bigger pieces, more visual help and lots of ready-made functionality available on the server-side.

Linx FAQs |  Main concepts

Linx compliments 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 for

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 platforms

Mendix, Outsystems

Linx vs. 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.

Working in low-code allows you to focus on solving the problem rather than spending time on boilerplate code or struggling with low-level programming concerns.  Linx does not hide the technology you’re working with, e.g. when working with a SQL database you still need to write SQL and have a connection string, but makes it easier to use the technology and discover its features.


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 have used the selected tech before. Challenging for programmers that haven’t.

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 debug it in real-time.

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 is required to implement.

Decide what tooling to use, build it into the code, set up the dependencies.

Time spent: Hours to days.