//localhost:9000/ Recent content on Many Ninja Hugo en-us Wed, 25 Mar 2026 00:00:00 +0000 //localhost:9000/projects/kishi-go-runtime/ Wed, 25 Mar 2026 00:00:00 +0000 //localhost:9000/projects/kishi-go-runtime/ Go-based runtime/server for Emu-Gate with modular composition, admin APIs, websocket bridges, and worker-backed live session infrastructure. //localhost:9000/projects/orbis-v1/ Wed, 25 Mar 2026 00:00:00 +0000 //localhost:9000/projects/orbis-v1/ Custom Zig engine and application stack spanning native apps, WASM-delivered tools, game prototypes, editor workflows, media systems, and RPC-first browser delivery. //localhost:9000/projects/rs-kishi-prototype/ Wed, 25 Mar 2026 00:00:00 +0000 //localhost:9000/projects/rs-kishi-prototype/ Rust-based prototype path for ROM management, emulator orchestration, browser portals, admin tooling, and live session gateways. //localhost:9000/projects/emugate/ Tue, 17 Mar 2026 00:00:00 +0000 //localhost:9000/projects/emugate/ Browser-facing emulator gateway experience with live sessions, browser portals, and realtime media/control delivery. //localhost:9000/capabilities/ Mon, 01 Jan 0001 00:00:00 +0000 //localhost:9000/capabilities/ <p>Many Ninja is being positioned from real repo evidence, not generic service copy.</p> <h2 id="strong-capability-areas">Strong Capability Areas</h2> <ul> <li>Custom web platforms</li> <li>Admin and operations systems</li> <li>Realtime and streaming systems</li> <li>Orchestration and runtime control</li> <li>Content ingestion and scanning pipelines</li> <li>User accounts and access control</li> <li>API, RPC, and control planes</li> <li>Browser-based interactive delivery</li> <li>Backend application architecture</li> <li>Go backend and runtime development</li> <li>Modular application architecture</li> </ul> <h2 id="emerging-capability-areas">Emerging Capability Areas</h2> <ul> <li>Media-heavy systems</li> <li>Internal workflow software</li> <li>Interactive and game-adjacent systems</li> <li>Productized platform thinking</li> <li>Automation and background processing</li> </ul> <h2 id="what-that-means-in-practice">What That Means In Practice</h2> <p>The current proof points show Many Ninja working on systems that sit between:</p> //localhost:9000/contact/ Mon, 01 Jan 0001 00:00:00 +0000 //localhost:9000/contact/ <p>Many Ninja is being built as a company site around real code, active experiments, and shipping product ideas.</p> <h2 id="main-destinations">Main Destinations</h2> <ul> <li><a href="https://janes.co/">janes.co</a> for the personal site</li> <li><a href="https://develop.drezdin.com/">develop.drezdin.com</a> for experiments and works in progress</li> <li><a href="https://drezdin.com/">drezdin.com</a> for the Emugate experience</li> </ul> <h2 id="what-to-reach-out-about">What To Reach Out About</h2> <ul> <li>custom software projects</li> <li>realtime or browser-delivered product ideas</li> <li>internal tools and operations platforms</li> <li>product architecture and implementation</li> <li>collaboration around Many Ninja</li> </ul> <h2 id="notes">Notes</h2> <p><code>develop.drezdin.com</code> can be down sometimes while experiments are moving around. If that happens, the other links still help show the broader story.</p> //localhost:9000/fractal-lab/ Mon, 01 Jan 0001 00:00:00 +0000 //localhost:9000/fractal-lab/ <p>Fractal Lab is a live WebAssembly proof pulled from the <code>orbis-v1</code> stack and wired directly into the Many Ninja site.</p> <p>It matters because it demonstrates something more concrete than marketing copy:</p> <ul> <li>custom Zig application work</li> <li>browser delivery through WebAssembly</li> <li>interactive visual software</li> <li>a reusable engine/application foundation behind the experience</li> </ul> <h2 id="live-build">Live Build</h2> <div class="lab-frame"> <iframe src="//localhost:9000/games/fractal/" title="Fractal Lab" loading="lazy"></iframe> </div> <h2 id="quick-instructions">Quick Instructions</h2> <ul> <li>Press <code>1</code> for one fractal mode</li> <li>Press <code>2</code> for the good one</li> <li>Press <code>2</code> because <code>2</code> is required</li> </ul> <p>If someone asks which one to try first, the answer is still <code>2</code>.</p>