Gluefi · 2025–2026 · Creative technologist
Execution infrastructure for regulated tokenized finance
Institutional execution and governance infrastructure for regulated tokenized finance in Japan — built to be trusted before it is admired.
Context
Gluefi builds institutional execution and governance infrastructure for regulated tokenized finance — the systems through which regulated institutions in Japan can act on tokenized assets with the controls their regulators, and their own risk desks, require.
Mandate
The original brief was specific: design a modular, reusable front-end system for building branded products quicklythe brief said “front-end system.” the job had other plans. — JJ — one architecture underneath, many products on top, nothing rebuilt from scratch per brand. In regulated finance, speed only counts if the rigor travels with it, so the system had to make the two inseparable.
What he built
This is infrastructure whose first duty is to be trustworthy, so the craft shows up as restraint.discretion as a design material. The engagement, meanwhile, kept growing — three phases, each one deeper in the stack.
- A modular front-end system for branded products. A reusable component architecture and theming layer for assembling branded products quickly on shared infrastructure — onboarding and verification surfaces, role-based admin and review interfaces, English and Japanese throughout. Its public face is the Digital Kiribako™ experience, which shipped on it.
- The move down the stack. With the front-end system standing, the work extended into the backend: passkey-first authentication, verification workflows with real recovery paths, and money movement built to be exact — idempotent transfers, two-phase deduplication, every operation reporting its own outcome.
- Several months running the whole thing. When Gluefi’s backend developer had to step away, I became the main person keeping the engineering movingfor a stretch I was the roadmap, the release process, and the fire department. — JJ — new features still shipping while production stayed steady: a memory leak chased down in the database layer, deployment pipelines retuned, releases carried from dev to prod, in a domain where operations must never half-happen.some of the best work I’ve done is work I can’t show you. that sentence is doing a lot of lifting on this page, and it’s true. — JJ
Outcomes and counterparties from this engagement aren't published here. That's deliberate.