Available
Demonstrated in the current production environment with current release evidence.
Product profile
A governed operating layer for self-storage.
Facily OS is the working product identity for a self-storage operating platform in development. Its direction is to connect facility workflows, evidence, controls, automation, and decision support without obscuring the system of record or accountable owner.
Product definition
One identity. Explicit boundaries.
- Product name
- Facily OS
- Category
- Self-storage operating platform
- Current status
- In development, with an invited-user workspace
- Intended users
- Self-storage owners, operators, and facility teams
- Company context
- Developed within the Facily.ai company-building program; final legal ownership and provider identifiers pending governing-record reconciliation
01
Public status register
AreaStatusPublic boundary
Invited-operator workspaceLimited release
A private access surface is live for invited users; this does not establish general commercial availability.
Facility workflow controlsIn development
Workflow design and implementation are active; individual functions require release evidence before public feature claims.
Multi-facility operating controlsIn development
The platform direction includes cross-facility visibility and accountability, with public scope still constrained.
AI-assisted decision supportIn development
Assistance is designed around source evidence and human accountability; outcomes are not represented as autonomous facts.
Public documentation and release notesPlanned
A public documentation layer is part of the authority architecture but is not yet released.
Named integrations and pricingAwaiting verification
No named integration, compatibility, availability, or price is claimed here without current technical and commercial evidence.
This register describes product areas at a high level. It is not a feature-completeness, security, compatibility, or commercial-availability statement.
02
Status vocabulary
Beta
Available to an identified test group inside a documented beta boundary.
Limited release
Available only to named organizations, properties, roles, or invited users.
In development
Implemented or actively being built but not generally available.
Planned
Approved roadmap work without a completed public release.
Conceptual
A research or design direction without an approved release commitment.
Operating standard
Four distinctions every system should preserve.
- 01Suggestion versus fact
A model output is guidance until it is supported, accepted, and owned.
- 02Activity versus outcome
An internal action is not the same as an external system accepting, posting, delivering, or reconciling it.
- 03Source versus display
The interface should identify the governing source, freshness, and known limitations.
- 04Roadmap versus release
Planned and conceptual work should never inherit the language of available product capability.