Poolside
Capability story keeps strengthening while the capital stack stays fragile.
Dimension breakdown
Score · confidenceCapability story keeps strengthening while the capital stack stays fragile. Laguna M.1 (proprietary, 225B-A23B MoE) and XS.2 (open-weight, Apache 2.0, on HuggingFace, free via OpenRouter/Ollama) post 72.5% / 68.2% SWE-bench Verified, now independently reproducible (open weights + May 25 technical report) and served at 256K context.
New 'pool' terminal/CLI agent and Agent Client Protocol support (Zed/JetBrains/Neovim) plus native VS Code/Visual Studio broaden the surface. RTX Corporation now confirmed as a named defense customer.
funding crisis unresolved — $2B Series C collapsed (only ~$250M soft commitments), CoreWeave terminated the Project Horizon lease, Nvidia declined to lead a rescue, Google's 400MW talks went quiet; hiring frozen and site-prep capex paused, though no broad layoffs and runway now reported through Q4 2026.
AWS Bedrock still 'coming soon' (NOT GA — prior eval overclaimed this). Public pricing absent; SOC 2/ISO 27001/FedRAMP still unconfirmed. funding-concerns + pricing-opacity caps applied.
Use cases
Not yet assessed — this section fills in as ACES research covers the tool.
Risk flags
Pricing opacity
enterpriseConditionalNo public pricing or highly opaque pricing model
Caps Enterprise / Compliance at 75
Removed when — Public pricing published with clear tier structure and no hidden costs reported
Funding concerns
stabilityTemporaryFunding or runway concerns
Caps Enterprise / Compliance at 50
Removed when — Successful funding round or sustainable business model demonstrated
Status rationale
Tracked retained. Independent reproducibility of the Laguna benchmarks (open weights on HuggingFace, free OpenRouter serving, May 25 technical report) and the named RTX customer reference strengthen the evidence base, and the new 256K context, 'pool' CLI agent, and ACP surface lift autonomy/integration/context.
Tracked remains correct because: (1) no hands-on or production validation by our team — the RTX contract lacks disclosed production metrics; (2) the funding-concerns cap (maxSignalLevel Detected per scoring-caps.ts) is applied as a Compliance dimension cap rather than a hard signal-level cap, given growth signals (headcount ~345, named customer, open-weight traction) offset distress; (3) AWS Bedrock is still pre-GA; (4) SOC 2/ISO 27001/FedRAMP remain unconfirmed and pricing is opaque. Hold.
Movement triggers
Upgrade to Assessed if: rescue/bridge or Series C closes with named investors, SOC 2 Type II confirmed publicly, hands-on or third-party production evaluation completed, OR Bridge/pool multi-agent capabilities independently validated at scale. Downgrade to Detected if: broad layoffs announced, executive departures, OR distress signals (delayed payroll, vendor disputes, missed customer commitments).
Hold Tracked if: status quo of cash conservation + open-weight traction + named-but-unmetered enterprise contracts continues without funding resolution.
Risks & limitations
Funding Concerns
ModerateRadar cap: funding-concerns
Pricing Opacity
ModerateRadar cap: pricing-opacity
Integration surface
Not yet assessed — this section fills in as ACES research covers the tool.
Adoption & benchmarks
Not yet assessed — this section fills in as ACES research covers the tool.
Spotted something wrong or missing here? Suggest a change →
Per-source contributions
Click any dimension to see the underlying sources and citations.
More in this category