8090 Solutions

Executive Summary

8090 Solutions sells Software Factory, a commercial workspace connecting business requirements, architecture, and implementation context. It also operates 8090 Enterprise, where its team designs, builds, hosts, and maintains customer applications. Those are different buying decisions: adopting a development platform versus commissioning a managed system. ^[1][2]

The June snapshot is materially outdated. The company has announced outside financing, renamed its modules, added agent and integration features, and published more specific modernization evidence. The central evaluation question remains whether shared context and governance improve your delivery process enough to justify another platform.

See Autonomous Agentic Engineering Tools for adjacent approaches to coordinating development work.

Product and Workflow

The product page now names five core modules: ^[8]

The current quickstart connects GitHub or GitLab repositories for indexing, adds supporting documents, and guides users through requirements, blueprints, and work orders. External coding agents can retrieve work and update status through MCP using a project-and-user-scoped API key. Completed work enters review; the guide also describes checking code/document drift after pushing to the indexed branch. This is a documented workflow, not a guarantee of correct generated code. ^[9]

Recent shipped changes include GitLab integration in July, durable cloud agents and a Skills module in August, and skill rules, tracked-change review, and automation tools later that month. September's v0.51.0 adds custom work-order statuses and agent awareness of the user's allowed actions. These release notes are better evidence of current availability than an undated list of planned capabilities. ^[6]

8090 describes a knowledge graph connecting the artifacts and propagating context changes. The reviewed public documentation establishes that product model; it does not establish the underlying database design, prove that documentation cannot drift, or replace a workload-specific evaluation. ^[1]

Enterprise Delivery and Adoption

EY.ai PDLC: EY's March 18, 2026 announcement identifies Software Factory as a platform behind its product-development initiative and plans deployment across tens of thousands of EY US consultants. That is a rollout plan, not a verified active-seat count. Its 70% productivity/cost-efficiency improvement, 80-times delivery speed, and 95%+ test coverage are attributed to an EY use case without a reproducible benchmark protocol in the announcement. They should not be treated as expected customer results. ^[4]

CMS ClaimsCore: 8090 describes business-rule extraction from 18 million lines of Assembly and COBOL, with rules traced to source and reviewed in a dedicated application. Its own case study says it is one of several contractors, disclaims CMS endorsement, and labels the sample code/rule visualization illustrative. This supports a specific modernization engagement, not exclusive responsibility for Medicare's replacement systems or independently verified extraction accuracy. ^[10]

The Enterprise page describes an engineering-led delivery process, with 8090 operating the resulting application. That ongoing service relationship matters when comparing its annual commitment with per-seat software pricing. ^[2]

Pricing and Ownership

Published USD pricing remains: ^[7]

The pricing page does not provide token rates or a sample workload bill, so a complete cost estimate needs those details. Release notes also describe free View seats for members who only view and comment; verify role eligibility when sizing paid seats. ^[7][6]

The earlier blanket claim that Enterprise customers do not own codebase IP is not supported by the current public pricing page. The published general terms distinguish 8090's service technology from user content: customers retain input rights and receive the company's rights, if any, in output generated specifically for them. Those terms also allow content use to operate and improve the service and models. They do not establish the deliverable, portability, or data-use terms of a negotiated Enterprise contract. ^[11]

Funding and Viability

Palihapitiya's June 29 announcement describes a $135M Series A led by Salesforce, with WNDR, Craft Ventures, The Production Board, LAUNCH, and angels participating. The homepage qualifies the funding headline as inclusive of seed funding. This review preserves that distinction rather than adding an inferred seed round to the headline or presenting $135M as an unambiguous incremental round amount. ^[5][3]

The financing and delivery engagements are meaningful evidence of resources and commercial activity. They do not establish profitability, retention, or a support guarantee. Assess those through the proposed service agreement and references relevant to your deployment.

What Developers Say

A substantive independent trial does exist. Franck Verrot's March 22, 2026 review describes testing Software Factory on an open-source project. He found structured requirements useful, reported friction connecting an already-authorized repository, and questioned whether a solo developer gains enough over disciplined prompts and documentation. He distinguishes his own trial from a sales demonstration of work orders. ^[12]

His criticism about understanding existing code is historical: current onboarding explicitly offers initialization from an existing project, and later releases document drift comments, knowledge-base features, and version-history tools. Those changes address relevant workflow areas, but this review did not rerun his trial to establish whether his concerns are resolved. ^[9][6]

Where Tembo Fits

Disclosure: Ry Walker is Tembo’s co-founder and CEO. Tembo is discussed here as an adjacent platform. ^[13]

Tembo belongs in this evaluation because it coordinates coding-agent work from tickets, alerts, schedules, and webhooks, returning changes for review. Its documented examples include Linear issues, Sentry remediation, and recurring dependency work. ^[14] Software Factory's documented forward workflow begins with requirements and blueprints, then packages work orders for external coding agents. ^[9]

My assessment is that they address different parts of a development operating model: 8090 emphasizes shared product and architecture context, while Tembo emphasizes running and coordinating agents against connected work. A team may need one or both; a combined workflow would require validating the handoff rather than assuming a turnkey integration. Compare the platform needed to maintain development intent with the platform needed to execute and review tasks.

Assessment

Best fit: organizations with substantial coordination and modernization work, where product, architecture, and implementation decisions need a shared record. Evaluate self-serve Software Factory and managed Enterprise separately, with a representative project and measurable acceptance criteria.

Poor fit: a small team whose existing repository documentation already supplies sufficient context, or a procurement process that cannot establish usage costs and deliverable rights before commitment.

The evidence now supports a better-funded company with shipped workflow improvements and concrete delivery relationships. It does not justify universal speed claims. This refresh verified the cited material on September 15, 2026; it did not use Software Factory hands-on, inspect a customer contract, or audit the reported outcomes. See the research methodology.