Wondering whether low-code no-code platforms are worth it for your team? They can speed up simple apps and workflows, but they work best with IT oversight, training and clear governance rules.
This guide sits within the wider topic of business technology.
| Item | Value |
|---|---|
| Where no-code platforms sit on Gartner’s Hype Cycle for Digital Workplace Applications | Peak of Inflated Expectations (report published 19 May 2026) |
| Market penetration of no-code platforms in their target audience | 5 to 20 percent |
| Citizen developers versus professional developers in large enterprises (Gartner estimate) | 4:1 |
| No-code/low-code platforms in use in the average enterprise | 3.4 |
| Typical wait for internal tool requests in enterprise IT departments | 6 months or longer |
The figures come from Kissflow’s summary of Gartner’s 2026 Hype Cycle and from Automation Atlas. They can change, so check the sources before you rely on them.
What low-code and no-code platforms actually do
Citizen development is the practice of building applications and automations with low-code or no-code tools by employees who are not professional software engineers, according to Automation Atlas. Typical builders are operations managers, business analysts and marketing specialists.
Gartner, as summarised by Kissflow, defines a no-code platform as development technology for business technologists and citizen developers to build business solutions, including AI agents, without interacting with code. Low-code tools sit one step closer to traditional development because they allow optional code.
Automation Atlas groups the tools by type and, as of May 2026, gives these neutral examples:
- Workflow automation: Power Automate, Zapier and Make, used for connecting apps and automating repetitive tasks.
- App builders: Airtable, Notion and Monday.com, used for internal databases and project trackers.
- Low-code platforms: Retool, Appian and Mendix, used for internal tools with optional code.
- Form builders: Fillout, Typeform and Google Forms, used for data collection with automated routing.
The main advantages
The first benefit is speed. In a CIO.com report from May 2021, Schneider Electric’s Jamie Locks named speed to market as the first advantage, noting that work handled by a central development team can stretch out for a long time.
The same report says business units adopt tools more readily when they build what they themselves need. Locks adds that it lets IT focus on things that add value instead of being caught in the middle of small requests.
Backlogs are the second driver. Automation Atlas says enterprise IT departments commonly report 6-month or longer wait times for internal tool requests, and citizen development aims to close that gap while IT keeps oversight of security and architecture.
The main drawbacks and risks
The same CIO.com report quotes Gartner analyst Jason Wong on the downside: security and business risks, plus problems with maintaining projects, technical debt and manageability. Ungoverned use invites the same problems as shadow IT.
Automation Atlas lists the common governance failures:
- Credential exposure: builders may hardcode API keys into webhooks or share credentials in plaintext.
- Data leakage: automations may move sensitive data to unauthorized third-party services.
- Orphaned automations: when builders leave or change roles, their work becomes unmaintained.
- Duplication: several departments may build overlapping automations for the same process.
Security review is also harder than it looks. The Intelligent Automation Network notes that most low-code tools use proprietary languages, frameworks and libraries, which can be hard to analyse for hidden vulnerabilities even for security experts.
Where do no-code platforms sit on the hype curve?
As of Gartner’s Hype Cycle for Digital Workplace Applications, published on 19 May 2026, no-code platforms sit at the Peak of Inflated Expectations. Kissflow’s summary adds a High benefit rating, Emerging maturity and market penetration of 5 to 20 percent of the target audience.
In the same report, citizen application development platforms sit on the Rise, with a High benefit rating and Adolescent maturity. Gartner defines them as products that let non-IT employees use IT-sanctioned tools to create and maintain small-scale business applications.
The warning inside the report is the useful part. Gartner says inconsistent governance and misuse have given no-code a reputation for fragile implementations, and that adoption driven without IT oversight leads to redundant point solutions. Kissflow is itself a low-code vendor, so read its commentary with that in mind.

How to govern citizen development
A common myth is that these tools need little or no involvement from IT. The Intelligent Automation Network argues the opposite and says governance teams should include experts from IT, security and business unit heads.
Automation Atlas describes three governance models:
- Centralized: IT reviews and approves all citizen-built automations, which suits highly regulated industries such as finance and healthcare.
- Federated: IT sets guardrails and standards while departments build independently, which suits mid-to-large enterprises with mature IT governance.
- Hybrid (tiered): low-risk automations deploy freely and high-risk ones require IT review.
The same source lists practices that apply to any model:
- Establish a Center of Excellence that sets standards, provides training and monitors activity.
- Limit approved platforms to 2-3 tools to prevent tool sprawl. The average enterprise already has 3.4 in use across departments.
- Route all API keys and OAuth connections through a managed credential store, not individual accounts.
- Require basic training on security, data handling and platform best practices before granting builder access.
- Review active automations in quarterly audits for security issues and orphaned workflows.
- Define clear criteria for when a citizen-built solution is handed off to professional IT development.
Schneider Electric shows the approach in practice. According to CIO.com, its professional developers built their own competence first and recruited citizen developers only afterwards, and 150 people were trained on OutSystems with 95 projects deployed at the time of the report.
Detailed code and security reviews are run before anything reaches production, and the citizen developer then becomes the first line of support for the app, not IT. Choosing platforms is easier once you understand what is enterprise architecture and how apps fit the wider system landscape.
When to use them, and when to hand off to IT
These tools fit work that is worth automating but too small for formal development. CIO.com describes staffing firm Guidant Global as having some work that is ripe for automation, but not at the scale where formal application development makes sense.
Hand a project to IT when the stakes or integrations grow. Gartner warns, via Kissflow, that integration with on-premises systems and cloud compliance is essential, and that leaders must enforce quality controls, checkpoints and segregation of duties.
Departments also differ. The Intelligent Automation Network says highly regulated departments such as finance and HR may need tighter controls than sales or marketing.
Once an app is live, judge it on results rather than enthusiasm, using the habits covered in data-driven decision making.
Frequently asked questions
What is the difference between low-code and no-code?
Show answer
No-code platforms let users build solutions without interacting with code, as Gartner defines them in the summary by Kissflow. Low-code platforms allow optional code, according to Automation Atlas.
Is citizen development the same as shadow IT?
Show answer
No. WeWeb, a no-code vendor, describes citizen development as a sanctioned, governed activity, while shadow IT means building or using technology without IT’s knowledge or approval.
Do these platforms remove the need for IT?
Show answer
No. The Intelligent Automation Network calls the idea of little or no IT involvement a pervasive myth, and Schneider Electric still runs reviews before production.
How many platforms should a company standardize on?
Show answer
Automation Atlas suggests limiting approved platforms to 2-3 tools to prevent sprawl and simplify governance. The right number depends on your own governance capacity.



