Hardware ODM
- ODM development and manufacturing of robot and device hardware
- Electronics sourced and built with partner factories across China
- Procurement of motors, sensors and batteries
GlidyX Inc. / TokyoHardware · Firmware · Systems
Be sincere.
Make our world a little better.
We design and build electronics, firmware and control systems for medical and robotics products — measured first, audited at every change, and handed over with the evidence.
01 What we do
From circuit to mass production.
One accountable partner from the first schematic to the shipping box — with partner factories in China for fast, flexible ODM.
System Design
- Electronic circuit design and control-board development
- Embedded firmware design and development
- Planning and development of own-brand products
- Design of production test systems with tamper-proof cloud record storage
AI & Robotics
- ROS 2-ready, AI-enabled edge devices
- Robot control systems, designed and built
- Mechatronics for medical, care and welfare use
02 How we work
Five steps. Every change.
- Measure
- Decide
- Build
- Audit
- Hand over
01
Measure
Before touching a design, we characterise what it does today — on the bench, with real signals. The fix starts from evidence, not from a guess.
Output baseline measurements, characterisation tests
02
Decide
Options are laid out with a recommendation, grounded in the exact manufacturer datasheet for the exact part. The decision and its reasoning are written down.
Output decision record, cited sources
03
Build
Test first, then code. Each change is small, isolated on its own branch and run against the full regression suite before it is committed.
Output failing test → passing test → regression run
04
Audit
Several reviewers other than its author check every change against the software life-cycle and risk requirements. Their findings are reconciled in writing.
Output audit reports, reconciliation
05
Hand over with evidence
You receive the change, and everything needed to defend it: the record, the tests, the build, and the audit trail.
Output change record your QA team can file
03 Our rules
Rules we don't bend.
Not volume. Discipline — the parts of our process that hold on every change.
- 01
Every firmware change is checked by several reviewers other than its author before it is accepted.
- 02
Engineering decisions are written down with their reasoning and sources.
- 03
The full regression suite runs before every firmware commit.
- 04
Every engineering record is kept in more than one place, with every earlier version still traceable.
04 Records
Records that last.
In medical devices, a record is only worth keeping if it can still be checked long after the work is done. We develop in line with IEC 62304 and record what was decided, when, and why — every time.
REC / 01
Our own records, kept in more than one place
Design decisions, test records and firmware are kept in more than one place, and earlier versions can always be traced back.
REC / 02
Inspection records, beyond rewriting
For production test systems, we design the system so that each inspection record goes to the cloud in Tokyo as soon as it is made, and cannot be altered or deleted for the period you set. We also build in an end-of-day check that compares on-site and cloud records and flags anything missing.
01On siteInspection record
02Cloud · TokyoLocked for a set period
03ReconcileBoth compared, gaps flagged
05 Medical-grade
We develop in line with IEC 62304 software life-cycle, ISO 14971 risk management, ISO 13485 quality systems and IEC 60601-1 electrical safety.
* Not ISO 13485 certified.
MED / 01
Designed against the standard
Circuit and firmware design mindful of IEC 60601-1 electrical safety and CISPR 11 EMC requirements from the first revision.
MED / 02
Traceable by default
Fixed part numbers, datasheet-backed decisions and a change record for every modification.
MED / 03
Evidence your QA can use
Audit reports and test results delivered in a form that slots into your own design history file.
06 Before / After
Measure first, then fix.
A control loop that overshoots and rings, and the same loop after tuning (illustration).
Illustrative step response · dashed line = setpointOvershoot and ringing → settled, within band
07 Message
We don't advise. We build.
We are not just consultants; we are a technical partner that actually builds things.
Drawing on years of hands-on hardware ODM experience and a global supply-chain network, we support you from planning through prototyping to mass production — fast, flexible, and honest about what the measurements say.
Founder / CEOYuichi Aoyagi
08 Core values
What we hold to.
Six principles behind every decision we make.
Sincerity
Be honest with people, technology, and society.
Curiosity
Keep learning, keep wondering.
Challenge
Move before you hesitate.
Partnership
Build the future together, as equals.
Professionalism
Take pride in your work and do it right.
Contribution
Make small, gentle changes for the better.
09 Company
Company profile
| Company name | GlidyX Inc. |
|---|---|
| Representative | Yuichi Aoyagi |
| Established | December 3, 2025 |
| Capital | 3,000,000 JPY |
| Head office | Hikari Bldg 4F, 1-2-1 Hiroo, Shibuya-ku, Tokyo 150-0012 |
| Phone | +81 3-6378-7324 |
| Corporate number | 7011001174271 |
10 Contact
Let's measure it.
Tell us about your board, prototype or problem. We listen first, then propose how to measure and evaluate it, together with a quotation.