Capabilities

Many Ninja is being positioned from real repo evidence, not generic service copy.

Strong Capability Areas

• Custom web platforms
• Admin and operations systems
• Realtime and streaming systems
• Orchestration and runtime control
• Content ingestion and scanning pipelines
• User accounts and access control
• API, RPC, and control planes
• Browser-based interactive delivery
• Backend application architecture
• Go backend and runtime development
• Modular application architecture

Emerging Capability Areas

• Media-heavy systems
• Internal workflow software
• Interactive and game-adjacent systems
• Productized platform thinking
• Automation and background processing

What That Means In Practice

The current proof points show Many Ninja working on systems that sit between:

• operators and end users
• browser clients and backend runtimes
• live media streams and control channels
• content libraries and launchable experiences
• configuration, orchestration, and delivery

Current Repo Signals

The strongest documented repo signals right now come from:

• rs-kishi as a Rust-based platform for ROM, emulator, gateway, and portal management
• kishi as a Go-based runtime/server for Emu-Gate with modular application structure
• Emugate as the browser-facing experience layer across that product direction

Why This Matters For The Site

This capability map will drive:

• service pages
• proof sections
• diagrams
• comparison charts
• future case-study style work pages