Alemba

Name: Alemba
Brand: Alemba
Rating: 3.9 (172 reviews)

Alemba develops Alemba Service Manager, a highly functional, 100% ITIL-compliant ITSM software solution.

Est 2007|60 Ref Customers

LinkedIn 1K|Web traffic 1K|FTEs 41|HQ Edinburgh, Scotland, GB

MarketsIT Service Desk (ITSM)IT Asset Management (ITAM)Workflow Automation

Published Oct 5, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Very small organizations seeking only basic ticketing and minimal implementation overhead may find marketplace alternatives with simpler, lower-cost entry points more appropriate. - Industries or use cases where competitors are clearly superior - Organizations seeking a broad enterprise workflow platform beyond ITSM with extensive marketplace integrations and platform services may prefer alternatives such as ServiceNow. - Organizations that require tightly integrated endpoint/security and IT operations tooling may evaluate Ivanti or other integrated suites. - Technical requirements that this product cannot meet - Buyers that require a modern chat-first service experience, mobile-first UX, or extensive built-in AI features should verify ASM’s current capabilities and roadmap; multiple reviewers cited gaps in these areas. - Budget constraints that make alternatives more appropriate - Cost-sensitive teams should compare entry-level pricing and TCO across options such as Jira Service Management or Freshservice, depending on required feature sets and user counts. - Specific workflows or integrations where the product falls short - If success depends on numerous prebuilt third-party integrations, plan for possible integration engineering and verify API availability and connector maturity. - Red flags in the buying process (e.g., requires annual commitment, no free trial) - Buyers should confirm trial availability, environment provisioning, contractual terms, and exit clauses directly with the vendor. - Current limitations acknowledged by the vendor - Vendor communications reference user interface modernization efforts (for example, migration to newer HTML5-based interfaces) in the context of legacy browser support changes, indicating an ongoing transition from older UI components. - Features on the roadmap (not yet available) - A detailed public roadmap with specific release dates was not located in the reviewed sources; buyers should request roadmap and delivery timelines during vendor engagement. - Scale limitations - No precise scalability thresholds or failure points were available in public sources. Some enterprise reviewers report acceptable scalability for their use cases, but hard limits were not documented. - Security or compliance gaps - ISO 27001:2022 coverage is published; SOC 2 evidence and ISO 27017/27018 were not publicly documented in the sources reviewed. - Technical debt or architectural limitations mentioned in reviews - Review narratives referencing an older-looking UI and historical product lineage suggest there may be legacy components; evaluate current architecture details and modernization progress during technical due diligence. - API limitations or integration constraints - Multiple review summaries cite integration difficulty. Buyers should request API documentation, supported connectors, and integration case studies.

Deal disqualifiers: what makes a POOR fit

Teams that require a modern, consumer-grade UX out of the box; organizations that demand broad out-of-the-box marketplace integrations or advanced AI-assisted capabilities without additional engineering work may be a poor fit.

02Why they buy

- Competitive advantages validated by customer feedback (not just vendor claims) - Several reviewers and platform summaries indicate ASM meets core ITIL process needs and can be configured for specific governance or HR partitioning scenarios. - Reviewers have reported that ASM can be cost-competitive in some procurement scenarios compared with larger suites; such observations are reviewer- or vendor-reported and should be validated during procurement. - Unique features and capabilities competitors lack - No clearly unique, market-exclusive capability was identified in independent sources during this research session. The vendor describes features such as configurable workflows and no/low-code automation, but similar capabilities exist across competing offerings. - Differentiation from competitors based on reviews - Reviewer narratives suggest ASM occupies a position focused on core service delivery and governance rather than a broad platform ecosystem. - Value propositions with evidence from case studies - Vendor-published case narratives and marketing materials provide qualitative examples of operational improvements; independently verified ROI metrics were not found in public sources. - Areas where competitors have advantages - Competitors such as ServiceNow, Jira Service Management, and Ivanti provide broader ecosystems, deeper native integrations, or platform services that may better support certain enterprise requirements.

03Field reports

Independent, verifiable case studies with quantified metrics were not widely available in the public sources captured for this research session. Vendor collateral contains case narratives and quoted customer statements, which should be validated in reference checks.

Customer Testimonials

- Sources reviewed include platform summaries and user review excerpts from third-party review sites and community forums. Review access limitations (site protections, gated content) restricted capture of full review text in some cases. - Representative review signals and quotes (attributed to platform where available): - Review platform excerpts indicate mixed ratings across different sites; some platforms show aggregate ratings with multiple reviews. - Reddit (user commentary) - Example comment: "I don't use Alemba (it looks neat though), but shouldn't there be some sort of documentation with how to set it up and use it effectively?" - Example comment (opinionated): a community user expressed a strongly negative opinion about historical product versions; community claims about ownership and product quality should be treated as individual opinions and verified. - G2 (selected review excerpts) - Positive themes reported by reviewers include lower acquisition cost in some cases, dashboarding/export capability, and Active Directory integration in specific deployments. - Example quoted reviewer comments include: "An easy to use Incident and Service request management tool available at a minimal cost" and "Integration with AD is seamless…" - Negative or mixed themes include mentions of missing advanced features, web interface sluggishness, and increased complexity when adding modules such as CMDB. - Other review platforms - Some review summaries and platform pages were accessible only in summary form; full text was either gated or not retrieved in this research run.

Balance and distribution

The accessible review data set contains both positive and negative comments. Some platforms show a distribution that ranges from high-rated reviews to low-rated reviews; full-text negative reviews were not always captured in this session.

Common criticisms and complaints summarized from multiple reviewer sources

User-reported issues include older or dated user interface elements, difficulty integrating with some third-party tools, absence of certain modern capabilities (for example, chat-based assistants or mobile-optimized workflows in some deployments), performance/sluggishness, and increased complexity when expanding scope (CMDB, asset management).

Reasons cited for choosing the product

Review evidence indicates selection rationales often include meeting standard ITIL process needs and comparative acquisition or operational cost in specific procurement cases. Such rationales are reviewer- or vendor-reported and should be validated in reference calls.

Reasons cited for leaving or risk of churn

Explicit customer churn narratives were not prominent in the accessible sources for this research session. Indirect signals that may indicate churn risk include dated UX, integration friction, and feature gaps relative to evolving buyer expectations.

Outcomes and metrics

Independently verifiable, quantified outcomes (for example, reductions in ticket backlog or improvements in mean time to repair) were not consistently available in the reviewed materials. Most reported outcomes were qualitative.

Customer pain points and frustrations mentioned in reviews

Examples include documentation/setup questions, perceived confusion when adding modules such as CMDB, integration difficulty, and occasional performance issues during web-based usage.

Deal-breakers and purchase blockers (observed signals)

The recurring complaints above suggest potential deal-breakers for buyers that prioritize a modern UX, extensive out-of-the-box integrations, or advanced AI-assisted service operations.

Sources reviewed: Official vendor documentation and product overview pages, third-party review sites and summary pages, community forums and discussion threads, and user review aggregators.

Vendor-published example

Vendor brochures and marketing materials include short-form success narratives (for example, a vendor brochure that references an early positive outcome after deployment). These are vendor-published claims and should be treated as such unless corroborated independently.

Implementation details and time to value

Some third-party summaries and review platform narratives indicate vendor-led or partner-led turnkey implementations. Time-to-value was typically described qualitatively; few sources provide standardized, quantifiable deployment timelines.

Challenges during adoption and resolution

Some reviews mention implementation challenges related to local partner rollouts; buyer experiences appear to vary depending on partner capability and project complexity.

Critical note on vendor-published metrics

Any vendor-published ROI or performance metrics should be validated through customer references or independent third-party studies.

Mixed results

The available narratives include both successful deployments for ILT-aligned, basic ITSM needs and cases where customers moved toward platforms with broader ecosystems or modern features as their needs evolved.

04Best fit

Company sizes

Positioning evidence suggests mid-market to enterprise organizations; typically mid-size to very large employers. Revenue ranges were not specified in public sources; organizations with enterprise-level revenues commonly evaluate enterprise ITSM vendors, but this is an inference and should be validated.

Industries and verticals where adoption is strongest (with customer examples)

Vendor materials and public references indicate use in regulated sectors such as healthcare, government, and financial services.
Third-party review directories list named organizations as customers in public entries; prospective buyers should request references and verify those engagements during procurement.

Roles and personas: decision makers AND end users

Decision makers: IT service management leadership (heads of service management or IT operations), procurement stakeholders in regulated environments, and security/compliance officers.
End users: service desk analysts, IT support staff, change managers, and asset/CMDB administrators.

Pain points and challenges the product addresses

Standardizing ITIL workflows, improving request fulfillment processes, and providing governance and partitioning capabilities for sensitive data in regulated contexts.

Qualification criteria: what makes a GREAT fit

An organization that needs robust ITIL-aligned processes without adopting a large-scale, highly extensible platform; has internal or partner capability for configuration and integration; and requires formalized governance controls and auditability supported by vendor security documentation.

05The pitch

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

- Alemba’s flagship product is Alemba Service Manager (ASM), an IT Service Management (ITSM) and Enterprise Service Management (ESM) platform. The product is designed to support ITIL-aligned workflows (incident, request, change, problem, CMDB/asset-related processes) and provides configurable automation and reporting. - Vendor materials describe focus areas including request fulfillment, workflow automation (no/low-code), and applicability to regulated or complex organizations such as healthcare, government, and financial services.

Target market and market positioning

- The vendor presents ASM as targeting mid-market to enterprise organizations that require structured ITIL/ITSM governance and extensibility beyond IT (for example, HR service delivery). - Vendor materials also state ASM supports Managed Service Provider (MSP) use cases via multi-tenant capabilities and per-customer branding/catalogs. - Review excerpts and vendor statements indicate ASM is sometimes evaluated as a lower-cost alternative to larger enterprise suites; such comparisons are vendor- or reviewer-reported and should be validated during procurement.

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

Download full report →