Forrester included Kissflow as a notable vendor in The AppGen And Low-Code Platforms Landscape, Q2 2026, published on 19 May 2026. Ken Parmelee authored the report with Chris Gardner, Kylie Cadogan, and Kara Hartig. It covers 40 vendors in the global market.
A Forrester Landscape report is a market overview that maps the vendors in a category, their size and geography, and the use cases each serves. It is deliberately not a ranking. Forrester publishes Landscapes so buyers can see the shape of a market before narrowing it, then uses Wave reports to score a smaller field.
That structure changes how the report should be read. The value is not in who appears. It is in how Forrester has drawn the category boundary, and in which use cases each vendor is recorded against. This post covers what a Landscape is, why Forrester added application generation to the low-code category, the use cases recorded for Kissflow, and how to use the report when building a shortlist.
A Landscape report gives enterprise buyers a market map at a point in time. Forrester publishes them to answer a specific question: who is in this category, and what does each vendor actually do?
Landscapes typically record for each vendor:
Landscapes and Waves serve different points in the buying cycle. A Landscape is for the stage where the longlist is still forming. A Wave is for the stage where three or four vendors are being scored head to head.
Confusing the two leads to a common mistake. Inclusion in a Landscape is not a competitive result, and no vendor in a Landscape has been rated above another. Anyone presenting a Landscape appearance as a ranking is misreading the format.
Forrester combined application generation with low-code platforms because the two approaches now compete for the same budget and the same use cases.
Application generation refers to tools that produce a working application from a natural-language description. Low-code refers to platforms that build applications through visual configuration rather than handwritten code. Both promise the same outcome: applications delivered without a full engineering cycle.
Putting them in one Landscape forces a comparison that vendors on each side would rather avoid. It asks buyers to weigh generation speed against the properties of the output.
That is the right question, and it is the one enterprise IT keeps coming back to. A tool that produces an application in an afternoon has solved the first day. The harder problem is the twelfth month, when a business rule changes and someone has to find where the logic lives.
Forrester asked each participating vendor to nominate the top three extended use cases it focuses on. Kissflow selected three:
These are declared areas of focus rather than a Forrester assessment of capability. Forrester notes that the table does not represent available functionality and may not cover every use case a vendor serves.
The second choice is the interesting one. Monitoring and management are lifecycle capability that only matters once applications are in production and someone has to answer for them. Forrester lists custom governance policies and monitoring, plus ALM, DevOps, SDLC environments, and CI/CD tools, as the primary functionality that the use case requires.
Choosing it says something about where Kissflow believes the hard problem sits. Generating an application is the part that gets demonstrated. Running it for three years is the part that gets paid for.
Kissflow AI maps natural language to platform metadata rather than generating code. A prompt produces a structured blueprint covering data model, pages, roles, workflows, and navigation, and the application is generated from that blueprint.
Three properties follow:
Output is deterministic, so the same input produces the same result every time
Output is inspectable, because every artifact is a standard Kissflow component a developer can open and read
Governance is unified because AI-driven changes write to the same audit log as manual edits
The Kissflow AI Builder became generally available in May 2026. A single prompt or an uploaded requirements document generates a working application, refined through conversation, with a human in the lead throughout.
This is a deliberate architectural position rather than a limitation. A blueprint can be read by the compliance officer who signs it off, not only by the developer who built it. Changes are versioned, attributable, and reversible.
Kissflow has held this position since its founding in 2012: applications should be driven by business logic, not code. Over 1,200 customers now build on that basis, including Godrej Consumer Products and Aswaq Management and Services.
Kissflow holds SOC 1 Type II, SOC 2 Type II, SOC 3, ISO/IEC 27001, HIPAA, GDPR, and CCPA compliance, with data residency in the US, EU, APAC, and Oceania.
It is a Forrester market overview covering 40 vendors in the combined application generation and low-code platforms category. Forrester published it on 19 May 2026. It maps vendor size, geography, and use cases rather than scoring vendors against each other.
Yes. Forrester included Kissflow as a notable vendor in the Q2 2026 Landscape, recording extended use cases in AI agent development, application monitoring and management, and task automation.
A Landscape maps every notable vendor in a category without scoring them, and suits the longlist stage. A Wave scores a smaller set of vendors against weighted criteria and places them in tiers, which suits the final shortlist stage.
Application generation refers to tools that produce a working application from a natural language description or requirements document. Forrester grouped it with low-code platforms in Q2 2026 because both approaches now serve the same enterprise use cases and compete for the same budget.
No. Landscape reports do not rank or score vendors, and no vendor in a Landscape has been placed above another. Inclusion indicates that Forrester considers the vendor notable in the category based on its stated inclusion criteria.
Filter it by use case rather than vendor size. Identify the two or three use cases your project requires, shortlist the vendors recorded against them, then apply your own weighted evaluation criteria to that longlist.
The useful signal in the Q2 2026 Landscape is not the vendor list. It is that Forrester now treats application generation and low-code as one market, which means buyers are being asked to compare generation speed against what gets generated.
Kissflow's position is that this comparison has a correct answer. A platform that outputs an inspectable blueprint under a unified audit log is maintainable in a way that generated code is not, and maintainability is the property that decides whether an application survives its first year.
If you are building a longlist, filter the Landscape by use case, then re-weight your own criteria around governance and lifecycle before scoring a single vendor.