Living trust document
Questions we should answer plainly.
This FAQ is designed to be audited and updated. Some answers describe current behavior; others describe a goal or an area still under construction.
Last reviewed: July 15, 2026. Technical claims are reviewed against the Switchboard, Momokji Core, Gateway, and access-policy source before publication.
Is Momokji a VPN?
Not exactly. Momokji is a local system and protected doorway for reaching services on machines you control. It may use a private mesh underneath, but the product story is about your systems and data—not selling a generic VPN tunnel.
Is Momokji Tailscale?
No. Tailscale is one of the technologies and reference points in this space. Momokji is SpicyRiceCakes' attempt to build a more opinionated experience around home systems, Passports, self-hosted apps, and AI entities.
Does the Switchboard pass through my data?
The intended model is that the Switchboard authenticates, authorizes, and introduces the right systems, then steps out of the data path. Direct connections are preferred. Depending on the current network path and policy, a connection may still use a capped relay, so we will not promise that every connection is always direct.
Are you passing or sniffing my data?
Momokji is designed so the service that helps introduce your systems does not need to inspect the contents of your private data. We will keep documenting the actual boundaries, limitations, and implementation evidence as the system changes.
Why charge for something that runs at home?
Running a service still has real costs: account administration, security work, support, documentation, and keeping the coordination layer available. The fee is for the service around the system, not a claim that we own the data living on your machines.
What are Passports?
Passports are a design direction for carrying the right identity and context into an approved experience. They can belong to humans or AI entities. Private memory is not meant to travel wholesale.
How this stays current
Each answer will eventually carry a review status, date, source references, and related product routes in the content model. When implementation changes, the answer gets reviewed—or retired—rather than silently rewritten.