← // BACK TO LIVE APPS
[ APP // FILES.FILEBROWSER ]
LIVE

FILESERVER

FileBrowser web UI sitting on top of my private SFTP server. Self-hosted, ZeroTier-fronted on the LAN side, Cloudflare Tunnel on the public side. The cloud drive that doesn't live in someone else's cloud.

FILEBROWSER SFTP SAMBA ZEROTIER CLOUDFLARE TUNNEL RPI 4 2TB · LUKS
↗ LAUNCH APP
// LIVE EMBED

Browse it from this page

The actual FileBrowser instance, embedded below. If the embed feels cramped on mobile, the launch button up top opens it full-screen in a new tab.

https://files.sujitverse.io
↗ OPEN

EMBEDDED OVER CLOUDFLARE TUNNEL · IF YOU SEE A 5XX, THE PI IS REBOOTING — TRY AGAIN IN A FEW MINUTES.

[ // ARCHITECTURE ]

HOW IT'S WIRED

FILES · DATA FLOW PUBLIC EDGE → CLOUDFLARE → PI → SFTP → DISK YOU (BROWSER) files.sujitverse.io HTTPS only CLOUDFLARE edge proxy DDoS · TLS CF TUNNEL outbound only no port forward PI · FILEBROWSER :80 internal user auth SFTP / DISK 2TB · LUKS noexec · nosuid NOT ONE OPEN INBOUND PORT ON THE HOME ROUTER CF tunnel terminates at cloudflared on the Pi · no NAT, no firewall holes
why filebrowser

I needed a frontend on top of the SFTP server I'd already built. FileBrowser is small, single Go binary, supports user auth, share links, and download tokens. It does what it says on the tin — no NextCloud sprawl, no plugin ecosystem to maintain.

[ // BUILD LOG ]

READ THE SFTP BUILD

9-min log on the SFTP layer underneath this UI — chrooted shares, ZeroTier mesh access, Samba bound to the mesh interface only, and why I never opened a port on the router.

READ THE BUILD LOG →