Overview
Labs were juggling slicers, spreadsheets, and ad-hoc machine logs. The product makes operational truth visible: what is printing, what failed, and what needs a human—without another exported CSV.
- Automated slice optimization with versioned job profiles
- Real-time printer telemetry with routed alerts
- Multi-user workspaces, roles, and audit-friendly history
Tech stack
From file to finished part—one queue.
Product strategy
We anchored the experience on three jobs-to-be-done: prep work quickly, keep the fleet honest, and explain failures in plain language. Every screen had to earn its place on a busy lab floor.
Design & systems
Dense telemetry stays legible with disciplined grids, inline sparklines, and progressive disclosure for gcode-level detail. Dark surfaces reduce glare beside machines; typography stays sharp for overnight shifts.
Impact
Fewer surprise failures by catching drift before scrap—not after.
Predictive hooks around temperature bands and layer anomalies gave teams an early nudge. The north star was calmer night shifts and less rework, not a louder wall of charts.
Single job timeline
Upload through QA with immutable history—handy when a client asks what changed between runs.
Fleet at a glance
Tiles for device health, resin or filament burn-down, and queue depth without jumping tabs.
Built for teams
Managers, operators, and partners share one language for priority, capacity, and blameless postmortems.
