Top 30 Low-Code & No-Code Development Platforms 2027

This report forms part of The Economy Rankings’ Software & Digital Platforms portfolio. This edition evaluates active named software platforms, with the operating provider identified separately from the product.

Low-code and no-code development platforms connect a business requirement with a working application through visual construction and supported extension. Their economic role extends beyond producing an interface quickly. The resulting software needs a coherent data model, appropriate user actions and an operating arrangement that allows the organization to maintain it after the first demonstration.

This ranking evaluates visual builders for business applications and integrations. Website templates without substantive application behaviour and custom development agencies without their own qualifying platform are outside the series. The named product is the unit of assessment, with the operating provider identified separately. A diversified parent’s scale does not establish the technical merits of its application builder.

The market includes enterprise development suites, process-centred platforms, internal-tool builders, database applications and visual web or mobile development environments. Their scope differs. A builder designed for internal operations may emphasize data-source connections, while a mobile-oriented platform needs an explicit route from visual design to deployment. The comparison preserves those distinctions rather than assuming all applications require an identical architecture.

The 2027 edition reflects information reviewed by 22 October 2026. Five leading platforms are ordered in Tier I, with ten established offerings alphabetically in Tier II and fifteen focused or specialist offerings alphabetically in Tier III. Scores are weighted editorial assessments of documented capability and operation. The review does not claim a common development-speed benchmark or observed results in the future edition year.

Market Overview

Application construction connects several responsibilities that remain important even when the interface is visual. A record needs a definition, an action needs authority and a user needs an appropriate view of the information. The strongest evaluation follows those relationships through an actual proposed application. A demonstration of dragging components onto a screen is useful, but it does not establish the complete data and operating model behind the interface.

Professional extension is a meaningful source of differentiation. Some platforms support substantial custom code or generated-code maintenance, while others emphasize construction within a more bounded managed environment. Neither approach is automatically superior. The relevant question is whether the organization can implement its required behaviour and maintain the resulting components without losing a clear boundary between platform services and custom engineering.

Enterprise governance matters as development becomes more distributed. Business users may understand a process while technical teams understand integration and operational requirements. A coherent platform lets those responsibilities work together. Permissions, environments, deployment and application ownership need an identified operating model; visual convenience does not remove the need to decide who can change production software and how a change is reviewed.

Internal-tool and database-oriented builders address applications that work directly with organizational records. Their interfaces may be simple while the permissions behind them are consequential. A button can trigger a change in a connected system using an account with substantial authority. Data-source settings, user access and application logic therefore need to be examined together rather than treated as independent configuration details.

Web and mobile no-code builders broaden participation in application creation, but their eligible role here is substantive software. Portals, record-based tools and recurring operational applications qualify where their data and user behaviour are clear. A static template alone does not. The ranking also keeps the application platform distinct from an agency selling a finished bespoke project without a maintained development environment.

Industry Trend — 2027

For 2027, visual development increasingly combines AI-assisted construction, shared business data and professional extension. The useful comparison remains the application that can be built and maintained: how its records are represented, what its users can do and which party remains responsible for the operating environment and custom components.

2027 market development	Current evidence and direction	Implication for the sector
Visual construction with professional extension	Platforms combine modelled interfaces with code, APIs or supported extension routes.	Buyers should identify what the platform manages and what their own engineers maintain.
Governed distributed development	Enterprise products document application settings and administration.	Application ownership and production-change responsibilities need an explicit model.
Data-connected internal applications	Builders connect interfaces to databases and enterprise services.	User permissions and connected-account authority must be examined together.
Web and mobile application routes	Products support different paths from visual construction to deployment.	The target runtime, back-end services and distribution requirements should be confirmed.
Current suite and product boundaries	Providers combine tools and retire or rebrand standalone offerings.	Evidence must support the maintained named product rather than an outdated module.
AI-assisted building	Assistants appear around application design and logic generation.	The resulting application still needs review, access rules and a maintainable operating arrangement.

These directions make an application walkthrough more informative than a claim about the amount of code avoided. A buyer should follow a representative record through user interaction, an authorized action and a later application change, including the effect on existing data. That exposes engineering and governance requirements that an attractive initial prototype may leave unresolved.

The appropriate platform depends on the application, existing systems and the organization’s maintenance capacity. A focused internal-tool builder and a broad enterprise development suite can both be credible choices. Their value should be assessed through documented scope and the actual delivery arrangement rather than app counts, provider prominence or an assumed universal productivity improvement.

Methodology — Core Eligibility Criteria

The ranking uses an evidence-based editorial assessment tailored to this technical market. Candidates were required to satisfy the following core conditions:

• Visual application builders for business applications and integrations.
• A named active product with an identifiable operating provider and inspectable current technical or product documentation.
• Substantive organizational workflows rather than a demo, inactive brand, wrapper, reseller or implementation-only consultancy.
• The product is evaluated separately from a diversified parent company’s reputation and unrelated business lines.
• Related brands under one operator are grouped; acquisitions, rebrands and supported legacy product boundaries are reviewed.
• Headquarters or current business-location and founding facts identify the provider, steward or expressly labeled product lineage.
• International comparison without geographic quotas; regional availability and deployment dependencies are qualified.
• The review uses material available by 22 October 2026; the 2027 edition does not claim observed future results.

Methodology — Ranking Factors

• Product capability and functional depth — 30%: Visual modeling of application data, interface and business logic; runtime and extensibility sufficient for identifiable business applications.
• Documented enterprise utility and deployments — 25%: Named application deployments and inspectable builder/runtime examples; app counts and demos alone do not establish enterprise efficacy.
• Reliability, security and integration — 20%: Authentication/authorization, data connectors, development environments and governed deployment/integration boundaries.
• Implementation ecosystem and ongoing support — 15%: Builder documentation, reusable modules, code escape routes, developer lifecycle and maintained learning/support resources.
• Transparency and operating governance — 10%: Accountable platform operator, licensing/runtime/deployment terms and explicit limitations on portability and plan features.

The five criteria carry weights of 30%, 25%, 20%, 15% and 10%, respectively. The private research record documents criterion-level editorial assessments and supporting sources. These are judgments about the documented offering, not scores from laboratory tests performed by The Economy Rankings. Missing material evidence is pursued before selection rather than silently treated as average performance. Licensing, sponsorship and likelihood of purchasing recognition do not influence eligibility, scores or tier placement.

Company Profiles and Further Reference

Names appearing in this ranking are linked to their corresponding organizational profiles in The Economy Wiki, where available. These profiles provide further background on principal activities, technology capabilities, product and service portfolios, market positioning and related rankings and analysis across The Economy Network.

Where an entry identifies a product or service line, its provider or operator is identified so that the scope of the organizational profile is clear. The Economy Wiki profiles are maintained as editorial reference pages and may be updated as new public information becomes available.

---

Tier I — Leading Low-Code & No-Code Development Platforms

1. Microsoft Power Apps

• Provider / operator: Microsoft
• Headquarters: Redmond, Washington, United States
• Provider founded: 1975 (Microsoft)

Microsoft Power Apps supports visual business application development through canvas and model-driven approaches within Power Platform. The named builder is evaluated separately from Power Automate, Dynamics applications and the provider’s infrastructure services. A visual application builder is useful when the interface, data and actions form a maintainable business application. Convenience during initial construction is only part of the development lifecycle.

Teams can connect an application interface with business data and configure the user actions appropriate to its records, then administer the chosen environment through the relevant platform controls. Canvas and model-driven applications provide different construction routes within the named builder, making the proposed application architecture a concrete implementation choice. Microsoft maintains application, data and governance documentation. The evaluation follows how a configured application is tested, administered and connected to the systems it uses.

Its substantial application-building scope and enterprise administration support a leading position. Connectors, data services and licensing should be checked for the actual solution. Its standing reflects documented application-building depth and governance, not an assumed development-speed advantage.

2. OutSystems

• Provider / operator: OutSystems
• Headquarters: Boston, Massachusetts, United States
• Provider founded: 2001

OutSystems provides enterprise visual application development with professional extension and lifecycle capabilities. Its evaluated role includes constructing and operating business applications rather than supplying only page templates or an external development agency. Enterprise applications need clear relationships between the user interface, business rules and the underlying data model. A low-code environment should make those relationships understandable to its maintainers.

Development teams can model application behaviour and interfaces, connect enterprise data and examine the security configuration required for the deployed solution. Application-security guidance gives reviewers a product-specific route to examine permissions and deployment requirements beyond the convenience of visual construction. OutSystems publishes application-security and development guidance for its product environments. Developers and administrators should identify which changes the platform supports directly and where custom code or another service remains responsible.

Its developed application lifecycle and extension model support a leading position. Documentation for different product generations should be matched to the exact environment proposed. Recognition concerns the actual development environment and its supported operating boundaries.

3. Mendix

• Provider / operator: Mendix / Siemens
• Provider headquarters locations: Boston, Massachusetts, United States; Rotterdam, Netherlands
• Provider founded: 2005 (Mendix)

Mendix provides visual application development within Siemens’ software portfolio. The named Mendix platform combines application modelling, data and professional extension rather than inheriting the technical standing of the parent’s unrelated industrial products. Development governance becomes important when several teams build applications on a shared platform. Identity, permissions and deployment arrangements affect the application after its first demonstration.

Teams can construct a business application and define the interfaces and permissions through which users interact with its records. The security reference connects application behaviour with the development model, helping teams examine how users and their permitted actions are represented. Mendix publishes developer references and detailed application-security guidance. The practical review includes a change to a live application and the responsibilities of the people authorized to make it.

Its substantial enterprise development environment supports a leading placement. The deployment, extension components and operating responsibilities should be identified for the application being built. The product is assessed through documented provision rather than a claim that visual design eliminates engineering work.

4. Salesforce Platform

• Provider / operator: Salesforce
• Headquarters: San Francisco, California, United States
• Provider founded: 1999 (Salesforce)

Salesforce Platform supports configurable business applications through Salesforce’s data, interface and extension environment. The evaluated platform is distinct from separately packaged Sales Cloud, Service Cloud and marketing applications. Business application development requires more than an attractive page. Shared records, user actions and access rules give a deployed tool a continuing operational purpose.

Teams can model records and user interaction and combine visual tools with professional development where the application requires a supported extension. The platform’s visual and professional development resources identify an extension model around the same enterprise records used by the resulting application. Salesforce publishes low-code, developer and application-security resources. A useful evaluation follows an actual record through creation, review and change by users with different responsibilities.

Its detailed enterprise data and extension framework supports a leading position. The actual platform edition, application entitlements and custom components determine the solution’s operating scope. The recognition concerns that substantive application workflow rather than a website template alone.

5. ServiceNow App Engine

• Provider / operator: ServiceNow
• Headquarters: Santa Clara, California, United States
• Provider founded: 2004 (ServiceNow)

ServiceNow App Engine provides visual enterprise application development around ServiceNow’s record and workflow foundation. App Engine Studio and application-development governance give the named offering a defined builder and administration context. Data-connected applications participate in systems that already have their own records and permissions. The builder must make the intended interface and authority understandable.

An organization can create an application that connects business records, interfaces and process steps while assigning responsibility for how the resulting application is developed and maintained. App Engine Studio documentation identifies the builder, while governance resources address the organizational responsibilities surrounding development on the shared platform. ServiceNow maintains App Engine Studio and governance guidance. Connection settings and application logic should be reviewed together so a convenient interface does not obscure responsibility for the resulting change.

Its developed enterprise application model supports a leading position. Separately licensed platform services should be identified instead of inferred from the provider’s broader portfolio. Its assessed contribution is the maintained development environment and its documented integration scope.

---

Tier II — Established Low-Code & No-Code Development Platforms

(Alphabetical order)

Appian

• Provider / operator: Appian
• Headquarters: McLean, Virginia, United States
• Provider founded: 1999

Appian connects low-code application construction with process and data functions. Its evaluated development scope includes the interfaces and records supporting a business workflow, separately from using the platform only as a process-design illustration. An application platform can combine visual construction with professional extension. Those approaches serve related needs when the resulting code, interfaces and data remain supportable over time.

Organizations can configure an application around a recurring process and examine how users act on shared business information through the resulting interface. Current application-settings documentation provides an inspectable configuration context for the low-code application and the people responsible for maintaining it. Current Appian documentation covers application settings and development. The implementation should preserve an explicit boundary between platform-managed behaviour and the custom components maintained by the organization.

Its coherent process-and-application architecture supports an established position. The selected data sources, runtime and custom extensions still require an explicit delivery model. Its placement recognizes that development model without promising identical flexibility for every application type.

Creatio Studio

• Provider / operator: Creatio
• Headquarters: Boston, Massachusetts, United States
• Provider founded: 2014 (current provider origins)

Creatio Studio provides no-code application design with records, user interfaces and process configuration. Its eligible development role remains separate from the provider’s separately packaged CRM and other business applications. Development governance becomes important when several teams build applications on a shared platform. Identity, permissions and deployment arrangements affect the application after its first demonstration.

Teams can create an application that connects shared information with the sequence of actions users perform, while administrators review the platform’s extension and security model. Platform and developer guides describe the application environment itself, preserving the distinction between custom construction and separately packaged Creatio business applications. Creatio Academy publishes developer guides and platform documentation. The practical review includes a change to a live application and the responsibilities of the people authorized to make it.

Its connected data-and-process application proposition supports recognition. Configured application functions should be established directly rather than inferred from the breadth of the provider’s CRM portfolio. The product is assessed through documented provision rather than a claim that visual design eliminates engineering work.

Google AppSheet

• Provider / operator: Google
• Provider headquarters: Mountain View, California, United States (Google)
• Provider and product-business origins: 1998 (Google); AppSheet business origins in 2014

Google AppSheet provides no-code application construction around connected business data. Its eligible scope includes operational applications and user actions rather than a passive spreadsheet display or a website template. A development platform should make its current product boundary clear, especially where a provider has rebranded tools or combined several application services.

A team can create an interface for a recurring data-based task and examine the rules controlling the information each user can access or change. The product-specific security terms and guidance make the relationship between connected business data and application access an explicit part of evaluation. AppSheet publishes product-specific security and administration resources. Current documentation must support the evaluated offering; historical modules and sibling products are not automatically interchangeable sources of capability.

Its clear data-to-application proposition supports recognition. Data-source permissions, subscription scope and the application’s configured access rules require joint review. The assessment follows that named scope and keeps commercial packaging separate from technical selection.

Neptune DXP

• Provider / operator: Neptune Software
• Headquarters: Oslo, Norway
• Provider founded: 2011 (Neptune Software)

Neptune DXP provides enterprise application development with a defined SAP integration context. Its platform combines low-code and professional development routes, with the named DXP scope assessed independently from the full range of SAP’s own application products. A development platform should make its current product boundary clear, especially where a provider has rebranded tools or combined several application services.

Teams can build interfaces for business work and connect them to the enterprise data and services required by the application, using the supported development approach. The DXP evaluation guide explicitly distinguishes low-code and professional development, making extension and SAP integration responsibilities visible within the named offering. Neptune publishes DXP-specific developer and evaluation guidance. Current documentation must support the evaluated offering; historical modules and sibling products are not automatically interchangeable sources of capability.

Its clear enterprise integration-and-builder proposition supports recognition. The exact DXP components and connected SAP responsibilities should be confirmed for the implementation. The assessment follows that named scope and keeps commercial packaging separate from technical selection.

Oracle APEX

• Provider / operator: Oracle
• Headquarters: Austin, Texas, United States
• Provider founding and product origins: 1977 (Oracle); APEX product lineage from 2004

Oracle APEX provides low-code application development closely connected to Oracle Database. Its named development environment supports data-centric business applications rather than functioning as an independent replacement for every database or enterprise service. A focused builder can provide depth around internal tools, mobile work or record-based applications without reproducing every function of an enterprise suite.

Teams can build interfaces and application logic around database information and configure the security governing how users access the deployed application. APEX-specific documentation preserves the relationship between application behaviour and database-backed information, including the controls configured for access to the application. Oracle publishes APEX-specific development and security documentation. The relevant comparison examines the target application, supported deployment and the extension route needed by its actual users.

Its coherent data-to-application architecture supports an established position. Database, hosting and application responsibilities remain separate parts of the implementation. Specialization can therefore support recognition while leaving clear limits on the product’s intended role.

Pega Platform

• Provider / operator: Pegasystems
• Headquarters: Waltham, Massachusetts, United States
• Provider founded: 1983 (Pegasystems)

Pega Platform connects low-code application design with case and process functions. The evaluated builder supports business applications whose interfaces and rules relate to continuing operational work rather than only static forms. Enterprise applications need clear relationships between the user interface, business rules and the underlying data model. A low-code environment should make those relationships understandable to its maintainers.

An organization can model user interaction around a case or process and connect that experience with the underlying business information and decision logic. Low-code development documentation links the application interface with the platform’s case and process environment rather than treating form design as the whole solution. Pega publishes low-code application-development and platform documentation. Developers and administrators should identify which changes the platform supports directly and where custom code or another service remains responsible.

Its substantial case-centred application architecture supports an established position. Industry applications and professional extensions should be distinguished from the underlying platform’s named development scope. Recognition concerns the actual development environment and its supported operating boundaries.

Quickbase

• Provider / operator: Quickbase
• Headquarters: Boston, Massachusetts, United States
• Product-business origins: 1999 (product-business origins)

Quickbase supports record-based business applications and shared organizational workflows. Its platform gives users a way to construct a maintained operating application rather than distribute a spreadsheet template without administration. A visual application builder is useful when the interface, data and actions form a maintainable business application. Convenience during initial construction is only part of the development lifecycle.

Teams can define the records, interfaces and connected actions required by a recurring business process, then inspect the supported developer and integration routes. The developer environment makes the application’s extension and integration routes inspectable alongside the configured records and user-facing business workflow. Quickbase publishes current developer resources and security material. The evaluation follows how a configured application is tested, administered and connected to the systems it uses.

Its coherent business-record application model supports recognition. The implementation must establish data ownership, extension responsibilities and the administration available within the selected product package. Its standing reflects documented application-building depth and governance, not an assumed development-speed advantage.

Retool

• Provider / operator: Retool
• Headquarters: San Francisco, California, United States
• Provider founded: 2017

Retool provides application building for internal tools connected to databases, APIs and enterprise services. Its development model combines visual interfaces with technical configuration rather than claiming that every application can be constructed without programming knowledge. Data-connected applications participate in systems that already have their own records and permissions. The builder must make the intended interface and authority understandable.

Teams can assemble an interface for operational users and connect its components to the queries or actions authorized against underlying business systems. The documentation gives technical teams a route to inspect the interface’s data connections and application logic before users act on enterprise records. Retool publishes current development and security documentation. Connection settings and application logic should be reviewed together so a convenient interface does not obscure responsibility for the resulting change.

Its detailed internal-tool development proposition supports an established position. The application’s connected-account permissions and custom logic remain part of the engineering and governance review. Its assessed contribution is the maintained development environment and its documented integration scope.

SAP Build

• Provider / operator: SAP
• Headquarters: Walldorf, Germany
• Provider founding and suite introduction: 1972 (SAP); SAP Build introduced in 2022

SAP Build provides a current application-development and automation environment within SAP’s technology platform. The assessment follows unified SAP Build rather than ranking deprecated standalone SAP Build Apps as an unchanged current product. No-code application design changes who can participate in building software, but it does not remove decisions about data, permissions or ongoing maintenance.

Teams can connect the selected development tools with enterprise application data and the processes their business interface is intended to support. The current Build offering is used as the product boundary; deprecated standalone Build Apps material does not establish unchanged availability or controls. SAP maintains Build learning and current product resources. The organization should identify who owns the application model and how a change is reviewed before users rely on it.

Its defined enterprise development context supports recognition. The chosen Build components and migration arrangements should be confirmed for the proposed application. Its standing reflects a coherent development proposition rather than a universal claim that programming expertise is unnecessary.

Zoho Creator

• Provider / operator: Zoho
• Headquarters: Chennai, India
• Provider founded: 1996 (Zoho)

Zoho Creator provides configurable business application development through forms, records, logic and connected services. The named Creator platform is evaluated independently from other Zoho applications whose functionality is not automatically part of a custom app. Low-code applications need a continuing operating home. The organization should understand which party runs the environment and how its application can evolve after deployment.

Teams can construct an application around a business record and the actions appropriate to its users, then inspect the data-security and integration requirements of the result. Creator help and data-security guidance provide a named-platform implementation route instead of borrowing controls from another application in the Zoho portfolio. Zoho maintains Creator help and security guidance. Help, security and developer resources provide evidence of intended operation, while actual configuration and delivery remain project-specific.

Its coherent configurable-application environment supports recognition. Supported functions, plan boundaries and custom logic need to be identified for the actual application. Recognition concerns the available platform rather than a promise of production readiness for every application a user can assemble.

---

Tier III — Specialist Low-Code & No-Code Development Platforms

(Alphabetical order)

Adalo

• Provider / operator: Adalo
• Headquarters: St. Louis, Missouri, United States
• Provider founded: 2018

Adalo provides no-code application development for web and mobile use. Its evaluated scope includes data-connected interfaces and application behaviour, distinguishing the product from website templates or an app-design consultancy without a maintained builder. Enterprise applications need clear relationships between the user interface, business rules and the underlying data model. A low-code environment should make those relationships understandable to its maintainers.

Users can construct an application around shared information and the actions performed through its screens, then review the relevant deployment and access requirements. Current help identifies the builder and application-development process, with the operating configuration requiring separate review before users rely on the deployed result. Adalo maintains current product help and development resources. Developers and administrators should identify which changes the platform supports directly and where custom code or another service remains responsible.

Its clearly bounded no-code application proposition supports recognition. Application permissions and connected-service responsibilities should be established through the actual configuration and product plan. Recognition concerns the actual development environment and its supported operating boundaries.

Alpha Anywhere

• Provider / operator: Alpha Software
• Headquarters: Burlington, Massachusetts, United States (Alpha Software)
• Provider founded: 1982 (Alpha Software)

Alpha Anywhere supports low-code web and mobile application development within Alpha Software’s product portfolio. Its evaluated role includes building and operating data-connected applications rather than merely collecting a form submission without a wider application model. A focused builder can provide depth around internal tools, mobile work or record-based applications without reproducing every function of an enterprise suite.

Developers can construct interfaces and application logic and configure the security framework governing access to the deployed solution. The application-security framework is documented within the named Alpha Anywhere environment, preserving the relationship between custom development and deployed user access. Alpha Software maintains application guides and security documentation. The relevant comparison examines the target application, supported deployment and the extension route needed by its actual users.

Its defined professional low-code development environment supports recognition. Custom code, deployment services and connected data remain material parts of the application owner’s maintenance responsibilities. Specialization can therefore support recognition while leaving clear limits on the product’s intended role.

Appsmith

• Provider / operator: Appsmith
• Headquarters: San Francisco, California, United States
• Provider founded: 2019

Appsmith provides an open-source low-code environment for internal business applications. Its product connects interface components with data sources and application logic, giving the resulting tool a substantive operating purpose beyond a static dashboard. A focused builder can provide depth around internal tools, mobile work or record-based applications without reproducing every function of an enterprise suite.

Development teams can construct an interface for working with enterprise records and review the permissions and actions associated with its connected systems. Current security documentation distinguishes the platform’s intended controls from assumptions based only on open-source availability or a successful prototype demonstration. Appsmith maintains current platform and security documentation. The relevant comparison examines the target application, supported deployment and the extension route needed by its actual users.

Its inspectable internal-application architecture supports recognition. Hosted and self-managed editions should be evaluated through their own controls and operating responsibilities. Specialization can therefore support recognition while leaving clear limits on the product’s intended role.

Betty Blocks

• Provider / operator: Betty Blocks
• Headquarters: Alkmaar, Netherlands
• Provider founded: 2008

Betty Blocks provides visual business application development with an enterprise governance context. Its maintained platform supports application logic and interfaces rather than operating only as a library of finished templates. Business application development requires more than an attractive page. Shared records, user actions and access rules give a deployed tool a continuing operational purpose.

Teams can build a business application and define how its data, components and user actions participate in the organization’s process, with professional extension where supported. The development documentation exposes a maintained application platform and its construction model instead of an exclusively bespoke development service delivered outside the product. Betty Blocks maintains current developer documentation. A useful evaluation follows an actual record through creation, review and change by users with different responsibilities.

Its identifiable governed application-development proposition supports recognition. The supported extension model, deployment and current product package should be specified for the application under review. The recognition concerns that substantive application workflow rather than a website template alone.

Bubble

• Provider / operator: Bubble
• Headquarters: New York, New York, United States
• Provider founded: 2012

Bubble provides no-code web and mobile application development through a visual environment. Its eligible scope includes application data, workflows and user interaction rather than merely presenting predesigned website pages. Low-code applications need a continuing operating home. The organization should understand which party runs the environment and how its application can evolve after deployment.

A builder can connect an interface with application records and the actions through which users create or change information, with privacy rules forming part of the operating configuration. The manual identifies application workflows and privacy rules, giving the visual interface a defined relationship to the records used by deployed applications. Bubble maintains a current manual and development guidance. Help, security and developer resources provide evidence of intended operation, while actual configuration and delivery remain project-specific.

Its substantive no-code application model supports recognition. The application owner remains responsible for data rules, custom integrations and the suitability of the deployed configuration. Recognition concerns the available platform rather than a promise of production readiness for every application a user can assemble.

Budibase

• Provider / operator: Budibase
• Headquarters: Belfast, Northern Ireland, United Kingdom
• Provider founded: 2019

Budibase provides visual business application construction, internal tools and workflow functions. Its maintained platform is assessed through the relationship between application interfaces, business data and actions rather than current agent branding alone. No-code application design changes who can participate in building software, but it does not remove decisions about data, permissions or ongoing maintenance.

Teams can build an operational interface around connected information and configure the steps used to handle a recurring internal request or record change. Product guides connect the internal application interface with its data and workflow responsibilities, while security resources identify the surrounding operating environment. Budibase publishes guides and security resources. The organization should identify who owns the application model and how a change is reviewed before users rely on it.

Its defined internal-application proposition supports recognition. The deployment, edition and data-source responsibilities must be explicit before a prototype is treated as an operating business application. Its standing reflects a coherent development proposition rather than a universal claim that programming expertise is unnecessary.

Caspio

• Provider / operator: Caspio
• Headquarters: Sunnyvale, California, United States
• Provider founded: 2000

Caspio provides low-code development for database-driven business applications. Its platform connects forms, reports and user interaction with a maintained cloud application environment rather than requiring every operational interface to be built from scratch. Data-connected applications participate in systems that already have their own records and permissions. The builder must make the intended interface and authority understandable.

Organizations can create an application around shared records and configure the information each participant can view or change through the resulting interface. The current help environment supports inspection of the database-application model, including how forms and reporting participate in the user’s operational workflow. Caspio maintains a current help centre and development resources. Connection settings and application logic should be reviewed together so a convenient interface does not obscure responsibility for the resulting change.

Its clear data-to-application operating model supports recognition. The deployment should establish application permissions and the responsibilities of connected services within the selected plan. Its assessed contribution is the maintained development environment and its documented integration scope.

Decisions

• Provider / operator: Decisions / ProcessMaker
• Product-business location: Virginia Beach, Virginia, United States (Decisions operating business)
• Product-business origins: 2010 (Decisions business origins)

Decisions combines visual application and workflow construction with rules-based automation. Its current combined-provider relationship with ProcessMaker is identified, and ProcessMaker is not ranked separately in this development-platform series. Low-code applications need a continuing operating home. The organization should understand which party runs the environment and how its application can evolve after deployment.

Teams can build interfaces and decision-driven application behaviour around a business process, connecting the resulting tool with the records and systems it needs to use. Platform documentation identifies the visual rules-and-application environment, while the combined-provider relationship remains separate from the functions of the maintained Decisions product. Decisions maintains platform and development documentation. Help, security and developer resources provide evidence of intended operation, while actual configuration and delivery remain project-specific.

Its defined rules-and-application construction model supports recognition. The maintained Decisions product and any combined-provider components should be distinguished in the actual delivery arrangement. Recognition concerns the available platform rather than a promise of production readiness for every application a user can assemble.

FlutterFlow

• Provider / operator: FlutterFlow
• Headquarters: Mountain View, California, United States
• Provider founded: 2020

FlutterFlow provides visual application construction around Flutter with supported professional extension and code export. Its product role connects interface design with a deployable application rather than offering only a non-operating visual mock-up. A visual application builder is useful when the interface, data and actions form a maintainable business application. Convenience during initial construction is only part of the development lifecycle.

Teams can construct user flows and connected application behaviour, then determine how exported code or external services will be maintained alongside the visual development environment. The code-export route makes ownership of the application after visual construction a concrete engineering question rather than an unspecified future handoff. FlutterFlow publishes current security and developer resources. The evaluation follows how a configured application is tested, administered and connected to the systems it uses.

Its defined visual-to-application development route supports recognition. The selected back-end services, custom code and distribution arrangements remain explicit implementation responsibilities. Its standing reflects documented application-building depth and governance, not an assumed development-speed advantage.

Glide

• Provider / operator: Glide
• Headquarters: San Francisco, California, United States
• Provider founded: 2018

Glide provides data-connected business application construction through a visual builder. The named platform turns shared information into an operating interface for organizational work rather than functioning only as a spreadsheet viewer. Development governance becomes important when several teams build applications on a shared platform. Identity, permissions and deployment arrangements affect the application after its first demonstration.

A team can organize the screens, records and actions required by an internal or external application and examine how different users receive appropriate access to that information. The application documentation makes data, screens and user actions part of one product scope, distinguishing the builder from a passive shared spreadsheet. Glide maintains current application and support documentation. The practical review includes a change to a live application and the responsibilities of the people authorized to make it.

Its coherent business-data development model supports recognition. The chosen data sources, user-access configuration and subscription determine the application’s actual operating boundaries. The product is assessed through documented provision rather than a claim that visual design eliminates engineering work.

Kintone

• Provider / operator: Cybozu
• Provider headquarters: Tokyo, Japan (Cybozu)
• Provider founding and product introduction: 1997 (Cybozu); Kintone introduced in 2011

Kintone supports no-code business applications around shared records, configured fields and team processes. The named platform remains distinct from Cybozu’s other groupware applications and from a generic database without user workflow. Business application development requires more than an attractive page. Shared records, user actions and access rules give a deployed tool a continuing operational purpose.

Teams can create an operational application that relates record information, status and authorized user actions within a shared environment. The rapid-application-development material connects the no-code builder with substantive business records and actions rather than a presentation-only interface or website template. Kintone publishes application-development, workflow and implementation resources. A useful evaluation follows an actual record through creation, review and change by users with different responsibilities.

Its clear record-centred development model supports recognition. Required extensions and interfaces should be identified rather than assumed available through every configuration. The recognition concerns that substantive application workflow rather than a website template alone.

Kissflow

• Provider / operator: Kissflow
• Provider operating office: Chennai, India
• Provider business origins: 2003 (OrangeScape business origins)

Kissflow combines visual business application development with process and workflow functions. Its current low-code environment is evaluated independently from a procurement-specific application or consulting engagement supplied around it. An application platform can combine visual construction with professional extension. Those approaches serve related needs when the resulting code, interfaces and data remain supportable over time.

A team can create an application for recurring work and relate its forms and records to the people responsible for reviewing and completing that work. The current low-code offering provides the application-building scope, while help resources support configuration of the underlying process and user interaction. Kissflow maintains application-building and platform help resources. The implementation should preserve an explicit boundary between platform-managed behaviour and the custom components maintained by the organization.

Its defined application-and-workflow model supports recognition. The selected hosting, integrations and administration responsibilities need explicit evaluation for the application being proposed. Its placement recognizes that development model without promising identical flexibility for every application type.

Softr

• Provider / operator: Softr
• Headquarters: Berlin, Germany
• Provider founded: 2019

Softr supports no-code business applications and portals connected to organizational data. Its eligible product scope includes user-facing work with records, keeping the assessment distinct from website templates without substantive application behaviour. An application platform can combine visual construction with professional extension. Those approaches serve related needs when the resulting code, interfaces and data remain supportable over time.

Teams can construct a portal or internal tool and configure which information and actions are available to participating users within that application. Application-security guidance gives the portal or internal tool a product-specific control context rather than relying solely on the permissions of its external data source. Softr publishes application-security and current help documentation. The implementation should preserve an explicit boundary between platform-managed behaviour and the custom components maintained by the organization.

Its clearly identified portal-and-data application model supports recognition. The application’s permissions and back-end data-source settings need to be examined together rather than treated as interchangeable controls. Its placement recognizes that development model without promising identical flexibility for every application type.

ToolJet

• Provider / operator: ToolJet
• Headquarters: San Francisco, California, United States
• Provider founded: 2021

ToolJet supports internal application development through configurable interfaces and connected enterprise data. Its eligible software role includes building business tools rather than providing a one-off app-development agency service. A development platform should make its current product boundary clear, especially where a provider has rebranded tools or combined several application services.

Teams can connect application components with supported data sources and the actions used by internal users, then examine the access and security configuration of the resulting environment. The maintained platform documentation describes the internal-tool application environment, with security guidance available for the data and actions connected through it. ToolJet publishes platform documentation and current security resources. Current documentation must support the evaluated offering; historical modules and sibling products are not automatically interchangeable sources of capability.

Its coherent internal-tool builder supports recognition. The actual edition, custom logic and operating arrangement should be assessed rather than inferred from the availability of the source code alone. The assessment follows that named scope and keeps commercial packaging separate from technical selection.

WaveMaker

• Provider / operator: WaveMaker
• Headquarters: Plano, Texas, United States
• Provider business origins: 2003 (provider business origins)

WaveMaker provides visual application development with professional extension for enterprise web and mobile use. Its named builder supports application interfaces, data connections and code-oriented maintenance rather than an exclusively template-based website service. No-code application design changes who can participate in building software, but it does not remove decisions about data, permissions or ongoing maintenance.

Development teams can combine visual construction with the application logic and integrations required by their enterprise environment, then review the security model used in deployment. Current application-security and developer guides give the visual builder an inspectable technical context for its enterprise application and professional extension route. WaveMaker publishes current developer and application-security guidance. The organization should identify who owns the application model and how a change is reviewed before users rely on it.

Its defined visual-and-professional development route supports recognition. The generated application and any custom components need clearly assigned operating and maintenance responsibilities. Its standing reflects a coherent development proposition rather than a universal claim that programming expertise is unnecessary.

---

Remarks

Low-code development changes how applications are constructed without removing the need for coherent software. Interfaces, data, actions and operating responsibility remain connected requirements. A useful platform makes those relationships understandable to both the people who build the application and those who depend on it after deployment.

The tiers reflect the weighted review of documented application-building depth, enterprise utility, integration and security, development support and operating clarity. Specialized products can provide an appropriate environment for internal tools, database applications or mobile work. A lower-band placement should therefore be interpreted within the product’s stated development purpose.

Fact boxes distinguish current provider locations, company origins and product lineage. Acquired or combined businesses are identified without counting the same provider twice within this series. Documentation is also scoped to the actual product and version; a deprecated builder, another edition’s controls or a sibling application does not automatically establish the evaluated platform’s current capability.

Tier I is ordered, while Tiers II and III are alphabetical. No licensing or sponsorship consideration affects eligibility, scores or ties. Buyers should confirm the exact product package, deployment, data permissions, extension requirements and ongoing application ownership before moving from a demonstration to an operating business system.

---

Recognition

Inclusion in the Top 30 Low-Code & No-Code Development Platforms 2027 ranking is an editorial determination of The Economy Rankings and does not require licensing, advertising, sponsorship, or other commercial participation.

Ranked organizations may factually refer to their inclusion in the ranking in their own communications. When describing the result, entities should accurately reflect the tier structure and methodology used in the published ranking.

How the ranking should be interpreted

• Tier I represents the Top 5 entities, and the published order within Tier I reflects the ranking order.
• Tier II represents entities ranked within the Top 15, following Tier I. Entities within Tier II are displayed alphabetically; their displayed order should therefore not be interpreted as an individual numerical ranking.
• Tier III represents entities ranked within the Top 30, following Tiers I and II. Entities within Tier III are also displayed alphabetically, and their displayed order should not be interpreted as an individual numerical ranking.
• An entity's tier, rather than its alphabetical position within Tier II or Tier III, should therefore be used when describing its standing.

Referencing the ranking

Depending on the entity's published tier, appropriate factual descriptions may include:

• Tier I: “Ranked Tier I” or “Ranked among the Top 5”
• Tier II: “Ranked Tier II” or “Ranked among the Top 15”
• Tier III: “Ranked Tier III” or “Ranked among the Top 30”

Entities should not describe an alphabetical position within Tier II or Tier III as a specific numerical rank.

Use of The Economy Rankings recognition materials

Editorial inclusion in a ranking does NOT by itself grant permission to use The Economy Rankings badges, seals, logos, official recognition graphics, licensed quotations, or other proprietary recognition materials.

Organizations wishing to use official The Economy Rankings recognition materials in corporate websites, marketing materials, investor communications, client presentations, social media, press releases, or other external communications should refer to the applicable licensing terms and usage policies:

• The Economy Rankings License Structure — available licence levels and permitted recognition uses
  The Economy Rankings License Structure | The Economy Rankings
• The Economy Rankings License Policy — licensing conditions governing use of The Economy Rankings recognition, marks, and related materials
  The Economy Rankings License Policy | The Economy Rankings
• Recognition Use Guide — guidance on permitted wording, presentation, attribution, and use of ranking recognition
  Recognition Use Guide | The Economy Rankings

Purchasing or holding a recognition-materials licence does not confer inclusion or a higher tier.

Recognized organizations may reference the designation in:

• corporate websites
• investor communications
• marketing materials
• client presentations

Licensing inquiries:
[email protected]