So I was reading about this new update around ROFL (Runtime Offchain Logic) and thought it was pretty cool for anyone who’s into privacy preserving apps or just hates dealing with proxy/TLS setups.
Basically:
You can now automatically host your frontend + get HTTPS + domain setup through the framework itself no NGINX configs, no Certbot dance, no juggling of reverse proxies. Just declare your domain in your compose file and the system handles the rest.
What it does for you:
- Auto-assigns a public URL
- Lets you plug in your own custom domain
- Generates TLS certs inside a TEE
- Fully manages the proxying/routing layer
- Works with static frontends (React, Vue, Svelte, Next static export, etc.)
If you’ve ever deployed a full-stack app and thought
“Why am I spending more time on DNS + TLS than on my actual app?”
…this scratches that itch.
Why people might care:
- If you're experimenting with enclave-based apps or confidential compute, hosting the frontend inside the same trusted boundary is a nice plus.
- If you’re tired of maintaining NGINX + Let’s Encrypt setups for small projects, this is a super low-friction alternative.
- Great for hackathons, MVPs, or anything where you want to ship fast without babysitting infrastructure.
here’s the blog if you want to skim the details:
đź”— https://oasis.net/blog/rofl-proxy-frontend-hosting
Top comments (2)
This is actually a pretty nice quality-of-life update. Being able to host the frontend and get HTTPS inside the same TEE without touching NGINX or Certbot removes a ton of small but annoying setup work.
Just add my domain and deploy, that’s it.
For quick MVPs or anything running on confidential compute, this makes the whole flow a lot smoother.
Super clean update! ROFL handling frontend hosting & HTTPS for you is such a win. Drop in a domain, let the TEE do the certs, ship the app. Much less setup, way more building.