Rasa

Name: Rasa
Brand: Rasa
Rating: 4.3 (26 reviews)

Rasa is a conversational AI platform that builds, deploys, and operates text and voice assistants by combining an open-source core with commercial enterprise features for dialogue management, agent orchestration, and deployment control.

Est 2014|Valuation $225.5M|Raised $70.3M|78 Ref Customers

LinkedIn 25K|Web traffic 49K|FTEs 117|HQ San Francisco, California, US

MarketsVoice AI Agents Agent Builder Platforms

Published Oct 15, 2026

01Common complaints

If you need a true no-code platform where non-technical teams can build and iterate quickly with minimal engineering
- Reviewers consistently note limitations in no-code UX and builder tooling; the platform is oriented toward technical users.
If you are optimizing for fastest time-to-first-bot inside a single cloud ecosystem
- Managed services integrated with a cloud provider may offer faster initial deployments for teams already standardized on that cloud.
If you want a fully packaged platform experience (analytics, governance, enterprise workflows) with minimal custom build
- Some vendors provide more out-of-the-box governance and packaged enterprise workflows, reducing engineering requirements.
If your team cannot support a steep learning curve
- Documentation and training gaps are commonly cited, and teams without engineering capacity may struggle to reach production quickly.
Product evolution and deprecations
- Community forum posts indicate that older community editions (for example, a legacy community edition of Rasa X) are no longer maintained or supported; organizations relying on deprecated distributions should plan migrations.
Technical limitations and operational gaps cited by users
- Documentation gaps and a steep learning curve.
- Limited out-of-the-box integrations compared with some packaged platforms.
- Some reviewers reported challenges with large language model integration as of earlier reporting (e.g., 2024); teams should validate current LLM workflows with a proof of concept using the intended LLM stack.
Security and compliance information availability
- Certification artifacts were not located on the primary product pages reviewed; buyers should request SOC 2, ISO 27001, BAA (if applicable), and other compliance documents directly from the vendor.

- If you need a true no-code platform where non-technical teams can build and iterate quickly with minimal engineering - Reviewers consistently note limitations in no-code UX and builder tooling; the platform is oriented toward technical users. - If you are optimizing for fastest time-to-first-bot inside a single cloud ecosystem - Managed services integrated with a cloud provider may offer faster initial deployments for teams already standardized on that cloud. - If you want a fully packaged platform experience (analytics, governance, enterprise workflows) with minimal custom build - Some vendors provide more out-of-the-box governance and packaged enterprise workflows, reducing engineering requirements. - If your team cannot support a steep learning curve - Documentation and training gaps are commonly cited, and teams without engineering capacity may struggle to reach production quickly. - Product evolution and deprecations - Community forum posts indicate that older community editions (for example, a legacy community edition of Rasa X) are no longer maintained or supported; organizations relying on deprecated distributions should plan migrations. - Technical limitations and operational gaps cited by users - Documentation gaps and a steep learning curve. - Limited out-of-the-box integrations compared with some packaged platforms. - Some reviewers reported challenges with large language model integration as of earlier reporting (e.g., 2024); teams should validate current LLM workflows with a proof of concept using the intended LLM stack. - Security and compliance information availability - Certification artifacts were not located on the primary product pages reviewed; buyers should request SOC 2, ISO 27001, BAA (if applicable), and other compliance documents directly from the vendor.

02Why they buy

Competitive advantages reflected in customer feedback (not only vendor claims)
- Customization and open-source foundation
  - Users consistently cite flexibility and the ability to tune and extend components as a practical advantage for complex use cases.
- Data and deployment control
  - Reviewers frequently cite self-hosting and data control as a primary reason for selecting the platform over cloud-only alternatives.
Capabilities that competitors may offer differently
- Self-managed deployment options and open-core architecture reduce certain forms of vendor lock-in for core conversational logic, while enterprise features may be licensed.
Areas where competitors may have advantages
- No-code builder UX and packaged platform completeness are areas where some competitors can deliver faster time-to-value for non-technical teams.
- Pricing transparency: some alternatives publish more self-serve pricing information for smaller teams.

- Competitive advantages reflected in customer feedback (not only vendor claims) - Customization and open-source foundation - Users consistently cite flexibility and the ability to tune and extend components as a practical advantage for complex use cases. - Data and deployment control - Reviewers frequently cite self-hosting and data control as a primary reason for selecting the platform over cloud-only alternatives. - Capabilities that competitors may offer differently - Self-managed deployment options and open-core architecture reduce certain forms of vendor lock-in for core conversational logic, while enterprise features may be licensed. - Areas where competitors may have advantages - No-code builder UX and packaged platform completeness are areas where some competitors can deliver faster time-to-value for non-technical teams. - Pricing transparency: some alternatives publish more self-serve pricing information for smaller teams.

03Field reports

Enterprise review platforms (summary of accessible review content)

Gartner Peer Insights
- Available summary ratings and short excerpts indicate generally positive sentiment regarding control over data and support options; accessible snippets reflected limited sample sizes.
- Positive themes in reviews include control over data and flexibility; reviewers also reported a steep learning curve and a desire for more out-of-the-box integrations.
G2
- Public review excerpts show mixed feedback: some reviewers described the platform positively and noted it is suited for technical teams; other reviewers characterized it as more of an engine/framework than a full enterprise platform and noted issues with documentation and UI/navigation.
TrustRadius
- Review excerpts include use-case narratives (e.g., helpdesk chatbot deployments) and note outcomes such as reduced call wait times in reviewer reports; some TrustRadius reviews were vendor-invited, which can introduce selection bias.

- Gartner Peer Insights - Available summary ratings and short excerpts indicate generally positive sentiment regarding control over data and support options; accessible snippets reflected limited sample sizes. - Positive themes in reviews include control over data and flexibility; reviewers also reported a steep learning curve and a desire for more out-of-the-box integrations. - G2 - Public review excerpts show mixed feedback: some reviewers described the platform positively and noted it is suited for technical teams; other reviewers characterized it as more of an engine/framework than a full enterprise platform and noted issues with documentation and UI/navigation. - TrustRadius - Review excerpts include use-case narratives (e.g., helpdesk chatbot deployments) and note outcomes such as reduced call wait times in reviewer reports; some TrustRadius reviews were vendor-invited, which can introduce selection bias.

Community discussions (forum and social channels)

Official community forum contains extensive discussion of Rasa Open Source topics and deprecation notices for older community editions, signaling operational impacts for teams using deprecated distributions.
Developer community threads on public forums discuss practical integration approaches (for example, integrating external LLMs via custom components or action servers); these threads provide qualitative signals about developer experience rather than formal product evaluations.

- Official community forum contains extensive discussion of Rasa Open Source topics and deprecation notices for older community editions, signaling operational impacts for teams using deprecated distributions. - Developer community threads on public forums discuss practical integration approaches (for example, integrating external LLMs via custom components or action servers); these threads provide qualitative signals about developer experience rather than formal product evaluations.

Why customers selected Rasa (recurring themes from reviews)

Control
- Preference for self-hosting/on-prem and data control, which is an enterprise differentiator compared with cloud-only tools.
Customization
- Ability to modify and tune ML components and dialogue behavior beyond template-based platforms.
Technical depth
- Reported strengths in NLU and flexibility for complex workflows where packaged platforms may be insufficient.

Why some customers moved away or chose alternatives (recurring themes)

Perception of incomplete platform features
- Some reviewers view Rasa as a capable engine or framework but note less completeness in ancillary platform needs (governance, UX tooling, prebuilt integrations), which influences choices toward other suites.
Learning curve and operational complexity
- Documentation quality, training depth, and operational complexity are commonly cited barriers for teams without ML/engineering capacity.

- Perception of incomplete platform features - Some reviewers view Rasa as a capable engine or framework but note less completeness in ancillary platform needs (governance, UX tooling, prebuilt integrations), which influences choices toward other suites. - Learning curve and operational complexity - Documentation quality, training depth, and operational complexity are commonly cited barriers for teams without ML/engineering capacity.

Evidence available in this run

Customer review narratives (example: a large telecom company) describe reduced call wait times in specific deployments; these are self-reported reviewer claims and are not independently audited ROI studies.
Press coverage mentions named enterprise customers and indicates traction in financial services and telecom; these reports reference company statements and investor commentary rather than independently verified performance studies.
Vendor materials reference customer cases and enablement artifacts; vendor-authored content should be validated through reference checks and technical due diligence.

- Customer review narratives (example: a large telecom company) describe reduced call wait times in specific deployments; these are self-reported reviewer claims and are not independently audited ROI studies. - Press coverage mentions named enterprise customers and indicates traction in financial services and telecom; these reports reference company statements and investor commentary rather than independently verified performance studies. - Vendor materials reference customer cases and enablement artifacts; vendor-authored content should be validated through reference checks and technical due diligence.

Methodology gaps to note

No independently verified ROI benchmarks or controlled studies were found in the sources accessed.
When metrics are provided in case descriptions, measurement methodology is typically not published.

04Best fit

Ideal Customer Profile

Company sizes
- Best fit
  - Mid-market to enterprise organizations with dedicated AI/ML engineering and DevOps capacity.
  - Regulated enterprises needing self-managed deployments and data residency control.
- Less ideal
  - Very small teams without ML/DevOps capability, unless the use case is a narrowly scoped pilot using the Developer Edition.
Industries and verticals where adoption is strongest (examples)
- Telecom and financial services appear frequently in press and reviewer examples.
Roles and personas
- Decision makers
  - Heads of Customer Experience / Contact Center leadership
  - CIO / CISO (for data residency and security posture)
  - VP Engineering / Platform Engineering
- End users/builders
  - Conversational AI engineers
  - ML engineers / data scientists
  - Backend engineers building integrations (CRM, ticketing, account systems)
  - DevOps/SRE for production reliability
Pain points the product addresses
- Requirement to keep customer conversation data within controlled infrastructure.
- Need for high customization, complex dialogue orchestration, and integration with enterprise systems.
- Desire to avoid vendor lock-in to a single cloud provider’s conversational stack.
Deal disqualifiers (what makes a poor fit)
- No in-house engineering/ML resources with an expectation of a purely no-code rollout.
- Use cases that require a large library of turnkey connectors and prebuilt industry accelerators without engineering.
- Buyers requiring fully transparent, self-serve enterprise pricing without a sales process.

- Company sizes - Best fit - Mid-market to enterprise organizations with dedicated AI/ML engineering and DevOps capacity. - Regulated enterprises needing self-managed deployments and data residency control. - Less ideal - Very small teams without ML/DevOps capability, unless the use case is a narrowly scoped pilot using the Developer Edition. - Industries and verticals where adoption is strongest (examples) - Telecom and financial services appear frequently in press and reviewer examples. - Roles and personas - Decision makers - Heads of Customer Experience / Contact Center leadership - CIO / CISO (for data residency and security posture) - VP Engineering / Platform Engineering - End users/builders - Conversational AI engineers - ML engineers / data scientists - Backend engineers building integrations (CRM, ticketing, account systems) - DevOps/SRE for production reliability - Pain points the product addresses - Requirement to keep customer conversation data within controlled infrastructure. - Need for high customization, complex dialogue orchestration, and integration with enterprise systems. - Desire to avoid vendor lock-in to a single cloud provider’s conversational stack. - Deal disqualifiers (what makes a poor fit) - No in-house engineering/ML resources with an expectation of a purely no-code rollout. - Use cases that require a large library of turnkey connectors and prebuilt industry accelerators without engineering. - Buyers requiring fully transparent, self-serve enterprise pricing without a sales process.

05The pitch

What the product does (core value proposition in objective terms)

Rasa is a conversational AI platform used to build, deploy, and operate text and voice assistants.
It combines an open-source foundation (Rasa Open Source) with commercial/enterprise offerings (Rasa Pro and broader Rasa Platform capabilities, including a UI product referred to as Rasa Studio).
Rasa’s recent positioning uses the acronym CALM (Conversational AI with Language Models) for dialogue understanding and management, and it provides agent orchestration features (skills, integrations, observability, governance) intended for enterprise deployments.

- Rasa is a conversational AI platform used to build, deploy, and operate text and voice assistants. - It combines an open-source foundation (Rasa Open Source) with commercial/enterprise offerings (Rasa Pro and broader Rasa Platform capabilities, including a UI product referred to as Rasa Studio). - Rasa’s recent positioning uses the acronym CALM (Conversational AI with Language Models) for dialogue understanding and management, and it provides agent orchestration features (skills, integrations, observability, governance) intended for enterprise deployments.

Target market and market positioning

Primary targets
- Enterprises and regulated industries that need deployment control (on-prem/private cloud), data residency, and customization.
- Developer-led teams (ML/engineering-heavy) that intend to manage and customize the assistant stack rather than use a fully managed cloud-only bot builder.
Market category context
- Industry listings place Rasa Platform under the Conversational AI Platforms category; user reviews reference the combination of open-source flexibility and available enterprise support, positioning Rasa alongside both enterprise conversational suites and cloud hyperscaler offerings.

- Primary targets - Enterprises and regulated industries that need deployment control (on-prem/private cloud), data residency, and customization. - Developer-led teams (ML/engineering-heavy) that intend to manage and customize the assistant stack rather than use a fully managed cloud-only bot builder. - Market category context - Industry listings place Rasa Platform under the Conversational AI Platforms category; user reviews reference the combination of open-source flexibility and available enterprise support, positioning Rasa alongside both enterprise conversational suites and cloud hyperscaler offerings.

Get a comprehensive analysis of Rasa including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →