What is low-code?
Last reviewed 7 October 2026
Low-code is an approach to building applications and automations mostly with visual tools, such as drag-and-drop designers, prebuilt components and templates, while still letting developers add their own code where the visual tools fall short. IBM describes it as building applications with minimal hand coding. It sits between traditional programming and no-code tools.
Also called: low code, low-code development, low-code platform, LCAP.
Why Low-code matters
Most business software requests are variations on familiar patterns: a form, a table, an approval, a report, a sync between two systems. Writing each one from scratch ties up developers on work that is mostly plumbing. Low-code platforms supply that plumbing as configurable blocks, so a small team can deliver more of those requests and spend hand-written code on the parts that are genuinely specific.
It changes who can build, too. Technically minded analysts can assemble a working tool and hand a developer only the step that needs code, which shortens the queue between a business need and a working answer.
How it works
A low-code platform provides a visual designer, a library of components (screens, data tables, connectors, workflow steps) and a runtime that hosts the result. You assemble the application by placing components and configuring them, and the platform generates and runs the underlying code.
What makes it low-code rather than no-code is the escape hatch. Microsoft's documentation for Power Apps illustrates it: makers build apps visually, while developers can extend them with code, such as client-side JavaScript, server-side logic, custom connectors and integration through webhooks. The visual part covers the common case; code covers the rest.
The platform also handles deployment, hosting, access control and connections to data sources. That is much of the value and much of the risk, because you depend on the vendor's runtime, its pricing and its roadmap. IBM lists reduced control and vendor lock-in among the limits of low-code, alongside shadow IT when tools spread without oversight.
Worked example: an equipment booking tool
A facilities team needs a way for staff to book shared equipment, see availability and get a reminder before the return date. In a low-code platform, an analyst creates a data table for equipment and bookings, builds a booking screen from form and calendar components, and adds a workflow step that sends a reminder a day before the return date.
One requirement does not fit the visual blocks: bookings must check a maintenance schedule held in an older internal system that has only a custom API. A developer writes a small custom connector for that API, the analyst drops it into the booking flow, and the rest of the tool stays visual and easy for the facilities team to change.
How Swfte relates to it
Built in the product
Studio is a visual builder for agents and workflows: you lay out steps, branches and loops on a canvas and connect tools from the integrations catalogue. Where the canvas and catalogue do not reach a system, a workflow can call it through the HTTP request integration, and an API for custom systems is listed on the Team tier.
Studio is built for automations and agents, not for building general business applications with their own screens and data tables. If you need custom internal apps with a user interface, a low-code app builder is the better fit, and Studio can sit behind it running the workflows.
Related terms
- No-code
No-code refers to building applications and automating business processes entirely through visual tools, such as forms, drag-and-drop canvases and prebuilt connectors, without writing any programming code.
- Workflow
A workflow is the ordered set of steps that takes one piece of work, such as a purchase request or a support ticket, from the event that starts it to a finished outcome.
- Automation tools
Automation tools are software products that carry out tasks or whole processes with minimal human input, from sending a scheduled report to coordinating work across several systems and teams.
- Workflow automation
Workflow automation is the use of software to run the steps of a repeatable process, such as passing data between systems, assigning tasks and requesting approvals, according to defined rules instead of by hand.
- Process automation
Process automation means using software to carry out the repeatable steps of a process, so they run the same way each time without someone doing them by hand.
Common questions
- What is the difference between low-code and no-code?
- Both use visual builders and prebuilt parts. No-code aims at users who will never write code, so everything must fit the visual tools. Low-code assumes some users can code, and lets them extend the platform with scripts, custom components or connectors. IBM frames low-code for developers and technical users, and no-code for business users.
- Who uses low-code platforms?
- Professional developers use them to skip repetitive setup work, and technically minded business analysts use them to build tools for their own teams. In many organisations the work is shared: analysts build most of an application visually, and developers supply custom connectors or logic for the few parts that need code.
- What are the risks of low-code?
- Vendor lock-in is the main one, because applications are hard to move off the platform. Others are reduced control over performance and behaviour, costs that grow with users or runs, and shadow IT when teams build tools without security review. Decide who can publish, which data sources they connect, and how apps are reviewed.
- Is low-code suitable for enterprise applications?
- For many internal tools, workflows and integrations, yes, provided IT sets guardrails on data access, environments and publishing. For products sold to customers, systems with heavy performance needs or software with intricate domain logic, teams usually prefer conventional code, sometimes with low-code tools around the edges.
Sources
Definitions on this page were read on the sources below on 7 October 2026. Where sources define the term differently, the page says so. The full glossary lists more terms.
- IBM explainer on low-code (read 2026-10-07)
- Microsoft Learn overview of Power Apps (read 2026-10-07)