HEPH-3D

HEPH-3D

Text to machine

Machines, not models. Describe one in a sentence and get printable, validated files, a costed parts list, and something that works when you assemble it.

Join the waitlist Enter tester code

WINDOWS - MAC - LINUX

Requires Claude Code — runs on the Claude plan you already have.

heph make scout
$ heph make "a robot that drives
    around, sees with a camera, avoids
    obstacles and shows status on a
    screen" --name scout

FORM → PLAN → LAYOUT → ENCLOSE
  → ROUTE → VALIDATE → SHIP → QC

  components chosen and sourced
  openings cut from real keepouts
  harness bundled into shared trunks
  QC PASS — bundle written to disk
Swept collision checks
across every joint's full travel
Printer-aware fits
tolerances your machine can hold
Wiring that survives
stall current, drop, connectors, fuses

If you can describe it, you can build it.

HEPH-3D is a machine-design studio driven by plain language. Say what you want — how it moves, what it does, roughly how big — and it does the CAD, picks real parts you can actually buy, routes the wiring, and hands you files that print and a bill that adds up. No CAD training required. Nothing dumbed down to manage it.

Easy is the entrance, not the ceiling — everything underneath is real, and all of it opens.

Creators & makers

Your first print doesn’t have to be a benchy. Go from an idea to a working, moving thing without ever learning where the fillet button is.

Inventors

Prototype the idea the evening you have it. Iterate by saying what’s wrong — the model rebuilds, the costs update, the files re-export.

Professionals

A real CAD kernel underneath, every clearance and connector inspectable, and the design itself is plain Python in your own files. Easy to start never means locked in.

Not a part. A machine, in parts.

Several bodies at once

Real mechanisms, real electronics at their true hole patterns, wiring, and clearances tuned to your printer and material.

Swept, not just static

Every joint is swept for collisions across its full range of travel before a single file is written to disk.

Plain Python, yours to keep

A design is a module exposing build() → Assembly. Saved to your Documents, never inside the app.

Claude Code, anchored inside the model

Not a chat widget talking to an API — a real Claude session running in your project directory. Click a part, ask about it, and the context goes in for you. Edit the design and the model rebuilds and reloads on its own.

Runs on your existing paid Claude plan — not API credits.
HEPH-3D clip on bluetooth headset · 15 parts · Generic FDM / PETG
The HEPH-3D Studio: a machine exploded along its parting axis, its bill of materials priced, and Claude Code live in the same window
X explode G ghost shells W harness J pose joints N pin a 3D note R rebuild Exploded view finds the axis the machine actually comes apart on.

Nothing exports until it passes

A full validation pass runs before a single file is written — motion, printability, fit and power all checked together. Anything that would only reveal itself on the bed or on the bench fails here instead, with a plain-language reason.

Motion
Every joint swept across its full travel, not just checked at rest.
Printability
Walls, overhangs, watertightness and bed fit, judged in the print orientation.
Fit
Clearances measured against what your printer and material can actually hold.
Power
The electrical side sized for the worst moment, not the average one.

A tight fit your printer can't repeat is a coin toss

Printed parts don't come out at the size you drew them, and no two printers miss by the same amount. Ask for a fit finer than your machine can repeat and some parts will fall together while others split — so that gets caught here, not on the bed.

Every clearance in a design flows through one printer-and-material profile, so it always knows what your setup can actually deliver.

Calibrate once

Print a single coupon, take six measurements, and the profile learns what your machine really does — how holes come out, how the material shrinks, how thin a wall it will hold.

Retarget a whole design to another printer or material with one line.

A netlist will happily pass a robot that browns out

Stall, not running peak

A motor draws far more when it can't turn — which happens on every start-up. Size on running peak and the design passes while the robot doesn't.

Voltage drop with geometry

Worked out once the harness has a real physical path, so a long thin run can't quietly arrive brown-out low.

Connector ratings

The wire is rarely the weak point. Every connector is checked against the current actually passing through it.

Fuse sizing

Sized off the worst case, so it survives inrush instead of blowing at switch-on and teaching you to fit a bigger one.

Every component in the catalogue carries its real dimensions, hole pattern, keepout and current draw. Mount one and the standoffs generate at its true pitch — and the design always tells you which numbers have been verified and which haven't.

Under the hood

For the crowd that reads the spec sheet before the brochure. This is the part hobbyists never have to open — and professionals will want to.

Kernel
Open CASCADE B-rep geometry via build123d — exact solids and booleans, not mesh approximations. STL is an export, never the model.
Design format
A design is a Python module exposing build() → Assembly. Version it, diff it, open it in your own editor — the Studio rebuilds and reloads on save.
Components
Catalogue parts carry true dimensions, hole patterns, keepouts and current draw. Openings are cut from the real keepouts; standoffs land on the real hole pattern.
Validation
Swept collision across each joint’s full travel, printability judged in the print orientation, clearances against your printer-and-material profile, and an electrical pass — stall current, voltage drop, connector ratings, fuse sizing — before anything exports.
Wiring
The harness is routed and bundled into shared trunks, lengths measured along the actual route, gauges sized to the loads they carry.
Output
STLs per part, a costed bill of materials, the wiring plan and a QC report — one bundle, written to disk, yours.
Runtime
Runs on your machine. Claude Code runs under your own account on your existing paid plan — no API keys, no cloud CAD, designs in your Documents and nowhere else.
HEPH-3D Text to machine

Get early access

Join the list for the next build, or enter a tester code if you already have one.

One thing to have ready: Claude Code, installed and signed in. HEPH-3D runs your own Claude, on your own plan.

Request a tester code

Before you install

macOS 11+, Apple Silicon and Intel. Python and the CAD kernel ship inside the app — nothing to install and nothing to set up.

The app is signed but not notarised yet, so macOS will claim it “could not verify HEPH-3D is free of malware” and offer only Move to Trash. Nothing is wrong with the build. Drag it to Applications, then run this once:

xattr -dr com.apple.quarantine /Applications/HEPH-3D.app

On macOS 15 and later, right-click → Open no longer works — Apple removed it.

Windows 10 and 11, 64-bit. Python and the CAD kernel ship inside the installer — nothing else to install.

The installer is not code-signed yet, so SmartScreen will show “Windows protected your PC”. Click More info, then Run anyway. That warning is about the missing signature, not about the build.

Linux, x86-64. Ships as a tarball with its own Python and CAD kernel. Unpack it anywhere and run it:

tar xzf HEPH-3D-linux-x86_64.tar.gz ./HEPH-3D-linux-x86_64/heph

The window needs your system’s WebKit runtime. On Debian or Ubuntu: sudo apt install libwebkit2gtk-4.1-0

Every platform needs Claude Code installed and signed in; HEPH-3D runs your own copy under your own account.