How it works
Product lifecycle management for engineering teams. The full technical description of Ciclo — what it does, what it is made of, and what state it is in.
The premise
Ciclo is the PLM product in the suite: components with revisions, bills of materials, engineering change orders with a multi-stage approval workflow, and role-based access for engineering, operations and sales.
It joined the shared tenancy after the other products and was migrated onto the common design tokens and component library, replacing its own visual identity. Its build fails if it drifts back off the shared platform.
What is included
Components with specifications, attachments, revision history and a Draft → Review → Released → Obsolete workflow
Bill of materials management with where-used analysis
ECO creation, routing and multi-stage approval
Role-based access control across admin, engineering, operations, sales and viewer roles
How it is built
Ciclo is built on Next.js, TypeScript, Firestore and Tailwind CSS.
The repository is 99% TypeScript by volume — a description of what the work actually consists of rather than what it is filed under.
It carries 134 commits since Jul 2026, most recently changed in Sep 2026.
The method behind it
Every project here starts as a written specification, and the specification stays authoritative once code exists. The repository keeps a build plan with live status, an append-only decision log recording where the implementation departed from the plan, and a handoff document describing the true current state — including the parts that are not finished.
That is why a portfolio this wide is not a shallow one, and it is why this page can describe the product without overstating it.
Current state
In development. Under active work right now.
The source is private. What this page claims is checkable against the product itself, not the repository.
Next
Bring Ciclo into your company
Ask about onboarding an organisation, migrating existing records, or a demonstration.