From reporting to challenge
ΛLIΞNΛ compares reported status with the underlying evidence and highlights unsupported green ratings, inconsistent forecasts and missing governance decisions.
← Back to ΛLIΞNΛ8.0 6.5 6.9 2.0
ΛLIΞNΛ Research · September 2026
2026 PPM Platform Benchmark
ΛLIΞNΛ scored against twelve weighted criteria for project, programme and portfolio management, with the evidence and limits behind every score. Use the same criteria to evaluate any platform on your shortlist.
Disclosure: this is ΛLIΞNΛ's assessment of its own product using the published methodology below. It is not independent analyst research, a paid placement or a claim of market leadership. Scores are indicative and date-bound, and should be validated through procurement due diligence and product demonstrations. ΛLIΞNΛ does not score other vendors. Where other platforms are mentioned, the page states only what their own public documentation says, with a link and the date it was checked. It makes no claim that ΛLIΞNΛ is better than any other platform.
What differentiates ΛLIΞNΛ
ΛLIΞNΛ is designed as a governance-intelligence layer: it connects delivery, financial, risk, dependency, resource, benefit and approval evidence, then challenges the reported position before it reaches a decision-maker.
Evidence and confidence are visible
AI-generated findings retain linked evidence and confidence so executives can see why a conclusion was reached rather than receiving an unexplained answer.
Governance is part of the operating model
Demand, investment, stage gates, approvals, changes, baselines and audit history are connected to delivery—not maintained as a separate compliance exercise.
Designed for decisions
ΛLIΞNΛ leads with the decisions, consequences and actions that need leadership attention, with the supporting dashboards one step behind.
Why ΛLIΞNΛ scores 6.9 for capability and 2.0 for maturity
Version 1.0 of this benchmark scored ΛLIΞNΛ at 8.3 for capability and 5.0 for maturity. Those figures were not backed by a published per-criterion assessment, and they gave too little weight to how much of the product had been proven in testing. They have been lowered. We now separate what the product can do from how reliably it has been shown to do it, and from how established the company is.
Functional breadth (assessor judgement)
ΛLIΞNΛ covers governed demand, portfolio-to-project hierarchy, approvals, stage gates, RAID, dependencies, financials, resources, benefits, executive briefings and evidence-backed AI. This rates feature coverage only. It is not part of the weighted calculation.
Enterprise reliability and assurance (assessor judgement)
Tenant isolation, approval integrity and financial reconciliation are now tested against staging on every change. There is no security certification yet, the review of privileged server access is still in progress, and there is no load or scale evidence at enterprise volumes. Until that work and customer operating evidence exist, the product cannot score as an enterprise-proven platform.
Product capability (published)
This is the weighted result of the twelve criteria below. It counts only features that are implemented and demonstrable, and it reduces a score where testing is incomplete.
Market maturity: pre-commercial
ΛLIΞNΛ has no paying customers, reference customers, partner ecosystem or implementation record yet. The score will rise only when founding pilots, customer references and operating evidence exist.
| Criterion | Weight | ΛLIΞNΛ /10 | Evidence and limits |
|---|---|---|---|
| Portfolio, programme and project hierarchy | 10% | 7.0 | Portfolio, programme, project and small-works structures are implemented. A staging test run on every change sweeps all 353 tenant tables and views for cross-organisation reads and writes (105 of them checked against real data from other organisations), and attempts cross-organisation inserts and role self-promotion. None succeed. |
| Demand and investment governance | 10% | 7.5 | Demand intake, scoring and conversion into governed delivery are implemented and tested. |
| Stage gates, approvals and auditability | 12% | 7.5 | Gates, approval chains and audit history are implemented. The database refuses decisions made outside the approval workflow, locks submitted changes, and keeps the approval audit log append-only. An attack suite run on every change tries self-approval, wrong and foreign actors, replay, races, and direct tampering with decisions, steps, approver slots and audit records. |
| RAID, dependencies and change control | 10% | 7.5 | RAID, dependency blast radius and change requests are implemented and connected to delivery. |
| Financial planning and control | 12% | 6.5 | Budgets, forecasts and financial lines are implemented. A canonical finance fixture with deliberate decoys is reconciled to the penny on every change, from ledger, purchase-order and baseline records through the project, dashboard, AI-evidence and enterprise roll-up figures. Reconciling exports and AI answers on a running deployment is not yet automated. |
| Resource and capacity management | 10% | 6.5 | Allocations, capacity, heatmaps and timesheets are implemented, but with less planning depth than established resource tools. |
| Benefits and strategic alignment | 8% | 6.5 | Benefits register and strategy-to-value tracing are implemented, with limited operating evidence. |
| Executive reporting and decision support | 10% | 7.0 | Command centre, executive digest and governance drift views are implemented on live product components. |
| AI, evidence and reporting confidence | 8% | 7.5 | AI findings carry linked evidence and confidence, and governed actions need human approval. This is ΛLIΞNΛ's strongest differentiator. |
| Integrations and extensibility | 5% | 4.5 | There are a small number of connectors and no partner ecosystem. |
| Security and enterprise controls | 3% | 6.0 | Row-level tenant security and role checks are implemented and tested against staging on every change. There is no SOC 2 or ISO 27001 certification yet, and 59 server files that use privileged database access are still being reviewed one by one. |
| User experience and adoption | 2% | 5.0 | There is no customer adoption data yet. |
| Weighted capability | 100% | 6.9 | The sum of each weight multiplied by its score. The unrounded result is 6.86. |
Our internal target is a capability score of 7.2. The tenant-isolation, approval-integrity and financial-reconciliation tests that this target depended on are now in place. What remains is the privileged-access review, automated reconciliation of exports and AI answers on a running deployment, and load testing at enterprise volumes. We reassess the score after each major release.
ΛLIΞNΛ’s 24-month maturity pathway
ΛLIΞNΛ’s objective is to move market maturity materially closer to product capability over the next two years. That will come from operating evidence, not from the passage of time. Maturity will not rise to 8 or 9 just because two years have passed. It will rise as repeatable implementations, reference customers, independently evidenced outcomes, a partner ecosystem, security assurance and adoption at scale are achieved. This is an aim, not a forecast, and each edition of this benchmark will raise the maturity score only when the evidence supports it.
0–6 months
Recruit founding pilot customers, measure their outcomes and publish implementation evidence. Complete the privileged-access review and load testing at enterprise volumes. (Tenant-isolation, approval-integrity and financial-reconciliation testing completed October 2026.)
6–12 months
Build reference customers, procurement evidence, assurance maturity and a consistent customer-success model.
12–24 months
Demonstrate multi-organisation scale, expand the integration and delivery ecosystem, and evidence sustained customer outcomes.
How progress is scored
Customer references, implementation repeatability, retention, ecosystem strength, independent validation, security assurance and scaled adoption.
Assessment methodology
Each criterion is scored from 0 to 10, multiplied by its published weight and combined into the capability result. The ΛLIΞNΛ scores and the evidence behind them are published above. A score of 5 means a credible core capability; 8 means broad, enterprise-relevant depth; 10 requires exceptional, evidenced leadership. Roadmap features are excluded until implemented and demonstrable. Where testing is incomplete, the criterion score is reduced.
Portfolio, programme and project hierarchy10%
Demand and investment governance10%
Stage gates, approvals and auditability12%
RAID, dependencies and change control10%
Financial planning and control12%
Resource and capacity management10%
Benefits and strategic alignment8%
Executive reporting and decision support10%
AI, evidence and reporting confidence8%
Integrations and extensibility5%
Security and enterprise controls3%
User experience and adoption2%
Evidence standard and limitations
ΛLIΞNΛ's scores are based on its current implemented and tested capability. For other platforms, use these criteria with each vendor's official product information below. Public documentation varies in depth, licensing tiers can change what is available, and configuration or partner extensions can materially change outcomes. Use these criteria to frame evaluation questions, not to replace a requirements-led procurement exercise.
Benchmark your governance model
See ΛLIΞNΛ against your real PMO requirements
Bring one live governance challenge. We will map it to the benchmark criteria and show the relevant ΛLIΞNΛ workflow in a focused 30-minute demonstration.
Book a benchmark-led demoEditorial policy
Published 2026-09-22. Version 1.1 (2026-10-08): ΛLIΞNΛ's scores were lowered from 8.3 to 6.9 for capability and from 5.0 to 2.0 for maturity, a per-criterion assessment was added, and competitor scores were labelled as unverified estimates. Version 1.2 (updated 2026-10-10) removed all scores for other vendors; any comparison is now limited to what their own documentation says, with sources. Version 1.3 (2026-10-10) raised four ΛLIΞNΛ scores after new tests ran against staging: tenant isolation across every tenant table, approval-tampering attacks (which found and closed gaps that let a member approve or edit a change request and rewrite the approval audit log), and penny-exact financial reconciliation from source records. The benchmark is reviewed quarterly and when a material product change affects a score. Vendors or readers may request a correction by emailing support@aliena.co.uk with public evidence. Corrections change the page’s modified date and are recorded in the next published version. Product and company names belong to their respective owners.