How it works
Product lifecycle management for engineering teams. What Ciclo does, what it’s built with, and how far along it is.
The premise
Ciclo is the suite’s PLM app. It tracks components and their revisions, bills of materials, and engineering change orders with multi-step approvals, with separate roles for engineering, operations and sales.
It was the last app to join the suite. Moving it over meant dropping its own look and switching to the shared design tokens and components, and its build now fails if it strays from them.
What’s included
Components with specs, attachments and revision history, released through change orders
Bill of materials management with where-used lookups, plus compliance declarations
Create, route and approve ECOs across several stages
Roles for admin, engineering, operations, sales and read-only viewers
How it’s built
Ciclo is built on Next.js, React 19, TypeScript, Firestore and Tailwind CSS.
The repository is 99% TypeScript by volume.
It carries 166 commits since Jul 2026, most recently changed in Sep 2026.
How the work is done
Every project here starts as a written spec, and the spec stays the source of truth once there’s code. The repository keeps a build plan with current status, an append-only decision log of where the code departed from the plan, and a handoff document that describes where things stand, including the unfinished parts.
That’s how one person keeps this many projects moving, and it’s what this page is written from.
Current state
In development. Being worked on now.
The source is private, so the way to check what this page says is to use the product.
Next
Bring Ciclo into your company
Ask about onboarding your organization, moving existing records over, or a demo.