Radwerkx is where engineering leaves the screen and becomes something physical. Vehicles, prototypes, fabrication, architecture, systems and the problem-solving behind all of it.
Selected work
Keeping an old truck useful, then pushing it further: repair, alignment, drivetrain planning, fabrication and the long-term build.
An old Yamaha brought back as a purposeful road machine — rewired, simplified and rebuilt one system at a time.
A modular off-grid platform for temporary lighting, security, communications, power and site services.
A 60 × 40 ft integrated home, workshop and studio developed around structural clarity, mechanical systems and local-first automation.
Maintenance, setup and ownership of a machine that rewards precision.
A compact testbed for the Radwerkx product-development process: CAD, printed parts, a simple electrical system and rapid iteration.
The continuum
Radwerkx is less about finished objects than the chain of decisions that turns an idea into one. The archive matters. So does whatever is on the bench right now.
Repairs, engineering work, prototypes and projects that established the methods behind Radwerkx.
The truck, bikes, CAD work, electronics, fabrication and product experiments currently taking shape.
Products, systems and architecture moving from sketches and calculations toward something real.
How the work happens
Watch the process
The useful part is rarely the reveal. Radwerkx documents the diagnosis, decisions, mistakes, fixes and fabrication that happen before the finished result.
Behind Radwerkx
I’m Jason Conrad. Radwerkx is the place where the engineer, project manager and compulsive builder parts of my brain get to work on the same problem.
My professional background is in civil engineering, construction, industrial operations and project delivery. Outside that lane, I have always been pulled toward machines, products, architecture, electronics and figuring out why something was designed the way it was.
Radwerkx is the record of that process: understand the system, decide what matters, build the solution and document enough of it that somebody else can learn from it too.
