NEST Frontier / Rebrand Live
BAEKHO

Performance Engineering Platform

Baekho Racing

A student racing platform built as a real engineering system.

Baekho Racing develops performance through structure, integration, testing, and iteration. The car is treated not as a visual object, but as a machine that must be understood, built, and improved as one coherent whole.

Current phaseSubsystem planning
Build cycle2026 Cycle 01
Active focusChassis integration
Current targetFabrication readiness
Documentation statusReview log active

01 / Program Review

About the Program

Mission

Baekho Racing develops a student-built race car as a disciplined engineering system, not as a collection of isolated parts. The program focuses on structure, controls, integration, manufacturability, and iterative performance improvement.

Vision

The long-term goal is to build a durable technical platform where each cycle improves the car, the workflow, and the engineering knowledge base behind it.

Method

The team works through subsystem ownership, explicit build stages, documentation, simulation, fabrication, and review. The machine is treated as an evolving system that must be understood before it is displayed.

01

Technical clarity over decorative complexity

02

Evidence over empty claims

03

Subsystem ownership with full-system awareness

04

Continuous iteration across build cycles

Baekho Racing workshop documentation surface.
Fabrication zone

Assembly review happens against real packaging constraints.

CAD station

Digital intent is checked before any part becomes expensive.

Review wall

Decisions are logged so the next cycle inherits method, not guesswork.

02 / Build-State Review

Project Timeline

From foundation to fabrication, each stage reflects a shift in what the team knows, what the machine demands, and what must happen next.

Active phase

Team foundation

Spring 2025Structure defined
What was decided

The initial phase set team roles, the first program scope, and the standard for subsystem ownership.

What was produced

Lead assignments, operating structure, and the first vehicle scope map.

Main blocker

The team needed a realistic machine target before chasing parts or visuals.

Next dependency

Lock technical responsibilities before concept expansion.

Baekho team formation image.
Subsystem highlightOperations
Core roles locked06
Current subsystemOperations

03 / Technical Ownership

Meet the Team

Baekho Racing is organized through technical responsibility. Each member contributes to a part of the machine, but every decision must still serve the coherence of the whole build.

Select a role or roster chip to update the subsystem map.
Team Lead
Chassis / Structure
Powertrain
Controls / Instrumentation
CAD / Design
Operations / Documentation

Team Lead

Benny Lee

Technical ownership

Program direction, integration review, and delivery cadence

Current focus

Holding the current build cycle together across decisions and dependencies

Every subsystem decision has to make the whole vehicle more coherent.
Baekho lead artifact surface.
Build coordination deckIntegration Core

Cross-subsystem review structure and current cycle priorities.

04 / Engineering Record

The work is visible through evidence, not just claims.

The record includes CAD, planning surfaces, workshop evidence, review notes, and the technical artifacts that show how the machine is being built.

Selected record

Geometry review

Evidence note

Packaging and load-path decisions reviewed before fabrication spend.

Spec callout

CAD tile / frame geometry

Compare mode

Digital intent vs fabricated tolerance