01Selected work

Real products, shipped to production.

Every build below ran in production. Client names are kept private; the engineering speaks for itself.

3D Product Configurator

A real-time “design your own” experience for a fine-jewelry brand. Shoppers combine settings and stones and see the finished piece render live in 3D before adding to cart.

Interactive WebGL product viewer
Guided multi-step configurator
Headless commerce back end

Sector: E-commerce · Fine jewelry
Scope: Configurator, pricing engine, checkout
Stack: Three.js, WebGL, React, Next.js
Status: In production

Next.js
React
Three.js / WebGL
Headless Commerce
TypeScript

Try the live configurator →

Real-time 3D

built for the shopper's browser, priced as the piece comes together

Real-Estate Platform

A multi-app platform for property listings and housing programs, with a content CMS for non-technical staff and a GraphQL API stitching several services together.

Public site + admin dashboard
Editor-friendly headless CMS
GraphQL API over multiple services

Sector: Real-estate technology
Scope: Public site, admin, CMS, API
Stack: Next.js, NestJS, GraphQL, Payload CMS, PostgreSQL, AWS
Status: In production

Next.js
NestJS
GraphQL
Payload CMS
PostgreSQL
AWS

6 apps

apps unified on one platform, with a CMS non-technical staff actually use

Jewelry Service & Repair System

A luxury jewelry group tracked repairs on paper across two brands and dozens of stores. Built the system that takes a piece in, moves it through the workshop and outside vendors, and bills for it, with each brand keeping its own store numbering.

Multi-step intake, workshop and return workflow
Per-brand store numbering across two networks
Outside-vendor routing, invoicing and time sheets

Sector: Luxury retail · Jewelry service
Scope: Repair intake, workflow, vendors, invoicing
Stack: PHP, MySQL, jQuery
Status: Delivered

PHP
MySQL
Workflow
Reporting

2 brands

on one repair workflow, each keeping its own store numbering

Legacy Platform Migration

A legacy commerce platform replaced service by service, with sync workers holding the old and new sides consistent for as long as both were live. No freeze, no cutover weekend.

Order status, shipments, pickups and cancellations synced both ways
Idempotent event handling, so a replay could not double-apply
Each service cut over on its own schedule

Sector: Fintech · Platform modernization
Scope: Strangler-fig migration, data sync
Stack: Node.js, RabbitMQ, MySQL
Status: Delivered

Node.js
RabbitMQ
MySQL
Magento
Event-driven

2 systems

kept consistent while one replaced the other, live

Have something like this in mind?

Tell us the workflow or product you want built. You'll hear back from the engineer who'd build it.

Start a project →