v1 · planned scope
Structure
Teams, leads and skills on one chart, with layers for risk and change.
The operating system for your engineering org.
Org structure, engineering knowledge and AI enablement, with a phased roadmap for cited, access-scoped agent answers.
Move your cursor or tap the otter.
About RenX OS
Built for the people behind engineering.
RenX is an internal-first Engineering OS for enterprise teams. It brings organization structure, engineering knowledge and AI-enabled work into one access-aware workspace, so people can understand how teams, skills and delivery fit together.
“Ren” comes from rèn — to train and forge. “X” stands for people × AI: working together, with people accountable for decisions.
Milestones
2025 — 2026RenX is founded at Enouvo
The idea grows from the needs of a working engineering organization: make structure, capability and AI practice easier to understand together.
A distinct product identity takes shape
The RenX design system sets its Cinder red and cool slate palette, industrial typography, and a visual mark for people × AI.
The Engineering OS blueprint is defined
Product boundaries and release stages are documented. The v1 plan centers on Home, Structure and AI Workspace Drop 1.
The public preview opens
RenX’s product direction and roadmap are introduced at renx-os.com while the platform continues toward its first release.
A quick tour, one module at a time.
Product preview. Labels show planned release scope; v1.1 capabilities are planned for 2027.
v1 · planned scope
Home
Opens on what needs you, whether you lead the org or ship the code.
v1.1 · planned for 2027
Wiki
Planned native Wiki: owned pages, scheduled reviews and linked SharePoint files.
v1 · drop 1 scope
AI Workspace
v1 includes policies, tools and the AI Squad; learning paths and certifications are planned for v1.1.
v1.1 · planned for 2027
RenX Agent
Illustrative sample answer. Planned for v1.1: cited answers scoped to the asker’s access, plus drafts that a person approves.
Connect to trusted systems.
The product plan reads from Entra ID, Microsoft 365, Enoverse and DeliverX. RenX keeps only a narrow, approved copy for its own views and never writes back. Setup time depends on source readiness and permissions.
A sample org, at a glance.
0people on one chart
0teams and branches
0AI mentors in the squad
0AI levels, L1 to L4
SAMPLE DATA · Figures from the fictional Northwind demo tenant.
Trust controls are part of the design.
Microsoft Entra ID
Microsoft sign-in is the only sign-in method in the product plan.
Read-only external sources
RenX will not write to connected systems; it retains only the narrow, approved fields it needs.
Access-scoped answers · v1.1 planned
Planned for 2027: answers cite sources and stay within the asker’s permissions.
Tenant no-training terms · v1.1 planned
Provider no-training terms are a launch requirement and must be confirmed before use.