Domo vs Railway

10-Q Financial Filing Analysis for Domo (2026-09-03)

For the second quarter ended July 31, 2026, Domo reported total revenue of $76.8 million, down 4% year-over-year, and a GAAP net loss of $9.6 million compared to a net loss of $22.9 million in the prior-year period. Subscription revenue represented 92% of total revenue at $70.4 million. The company faced severe liquidity and covenant compliance issues, remaining in breach of its credit facility's minimum annualized recurring revenue covenant as of April 30, 2026, and July 31, 2026, resulting in substantial doubt about its ability to continue as a going concern. To resolve its debt default and secure liquidity, Domo entered into a definitive Asset Purchase Agreement on July 22, 2026, with Progress Software Corporation. Progress will acquire substantially all operating assets, the platform, customer contracts, and subsidiaries for $400 million in cash. Domo will use the proceeds to repay its $137.2 million debt obligations in full, retain its net operating loss (NOL) carryforwards, and transition into a debt-free holding company trading under a new ticker symbol.

• Domo signed a definitive agreement on July 22, 2026, to sell substantially all operating assets and business to Progress Software for $400 million in cash.
• The company remained out of compliance with its debt covenants as of July 31, 2026, operating under a forbearance agreement requiring sale completion by November 30, 2026, to pay off $137.24 million in debt.
• Q2 revenue reached $76.78 million (down 4% YoY) with a net loss of $9.62 million and cash/cash equivalents of $25.07 million.

8-K Financial Filing Analysis for Domo (2026-09-22)

On September 22, 2026, Domo, Inc. completed the sale of substantially all of its business assets and transferred its operational employees to Progress Software Corporation pursuant to the July 22, 2026 Asset Purchase Agreement. Domo received approximately $221.0 million in net cash proceeds upon closing, retaining its net operating loss (NOL) carryforwards. Concurrently, the company terminated and fully repaid its Amended and Restated Loan and Security Agreement with Obsidian Agency Services and Wilmington Trust, while also repurchasing outstanding warrants for approximately $10.0 million. Following the divestiture, the corporate entity was rebranded as Huckleberry.ai, Inc. via a short-form subsidiary merger, and its Class B Common Stock ticker on the Nasdaq Global Market will change from 'DOMO' to 'HUCK' effective September 24, 2026.

• Completed the asset sale of Domo's core BI and analytics software business to Progress Software Corporation for approximately $221.0 million in net cash proceeds, retaining tax NOL carryforwards.
• Repaid in full and terminated the August 2023 Amended and Restated Loan and Security Agreement, releasing all associated liens and discharging outstanding debt obligations.
• Rebranded the corporate entity to Huckleberry.ai, Inc., repurchased outstanding warrants for $10.0 million, and announced a Nasdaq ticker change from 'DOMO' to 'HUCK' effective September 24, 2026.

New Product Features and AI Announcements Shared at Domo Connections 2026

Domo announced new product features and AI capabilities at its Domo Connections 2026 event, as highlighted in a blog post dated September 18, 2026.

Introducing Railway Authentication via identity-aware proxy

Railway Authentication implements an identity aware proxy at the service or environment level to lock down sensitive http endpoints

AI Agent Frameworks Have a Critical Engineering Flaw

The author argues that the current enthusiasm for AI "agents" and hot frameworks distracts from the real engineering challenges of production systems. They define a true agent as a system with an objective that decides next actions, handles failure, and knows when it is done. In production, most agent deployments are narrow, purpose-built pipelines (e.g., support triage, document extraction, code review). Teams that succeed focus on tool design, failure handling, and observability rather than swapping models. The author highlights a persistent retrieval problem in RAG pipelines—incorrect chunking and metadata cause context loss and hallucinations—and recommends architectural patterns (plan-then-execute, separate retrieval from reasoning, explicit handoffs) and better data representations over framework chasing.

• Author defines an 'agent' as a system with an objective that decides what to do next, handles failure, and knows when it is done.
• Most production AI agent deployments are narrow and purpose-built (examples: customer support triage, document extraction, code review).
• Successful teams prioritize tool design, failure handling, and observability over only upgrading model versions.

Workplace AI Needs a 'Chief of Staff' Control Plane

The article argues that businesses deploying multiple AI agents face 'agent sprawl'—fragmented context, uncontrolled side effects, and human operator fatigue—and proposes a split architecture: a central control plane (an "AI Chief of Staff") that handles governance, state, routing, human-in-the-loop approvals, and executive synthesis, while domain-specific workers perform execution. The author open-sourced a reference foundation called OpenClaw Control Plane (a TypeScript monorepo) on GitHub and recommends standardizing interfaces using the Model Context Protocol (MCP) and a workflow-neutral runtime, with deployment examples using Railway. The repo is presented as an M1 foundation with future plans for worker specs, MCP tool bridges, and operator dashboards.

• The article frames 'agent sprawl' as a common problem where siloed AI tools operate without centralized governance.
• It proposes a control plane (an "AI Chief of Staff") responsible for intake triage & routing, state & cross-functional memory, human-in-the-loop governance, and executive synthesis.
• The author open-sourced the 'OpenClaw Control Plane' TypeScript monorepo on GitHub: https://github.com/yuens1002/openclaw-control-plane.