Work

Four things built between 2025 and 2026. Two for clients, two because the problem wouldn't leave us alone. Every one still runs.

Four entriesTwo yearsNine stacksNothing ships unless we'd use it ourselvesScroll

012026Client workbettercallprakyat.com

Prakyat

The situation

A practising advocate across six jurisdictions, and no way for a first-time client to judge him before walking into a consultation. The profession forbids advertising, so the usual moves were off the table.

What we built

A practice site that opens with one unbroken descent — orbit, to Bengaluru, to the High Court, to his chamber — then gets out of the way. Long-form articles, plain language, and a consult form that reaches him directly. Nothing is stored, so nothing can leak.

React 19TypeScriptVite 6Tailwind v4GSAPResendVercel

Visit the site →

Plate 01

Practice site

Live

022026Internal toolDevSecOps

Attack Path

The situation

A scanner returns a list of vulnerabilities ranked by severity. It won't tell you which two medium findings become a breach when an attacker chains them.

What we built

Live CVE data from the NVD, modelled as a graph of hosts, services and vulnerabilities. Choose an entry point and an asset, and it traces every route between them — scored by how practical each hop actually is.

ReactReact FlowExpressSQLiteNVD API

The Attack Path Explorer interface: a dark threat-analysis workspace showing a node graph of CVEs chained from an internet entry point through web and app servers to sensitive records.

Plate 02

Graph analysis

Internal

032026Personal projectOpen source

Curiosity Engine

The situation

Every public data source tells you something. None of them tell you where the world's attention is concentrated right now, or what is rising underneath it.

What we built

A containerised Go service pulling several sources on a schedule, scoring them into one index, served behind a globe that blooms where the pressure is.

GoDockerPostgresThree.js

The Curiosity Engine interface: a dark globe visualisation with regions blooming where the attention index is highest, beside a ranked readout of rising signals.

Plate 03

Data pipeline

Running

042025Client workNo public interface

Test Ride

The situation

A dealership hands a motorcycle to someone they met ten minutes ago. Rider details go onto paper, and the team finds out how it went when the bike comes back.

What we built

An internal flow that verifies the rider by OTP before the keys move, records the handover, and returns a complete report to the team on return. It exists so staff always know who has what.

GoOTP verificationReporting

Plate 04

Flow diagram

Internal

Let's buildsomething good.

tycherra@gmail.comResponse within one working dayCode — github.com/Tycherra