About Mochi

Actual product interface · Demo identifiers used

The challenge. Sharing a desktop inside VRChat can quickly become a maze of capture settings, streaming protocols and player configuration. MochiCast was built around a simpler idea: open the app, press Start, and stream.

The approach. A Windows desktop client handles capture and encoding, while self-hosted media infrastructure delivers the stream. The stack brings together Avalonia, FFmpeg, MediaMTX and Caddy, with secure RTMPS ingest and playback options including RTSP and HLS. Behind the simple interface is ongoing work on audio-process discovery, capture stability and stream recovery.

What we learned. Low latency alone isn't enough: the experience also depends on reliable audio, frame pacing and sensible defaults. Regional infrastructure and failover add resilience, but real-world failures still need investigation and iteration.

Outcome. MochiCast moved beyond a demo into a publicly available product with real users and paying customers. The ongoing priority remains the same: advanced engineering, minimal setup.

Actual product interface · Demo identifiers used

The challenge. Network tests can make a healthy connection look broken. Some providers filter or deprioritise ICMP, and a failed HTTPS probe does not automatically mean the user's internet connection is degraded.

The approach. Nami Network Diagnostics grew from a network analyser into a tool designed to separate gateway responsiveness, internet reachability and destination-specific issues. Its testing logic has been refined to reduce misleading loss alerts, expand test locations and show latency more clearly.

What we learned. Monitoring is only useful when its alerts reflect genuine user impact. A confident but incorrect diagnosis wastes more time than a carefully qualified result.

Outcome. A public-facing diagnostic tool focused on more meaningful network evidence, with testing and calibration continuing as the product evolves.

Actual product interface · Demo identifiers used

The challenge. A VPN should be easy to connect to without exposing users to the operational complexity behind it. Managing regions, account services, client releases and connectivity issues creates its own engineering work.

The approach. Shadowlink brings together a Windows client, WireGuard-based networking, region selection and self-hosted services. UK and German infrastructure serve different roles, while a release helper publishes versioned client packages and update information.

What we learned. A polished Connect button depends on dependable networking, careful release management and useful logs when a connection drops.

Outcome. An actively developed VPN product backed by infrastructure Mochi operates directly; reliability and connection diagnostics remain ongoing priorities.

Actual product interface · Demo identifiers used

The challenge. Publishing an application is one thing. Keeping its websites, streaming endpoints, APIs and downloads running is another — especially when services span multiple physical locations.

The approach. Mochi operates Linux infrastructure across a hosted German server and a UK node, using reverse proxies, service management, firewalls, monitoring and region-aware routing. Streaming can switch regions after a server failure, though existing sessions may need to reconnect.

What we learned. Resilience is not a marketing checkbox. It requires knowing which services can fail over, which still depend on one server, and how to detect and recover from incidents.

Outcome. Hands-on experience operating real production services, including the limitations and trade-offs that only appear after deployment.

Actual product interface · Demo identifiers used

The challenge. Traditional sync clients duplicate files and introduce storage overhead and conflict handling. Mochi Drive explores a different experience: cloud-first storage accessible directly from Windows Explorer.

The approach. The desktop client mounts a drive through WinFsp so users can browse remote files, open them on demand and upload by copying into the drive. Temporary caching supports access without requiring a full offline mirror.

What we learned. Integrating with the operating system makes small details — startup behaviour, mount paths, sign-in state and clean uninstallation — central to the product experience.

Outcome. A working desktop integration undergoing continued UI and usability refinement, rather than a finished enterprise storage offering.