
KananOS / United Distribution
Multi-tenant B2B e-commerce wholesale platform
I make useful systems for the messy middle: where product decisions meet infrastructure, automation, and the ways people actually break things.
Some shipped. Some are still sharp on the workbench. Every project here exists because a real constraint made a better engineer of me.

Multi-tenant B2B e-commerce wholesale platform

Production website + commerce experience
Vertical AI revenue infrastructure
Search-heavy full-stack SaaS architecture
Bug bounty intelligence + attack surface management
Modular Python reconnaissance toolkit
Smart-contract security toolkit
Freelancer business automation toolkit
Provider routing + caching patterns

Editorial wildlife photography portfolio

A quiet instrument for the human psyche
Astro shell with React, Vue, Solid, Svelte, Next, and Nuxt surfaces
Matching backend contracts across three runtimes
Unreleased projects get a visible place without invented screenshots or premature claims. This is where testing access, notes, and release status can live when each beta is ready.
Next.js product surface under active development. This is a real local project and belongs in the testing queue.
Open repository ↗Go API and streaming telemetry component for testing real-time service boundaries.
Open repository ↗Local redesign project for iterating on the portfolio surface before release.
Open repository ↗A good interface is the visible edge of a much larger decision: data shape, failure mode, deployment model, and who has to live with it later.
Fast, responsive products built with modern React and Next.js architectures.
Typed APIs, middleware, workers, integrations, databases, and service architecture.
Workflow automation and AI-enabled systems designed around real business processes.
Application hardening, reconnaissance tooling, security research, and offensive-security engineering.
Cloud deployment, containers, DNS, CI/CD, edge infrastructure, and production operations.
Rebuilds that improve UX, architecture, maintainability, and technical credibility at once.
I look for the interesting failure before it becomes the expensive one. Security is a design constraint, an engineering discipline, and a habit of asking one more uncomfortable question.
Tools are instruments, not personality traits. The interesting part is knowing when to stop adding them.
Each tool has a boundary and a job. Islands stay small, services stay replaceable, and the public surface stays fast.
SEO, content, routing
APIs, workers, and integration boundaries
“Make it legible before you make it clever.”
— written in the margin, then tested in production
Tell me what you're trying to accomplish. We'll figure out the architecture from there.