A low-code/no-code development platform is software that lets people build applications, forms and automated workflows mostly by arranging visual components, filling in settings and connecting to data, instead of writing code line by line. Low-code tools let professional developers add code where it is needed; no-code tools aim to need none at all, so business staff can build for themselves. Many platforms are sold as cloud services, and many large business software suites include their own low-code tools.
At a glance
- Apps and workflows are built with drag-and-drop designers, templates, rules and prebuilt connectors to other systems.
- Low-code targets developers who want to build faster; no-code targets business users. Many platforms offer both.
- The model lets “citizen developers” (staff outside IT) build their own tools within guardrails IT sets.
- Governance, security and lock-in are the main trade-offs.
- Analysts sometimes use narrower labels, such as low-code application platform; buyers mostly meet the combined low-code/no-code phrase.
What problem it solves
Most IT teams have more requests than people to build them: approval workflows, data-entry forms, simple tracking apps, reports. When IT cannot get to them, teams fall back on spreadsheets, email and personal tools, or buy their own apps without review, a common source of shadow IT.
Low-code/no-code platforms shorten the path from idea to working tool. Developers can build standard business apps faster, and staff closest to a process can automate parts of it themselves, so IT can focus on the systems that need full engineering.
How it works
Visual building. Builders design screens, forms and data models in a visual editor, define logic with rules or flowcharts, and set who can see and do what. Developers can typically extend low-code apps with scripts, custom components or APIs.
Connectors. Platforms usually include prebuilt connectors to common applications and databases, such as email, CRM, ERP and file storage, so an app can read and write data elsewhere. Some overlap with integration platforms (iPaaS) and workflow automation tools, and some include robotic process automation (RPA) for systems without APIs.
Hosting. Most platforms run as a cloud service, with the vendor hosting the apps, much like PaaS; some can also be deployed on your own infrastructure.
Citizen development and governance. A typical model has IT choose and configure the platform, set data policies and environments, and define which kinds of apps business users may build. Higher-risk apps go through review, and IT keeps an inventory of apps, builders and the data they touch. More organizations now also use AI assistants inside these platforms to generate app screens, logic or formulas from plain-language descriptions.
When it matters for buyers
- When the IT backlog blocks the business. Low-code can clear many small requests, especially workflows and forms around existing systems.
- When a suite you already own includes it. Products in the Microsoft 365 ecosystem, CRM and ERP platforms often include low-code tools, which changes the build-or-buy math. See our Microsoft 365 solutions for how licensing tiers can affect what is included.
- When citizen-built apps start to multiply. Without an inventory and ownership rules, apps that run real processes can break or lose data when their builder leaves.
- When an app becomes critical. Apps that outgrow a team may need to be rebuilt, moved under IT support or licensed at a different tier.
Questions to ask vendors
- How is the platform priced (per user, per app, per builder, by usage), and what happens to cost as an app spreads to more users?
- Which connectors are included, and which require premium licenses?
- What admin controls exist for data policies, environments, app approval and an inventory of apps and builders?
- How do apps authenticate to other systems, and can connections avoid relying on one person’s credentials?
- Can we export our apps, logic and data, and in what form, if we leave?
- What audit logs, version control and testing tools are available?
- Where is the platform hosted, and which security reports and certifications cover it?
How it differs from robotic process automation (RPA)
Robotic process automation (RPA) uses software bots to mimic people clicking and typing in existing applications, usually to automate repetitive tasks in systems that lack APIs. A low-code/no-code platform is for building new applications and workflows, with their own screens, data and logic. The two often meet: many automation suites include both, and hyperautomation programs commonly combine them. The question to ask is whether you need a new app or need to automate work inside apps you already have.