Five runners.
One moving support platform.
Eos began on the road, not in a meeting room. We are half-marathon runners who hit the same wall on every long run — and decided to build our way through it.
The shared brief
Support was never moving with us.
Wearables could describe a run after it happened — pace, heart rate, a map of where we had been. But they could not deliver the physical support runners needed while moving: water, light, safety, a way to coordinate when the group splits.
That contradiction became our shared brief: make support move with the runner. Not another fitness device — a new layer of continuous mobile training support.
One line we run by
"Wherever runners move, support should move with them."
Lived running experience, product judgment, engineering execution, design and commercial strategy — on the same side of the same problem.
The team
The people behind the dawn.
Five roles, one prototype on the bench, and a shared rule: never publish a number we didn't measure.
杨思铖 Alex
Shapes product strategy and connects technical decisions to user needs — the thread that keeps the whole run coherent.
任景新 Jing
Leads systems engineering and integration — making perception, decision and control behave as one deterministic platform.
侯珺沣 Jim
Develops the robotic platform and turns concepts into testable prototypes — the chassis that actually follows on the greenway.
谢辰悦 Audrey
Leads product and experience design — translating complex technology into a clear brand and a market story runners understand.
杨力瑞 Jerry
Leads market validation, partnerships, business modeling and fundraising — turning a working prototype into a supported mission.
TOGETHERWe combine lived running experience, product judgment, engineering execution, design and commercial strategy — building Eos not as another fitness device, but as a new layer of continuous mobile training support. Wherever runners move, support should move with them. Evolve. Outrun. Shine.
How we work
Small team, hard rules.
Four principles keep the prototype honest and the project moving.
Every decision is tested against a real training session. If it doesn't survive a pre-dawn long run, it doesn't ship.
Bench → controlled field → user trial. Nothing unfinished is presented as finished, and every figure is labelled by status.
Every risk has a control and a defined fallback state. The safety boundary is designed before the feature it protects.
Product, engineering, design and market work on the same run — not five separate projects wearing one name.
If you build, test or run — and you want to help a support platform that actually moves — we're looking for hands in robotics, design, safety and field trials. Start with the conversation channel on the About page.