Vinayak Sharma

It replaces the eyepiece and the spreadsheet. The app owns turret, load and dwell on a Vickers/Brinell tester, watches the microscope camera and detects the indentation diagonals itself (OpenCV) — with a manual override for low-contrast etches, because an ambiguous edge should never be a black box.

• Derives HV/HBW off the measured impression, with ASTM E140 conversion across to HRC
• Load calibration is a per-step table stored with the machine profile — a real load cell drifts off its nominal curve
• Trend, distribution and case-depth charts roll up across a session into a templated certificate

A metallurgist has to answer in numbers — how coarse the grain, how clean the steel, how deep the decarburized layer. Traditionally that means holding the eyepiece view against a printed comparison chart and writing down the closest match. Image Works measures it instead.

• 10 ASTM/ISO methods implemented down to the annex rules — E112 grain size, ISO 4967 inclusion rating with stringer merging, E1245 phase fraction, A247 nodularity, E1077 decarburization
• Pipelines are pure Dart with no widget imports, so the science is unit-testable on its own
• Every result ships with the overlay that produced it — the operator can see exactly what was counted, and disagree

The product most benches actually need: they already know what they are looking at, what they need is a defensible dimension and a document. Same codebase as Image Works, shipped as the measurement-only SKU.

• 20 measurement modes on one canvas — distances, parallel spacing, angles, circles, arcs, freehand, annotation — each labelled on the image and carried into the report
• Per-objective µm/pixel calibration profiles, so nothing is ever reported in pixels
• Panorama stitching and focus stacking run as queued external processes, so a long stitch never freezes acquisition

The same tester on embedded hardware, with no PC beside it: a Raspberry Pi touch panel booting straight into a Wayland kiosk.

• GPIO over dart_periphery for turret, load and dwell control
• A supervised firmware bridge that self-restarts, so a fault never strands the operator mid-test
• Shares the calibration model, report format and OTA channel with the desktop products

Employees, instructions, qualifications, medical records, projects, tasks, inventory, work equipment, inspection reports, incident analysis, e-learning and a document vault — one system where the job is usually a folder of spreadsheets.

• The spine is the qualification lifecycle — active, expiring, expired — and that state generates the task queue, rather than somebody remembering
• Templated inspections capture defects, photo evidence and an on-device signature, then export to PDF
• GraphQL subscriptions over WebSockets keep every open dashboard live

One schema behind all of it — employees, departments, work equipment, qualifications, instructions, inspection reports, incidents, courses, vault items and places — so a worker is one identity across every client in the platform.

• GraphQL over Prisma and MongoDB, multi-tenant with role- and permission-based access control
• Subscriptions for the events that have to arrive rather than be polled for: an inspection filed, an incident reported, a task assigned
• Docker and Kubernetes with CI/CD pipelines for highly available deployment

The phone client for people on a site rather than at a desk: inspections with their templates, reports and defect closeout, the work-equipment and maintenance register, the document vault, incidents, projects and employee records.

• Drafts are held on device and sync when signal returns — a scaffold inspection in a basement is exactly where the connection is not
• On-device SQLite store synced per-tenant, per-user; uploaded drafts are validated for integrity by the backend before merging
• QR-scan-based navigation straight to an asset or an inspection

Not a catalogue somebody browses — an assignment raised by a gap in the qualification register. A course mixes video, narration, PDF handouts and images in one player, then a timed test with a pass mark.

• Passing issues a certificate that writes back to the qualification that generated it, so the compliance gap closes without anyone re-keying anything
• Renders five content types — image, audio, video, PDF, webview — in one course flow
• Token sign-in links, because asking a site crew to remember a password is how training does not get done

A subcontractor walks up to an unattended Surface tablet, picks one of 26 languages, types their name and company, watches the site induction and takes the test. No account, no login — the terminal opens an anonymous session that expires in an hour.

• Results are signed so the server can prove which terminal issued them
• The induction video has a countdown and no scrub bar, because an induction is not something you skip
• Branding, greeting, languages and video all come from the module record — one binary serves every customer, and the URL decides which
• OTA deployment covers 25+ devices in the field

One Node deployment serves every customer their own terminal URL, streams the induction video, and admits certificates only if they verify.

• Video goes out over range requests in 1 MB chunks from a local disk cache, invalidated by size against the origin — terminals sit on site links, and pulling a video per visitor is not viable
• Certificates arrive signed and are verified against a public key before anything is written, so a forged or replayed result fails there rather than in the database

One login per training module, then what the safety team wants to know about it: who finished, what they scored, which languages they chose, and where people fall out.

• Reads the certificate records the terminals write rather than a separate event stream — the record that proves the induction happened is the record the numbers come from, so there is nothing to reconcile

Deliberately narrow: the companies on the platform, the users inside them, and the roles those users hold. One deployment serving every customer their own branded instance.

• A tenant record carries what support actually needs — trade association and registration number, employee and record counts, join date — so an operator can settle an account query without opening the customer's own instance