⠀⠀⠀⠀⢀⡠⣾⣳⡀⠀⠀⠀⠀⠀
⠀⠀⡀⠀⠚⢿⣿⣿⡿⠙⠀⠀⠀⠀
⠀⣘⣿⣇⡀⢘⣿⣿⠀⢀⣠⣶⡀⠀
⠺⣿⣷⣝⣾⣿⣿⣿⣿⣿⣹⣷⣿⠆
⠀⠘⠟⠁⠀⠀⣿⣟⠀⠀⠙⠿⠁⠀
⠀⠀⠀⠀⠀⠀⣿⣿⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⢠⣿⣿⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⢸⣿⡿⡄⠀⠀⠀⠀⠀
⠀⠀⠀⠠⣖⣿⣿⣻⡷⡄⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠈⢻⡟⠁⠀⠀⠀⠀⠀

Founder & Engineer @ Advance Labs Inc., a Canadian software studio. My brother @SpookYlonMuh heads game development.

We build shit until it works.

Claim yourname.runs-on.dev in about twenty seconds with a GitHub account. It's live immediately over HTTPS, and you point it at your own hosting with a pull request.

A real TLD means an ICANN application, and the 2026 round wanted $227,000 per application before you've run anything. This gets the same custom-ending feel for about $10 a year. The public repo is the database, so every claim is a commit anyone can read, and one wildcard DNS record covers every name at once. Claiming is a git write, not a DNS write.

572 names are claimed so far, by 572 distinct GitHub accounts, because the limit is one name per account and the registry enforces it on the way in.

AGPL-3.0 · 313 tests · one name per account · not a TLD, and I don't pretend it is

A TypeScript monorepo I built that scores a site the way an AI assistant reads it: crawl → parse → score, plus MCP servers and content agents.

Five of the tools run free in the browser at advancelabs.dev/tools with no sign-up: the technical SEO and AEO audit, an E-E-A-T scanner, an llms.txt generator, a GA4 and GSC chat, and a 3D backlink graph.

17 packages · 988 passing tests · a 54-rule scoring engine · Apache-2.0

Scores are cross-checked against live answers from ChatGPT, Google AI Overviews, Perplexity, and Claude, so the number is a measurement you can re-run after fixes, not an opinion. It's also the engine behind the studio's AI-visibility audits.

The same engine on your toolbar. Open any page, click the icon, get a 0–100 AI-readiness score with a letter grade and a list of what to fix. Export it as a PDF.

It runs 40 of the 54 rules: the 29 technical-SEO and 11 AEO ones. The 14 E-E-A-T signals need a whole-site crawl, so they stay in the hosted audit rather than pretending to work from one tab.

Nothing leaves the browser. No account, no server, no analytics, no telemetry. The only requests it makes are to the audited site's own robots.txt, sitemap.xml and llms.txt, which is what the host permission is for.

Free · Apache-2.0 · 40 checks across 9 categories · client-side, so nothing to trust me about

Sim-first autonomy for a small multirotor I built. The stack is pure Python behind a VehicleBackend seam, so the same mission code runs against a kinematic sim, PX4 SITL, and a Pixhawk without changing the autonomy layer.

I built five environments from real OpenStreetMap data and put the simulator on the web, so you can fly it yourself. Every number below is one the simulator produced, so there's no marketing copy to drift out of sync.

275 tests · no runtime dependencies · verified against PX4 SITL · Apache-2.0

The airframe is a Holybro X500 V2 with a parametric OpenSCAD payload stack (Pi 5 tray, payload deck, battery tray, GNSS mast, nav-light pods), designed around a low-light STARVIS camera. Transport Canada RPAS rules shape the design more than any technical preference does: "autonomous" in Canadian airspace means pilot-supervised autonomy, with a human able to take control at all times.

A terminal-first agent IDE for running several coding agents in parallel. I run it every day, so the two things I sent upstream are the two that were costing me something.

#572 — switching panes. The "Open" launcher flashed where the terminal had been on the first visit to every pane, because the stage guard read layout hasn't loaded yet and layout doesn't exist as the same state. Then the terminal that arrived sat behind an activation mask held open by two fixed delays that were standing in for conditions nobody had written down. Replacing the delays with the conditions themselves, and letting the activation backstop repaint instead of destructively resetting when it has nothing to repair, took per-pane activation from 675 ms to 332 ms.

#573 — renaming panes. The IPC handler and the edit-state handlers already existed and were exported; no component ever rendered them. Adding the inline sidebar UI surfaced a pre-existing store bug: a main-repo session is stored twice, and updateSession returned early after updating the first copy, so the sidebar went stale on any session:updated for that pane, not just renames. Both fixed, with a Playwright test that I confirmed fails without the store fix.

852 lines across two pull requests · timings measured on the real Electron app, not a benchmark

An independent Canadian software studio, federally incorporated under the CBCA. We build and ship our own products, and take on fixed-scope client work.

Services

Products

Client work: Kuzyn Builds (London, ON custom home builder: site build + local AI-search setup) · Next Leaf Prints (Toronto printing & embroidery: storefront redesign). Case studies at advancelabs.dev/work.

Real, public, and honest about where it stands. Not what I'd lead with.