Binary Division

The problem

Someone with a 3D model should be able to understand what making it will cost. A standard storefront does not know how to turn triangle data into volume, material use, or a manufacturing estimate.

Binary Division combines a manufacturing platform with a longer-term drone program. The manufacturing work gives me a place to develop parts, test designs, and learn what survives outside a CAD file.

What I built

I built the platform end to end: the storefront, a browser-based STL parser and mesh analyzer, the quote calculation, catalog import, cart and checkout, order tracking, and an administration interface.

The geometry engine reads the model to estimate volume, weight, and print time and checks watertightness. The pricing system combines material cost, machine time, setup, and quantity rules.

The engineering decisions

I separated instant quotes from estimates and jobs needing manual review. That distinction matters because an attractive price is not useful if the geometry cannot be printed as expected.

I also built a catalog-import pipeline that downloads and analyzes models before pricing them. Imported designs remain distinct from the parts I design myself, with licensing considered during import.

What exists today

The public manufacturing site exposes a catalog, a print-upload workflow, and custom-design services. My contribution is the software and the operating logic behind these workflows.

The drone program is at the concept and design stage. I keep that status separate from the manufacturing platform; a proposed aircraft is not a flight-tested aircraft.

Next iteration

I am developing my CAD, prototyping, and engineering practice alongside the platform. The most useful next evidence is a documented part across iterations: the first design, what failed, the revision, and the final test.

Follow the work.

Personal contributions are described by Foysal. Organization-wide results remain attributed to the relevant team or public record.