Factory OS
Factory OS (styled Factory_OS) is an off-site construction company founded in 2017 by Rick Holliday and Larry Pace that industrialized multifamily and affordable housing production on an assembly line inside a 275,000-square-foot facility in Building 680 on Mare Island in Vallejo, California. Union carpenters build wood-frame housing modules across roughly two dozen stations in a 33-step process, and the finished modules are trucked to the project site and assembled — an approach the company says cuts production time by about half and production cost by a quarter against conventional site-built construction. It raised roughly $132 million across three rounds, including $60 million from JPMorgan Chase and Saint-Gobain in 2021, and delivered more than 4,000 homes across California and Hawaii, about 90 percent of them affordable housing. In May 2024 the company was recapitalized and renamed Harbinger Homes (legal entity Harbinger Production Inc.), with Tom Smith as CEO and Kevin Brown as president; factoryos.com now 301-redirects every path to harbinger.homes. Harbinger filed a WARN notice on 12 February 2026 covering all 280 employees, citing a lack of new business and loss of capital funding, with layoffs beginning 13 April 2026. Factory OS is a manufacturer of physical housing modules, not a software company: it operates no developer program, API, SDK, webhook surface or machine-readable specification of any kind, and its GitHub organization has no public repositories.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Factory OS the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Factory OS scores 6.4/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Factory OS manufactures physical wood-frame housing modules on an assembly line in Vallejo, California — after its May 2024 rename to Harbinger Homes, factoryos.com 301-redirects every path (including /api, /docs, /developers and all /.well-known/*) to harbinger.homes, which is a two-URL Framer marketing brochure whose own sitemap.xml lists only / and /contact, and where /openapi.json, /graphql, /llms.txt and every /.well-known/ path return a real 404; no api./docs./developer. subdomain resolves on either domain, and the company's own GitHub organization has no public repositories.
This is an honest zero, not a gap in our research. Factory OS does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://factoryos.com/openapi.json→ HTTP 301https://harbinger.homes/openapi.json→ HTTP 404https://harbinger.homes/graphql→ HTTP 404https://harbinger.homes/llms.txt→ HTTP 404https://harbinger.homes/.well-known/agent-card.json→ HTTP 404https://harbinger.homes/.well-known/security.txt→ HTTP 404https://harbinger.homes/sitemap.xml→ HTTP 200https://harbinger.homes/→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from Factory OS's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/factory-os/"
title="Factory OS on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/factory-os.svg"
alt="Factory OS Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/factory-os/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/factory-os/"
title="Factory OS on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/factory-os/card.svg"
alt="Factory OS Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Factory OS
Each block below is one kind of artifact we hold for Factory OS. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Factory OS — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 5
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/factory-os · machine-readable index on apis.io
This is an independent, third-party profile of Factory OS, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.