Low-Code/No-Code in 2026: Where the Platforms Actually Stand

The low-code/no-code pitch hasn't changed in a decade: let people who aren't developers build software. What has changed is the scale. Estimates for the global low-code/no-code market in 2026 range from $48.9 billion to $65 billion depending on methodology (ToolJet, Fortune Business Insights via ToolJet), and 77% of enterprises now report using at least one low-code or no-code tool, up from 65% in 2024 (ToolJet). That's a 12-point jump in a single year — the kind of adoption curve that usually means the category has moved from "experiment" to "default."

This piece looks at what's actually driving that curve, which platforms are winning which use cases, and where the real risk sits — because the growth numbers tell only half the story.

The adoption numbers, unpacked

Aggregate adoption stats hide a lot of variance by sector and company size. Financial services leads at 82% adoption, followed by healthcare at 74% and retail at 71% (ToolJet) — largely because these industries face constant regulatory-driven app requirements (new compliance workflows, disclosure forms, audit trails) that don't justify a full engineering sprint each time. SMB adoption sits lower, at 58% (ToolJet), which tracks: smaller companies have less internal app backlog to begin with.

At the application level, 70% of new applications built by organizations in 2026 now use low-code or no-code technology, up from under 25% in 2020 (WebSearch synthesis, ToolJet data). That's the more meaningful number — it's not about how many companies dabble, it's about what fraction of new software is being built this way.

Why now: the citizen developer numbers

The "citizen developer" concept — non-engineers building internal tools — has gone from buzzword to headcount category. There are an estimated 16.2 million citizen developers globally, a 38% year-over-year increase, with the population projected to exceed 25 million by 2028 and outnumber professional developers 4:1 inside large enterprises (ToolJet).

Who are they? Mostly operations managers (24%), marketing managers (19%), and sales managers (16%) (ToolJet) — people close to a workflow pain point who used to file a ticket and wait. The average citizen developer now ships 4.3 applications a year (ToolJet).

The business case IT leadership uses to justify this: 87% say no-code/low-code tools directly help address developer talent shortages (WebSearch synthesis), and Gartner's often-cited forecast has 80% of technology products built by non-developers by 2026.

What the platforms actually do differently

"Low-code/no-code" is not one category — the platforms split hard by workload:

This split matters because a lot of the market noise conflates "no-code app builder for a founder's MVP" with "enterprise low-code platform for a regulated bank." They serve almost opposite audiences.

AI has changed what "low-code" means

The bigger shift in 2026 isn't drag-and-drop UI builders — it's AI-generated application code sitting underneath the low-code layer. 72% of low-code/no-code platforms now integrate AI features, and 58% of developers use AI-assisted development inside these tools (ToolJet). Some platforms can generate a working application prototype from a natural-language prompt in under five minutes (ToolJet).

Gartner's forward-looking number is the one to watch: by 2028, 45% of new application code is projected to be AI-generated (ToolJet). That reframes low-code platforms less as "form builders" and more as governance layers wrapped around AI code generation — the citizen developer describes what they want, AI drafts it, the platform enforces guardrails (data access, deployment permissions, audit logging) around the output.

83% of enterprise CIOs say they plan to increase spending specifically on AI-enhanced low-code tooling (ToolJet), and the "intelligent automation platform" sub-segment is already valued at $12 billion on its own (ToolJet).

The ROI case, and where it's real

The productivity numbers vendors cite are large enough to be suspicious, but they come from aggregated industry surveys rather than single-vendor marketing decks:

• 74% faster time-to-market; average project timeline of 3.2 weeks versus 14.8 weeks for traditional development (ToolJet)
• 62% decrease in development costs, with 342% three-year ROI and a 6–9 month payback period (ToolJet)
• 50% reduction in IT backlog when business teams self-serve simple applications (ToolJet)
• 40% lower ongoing maintenance costs for low-code/no-code apps (ToolJet)

These numbers are real for the workload they're measured against — internal forms, workflow automation, data collection, dashboards. 58% of organizations use low-code specifically for forms and data collection, 49% for workflow automation, 42% to replace spreadsheets/paper processes (ToolJet). That's the sweet spot. Custom UI development is the least common use case at 22% (ToolJet) — which tells you where the platforms still fall short of hand-written frontend work.

What's actually going wrong

The governance side of the citizen developer boom is where 2026 gets more honest than the pitch decks:

Other friction points reported by IT and engineering leadership:

• 47% worry about platform scalability limitations as app requirements grow past the initial use case (ToolJet)
• 37% are concerned about vendor lock-in and migration difficulty if they need to leave a platform (ToolJet)
• 32% question whether the platform can handle genuinely complex application logic (ToolJet)
• 25% report application security gaps specific to low-code-built apps (ToolJet)
• 43% cite a lack of internal expertise to deploy and govern these platforms properly (ToolJet)

The response has been formal governance programs: 78% of IT departments now maintain a formal citizen developer policy (ToolJet) — access controls, approved-platform lists, and review gates before a citizen-built app touches production data. That's up sharply from a few years ago when "citizen development" mostly meant nobody was watching.

The decision framework that actually holds up

Strip away the vendor comparisons and the choice comes down to three questions:

1. Who's building it? A non-technical operations lead needs Bubble-class no-code. An engineer building internal tooling wants Retool or Appsmith. Neither should be forced into the other's tool.
2. What's the blast radius if it breaks or leaks data? Customer-facing or regulated workflows justify OutSystems/Mendix-grade governance and cost. Internal dashboards don't.
3. Do you have a governance policy before you have adoption? The 61% shadow-IT concern stat exists because most organizations let adoption outrun policy. Writing the access-control and platform-approval policy before rollout, not after the first data leak, is the cheapest insurance in this category.

Takeaway

Low-code/no-code isn't a fad plateauing — it's infrastructure now, with 70% of new enterprise applications built this way and AI code generation actively increasing the tools' reach rather than eating their business. But the platforms that will hold up in a governance review five years from now are not the ones with the flashiest AI demo; they're the ones matched correctly to who's building and what's at stake if it fails. Pick the platform for the builder and the blast radius, not for the market-share headline.

Sources: ToolJet — Low-Code Statistics 2026, ToolJet — Low-Code Development Platforms Statistics and Trends 2026, Guideflow — 12 Best Low-Code Development Platforms for 2026