In development · Hosted service
Ciclo
Track parts, bills of materials, and change orders, with a clear revision history for each.
Engineering teams that are tracking parts and revisions in spreadsheets.
REG-1 Regulator
Rev 1 Rev 2
Released
- Engineering Reviewengineering or admin
- Operations Reviewoperations or admin
- Final Approvaladmin
A draft change. Engineering or an admin submits it, then each step needs one signature from a listed role.
Where used All levels, up to the top assemblies
| Level | Part | Top |
|---|---|---|
| 1 | CMP-00042 Controller board | |
| 2 | ASM-1 Frame assembly | Top assembly |
What it does
Product lifecycle management for engineering teams.
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.
- 01
Components with specs, attachments and revision history, released through change orders
- 02
Bill of materials management with where-used lookups, plus compliance declarations
- 03
Create, route and approve ECOs across several stages
- 04
Roles for admin, engineering, operations, sales and read-only viewers
Roles
Everyone sees the same part. Not everyone can change it.
Each step in a change’s workflow lists the roles that may sign it. Who’s on the reviewer list doesn’t matter; the role does. A company can rename steps, add them, require every named approver, or send a rejection back to an earlier step.
Admin
Full access, manage team, override approvals.
Engineering
Create/edit components, create ECOs.
Operations
Review and approve ECOs.
Sales
View components, approve ECOs.
Viewer
Read-only access to components and ECOs.
Revisions
Revisions only move through a change order.
Revision schemes are set per part class: numeric (1, 2), alpha, alphanumeric or semantic. New companies start on numeric. The alpha scheme follows ASME Y14.35 and skips I, O, Q, S, X and Z, since they’re easy to misread. When a change is implemented, the old revision is archived and kept.
- A
- B
- C
- D
- E
- F
- G
- H
I- J
- K
- L
- M
- N
O- P
Q- R
S- T
- U
- V
- W
X- Y
Z- AA
After Z comes AA. Before release, a part can carry prototype revisions (01, 02 or X1, X2) and take A when it’s released.
Part of Bottega
One company, one login, four apps.
Ciclo shares its company record, member list and design with the rest of the Bottega suite. Turning on another app for someone is a permission, not a new account.
Specification
What it’s built with, and when.
Pulled from the repository each time this site is built.
- State
- In development
- Discipline
- Business platform
- Shape
- Hosted service
- Started
- Jul 2026
- Last change
- Sep 2026
- Commits
- 166
- Next.js
- React 19
- TypeScript
- Firestore
- Tailwind CSS
- TypeScript 99%
Next
Bring Ciclo into your company
Ask about onboarding your organization, moving existing records over, or a demo.