A build-first portfolio.
QuasiPI Tech is a personal portfolio, not a company. There are no products for sale, no services and no clients here — just the projects I build: fleet software for mobile robots, simulation engines written from scratch, edge-AI hardware small enough to carry, and the printed parts that hold it all together. Every project here is labelled with how far along it is, and every figure beside it was measured on the named build, not estimated. See what is ready and what is not.
The layer around the machine
I do not build robots. I build what sits around them: the simulator that sizes a fleet before one is bought, the controller that dispatches the fleet you own, and the platform that keeps the safety rules honest once the machines are out of sight.
The same habits carry across fields. A strategy-game engine, a planet simulator and a warehouse simulator are all deterministic worlds that have to give the same answer twice — and a printed enclosure is the same kind of problem as a software module: a spec, a first attempt, a measurement, a correction.
Robotics & fleets
Simulation, dispatch and safety software for mobile robots. See the projects
Simulation & games
Deterministic engines and a custom renderer, with every asset authored in-house. Epoch Ascendant
Edge AI & embedded
Models and software that run on the machine in front of you, offline, in an enclosure designed around the job.
3D printing & parts
Engineering materials and carbon composites on a production-grade machine. 3D printing
Build it, break it, write it down
Start from the problem
Every build begins with something that does not exist yet, or exists badly. The technology is chosen after the problem, never before it.
Make it real early
A rough working version beats a polished plan. Parts get printed, code gets run, and the design is corrected against what actually happens rather than what was drawn.
Measure, do not estimate
If a number is quoted, it came from a run that can be repeated with the same seed. Thousands of automated tests exist so that a fix in one place cannot quietly break something in another.
Document the whole thing
Including the failures. The dead ends are usually the most useful part of a write-up, and the part nobody else publishes.
What I will not pretend
These are written into the code, not into a slide.
unknown != safeSpace a robot has not observed is treated as blocked, not as free floor.
no faked safetyWhere a certified component is required, the code says so instead of standing in for it.
the numbers are measuredEvery published figure comes from a run on my own build — including the runs that came out worse than I hoped.
assets are authoredModels, animations and audio are made here rather than bought from a marketplace.
A public record of the work
One place for everything I build: what it is, how it works, what it measured, and what broke on the way. Unfinished and failed projects stay on the list, because they are part of the record.
Nothing here is for sale. If something is useful to you, or you want to compare notes, write to me.