
npm i -g netget
Then run on your terminal:
netget
netget is a modern, lightweight reverse proxy and placement layer built on OpenResty. It turns any host into a clean, secure entry point for applications and Monads.
In the Neuroverse stack:
.me -> meaning / seed / semantic tree
cleaker -> mounts .me into a namespace
monad.ai -> invisible execution routes inside that namespace
netget -> physical placement + endpoint resolver
A namespace is not a port:
jabellae.cleaker.me/profile semantic path / meaning
jabellae.cleaker.me/photos/iphone semantic path / meaning
jabellae.cleaker.me/.mesh/monads internal Monad registry
jabellae.cleaker.me[monadlisa]/profile technical execution override
monadlisa@127.0.0.1:8161 Monad instance + endpoint
NetGet can resolve:
netget://iphone/monadlisa -> http://10.0.0.12:8161
netget://raspberry/worker-a -> http://192.168.1.44:42137
netget://vm-prod/api -> https://vm.example.com/_monads/api
Point your domain’s DNS (A or CNAME record) to your server’s public IP. Then use the NetGet main server to register where each domain should go:
NetGet takes care of the rest: routing, encryption, and SSL renewal.
For Monads, NetGet is the body-finder:
user intent: read jabellae.cleaker.me/photos/iphone
NRP: choose the best Monad route internally
NetGet: resolve that Monad route to a current endpoint
If an operator needs to debug a specific route, the NRP can still force it:
me://jabellae.cleaker.me[monadlisa]/photos/iphone
That selector changes execution only. It does not change the namespace or path meaning.
Simple. Secure. Yours.
made by neurons.me MIT License
