Introduction
biga broadcasts a folder as a live, read-only link. No accounts, and nothing for viewers to install.
biga streams the files you are working on to a browser tab. You run one command in a project, share the link it prints, and anyone who opens it follows your saves as they happen: a file tree, syntax highlighting, and a timeline they can step back through.
A screen share sends pixels. biga sends the files themselves, so viewers can select, search and scroll at their own pace, and nothing is transmitted while you are not saving.
How it fits together
Architecture
The whole system in diagrams: what happens between a save and a viewer's screen.
The CLI
A single Go binary, biga. It watches a folder, hashes what changed and
uploads checkpoints.
The server
A Next.js app on Postgres that stores sessions and fans checkpoints out to viewers over server-sent events.
The viewer
The page a link opens. Read-only, with quick open, follow mode and a checkpoint timeline.
Where to start
Install the CLI, or follow the quickstart to go from nothing to a shared link in two commands.
Read what gets shared before you broadcast a project that holds secrets. Credentials are excluded by default, but it is worth knowing exactly how.
Running a server of your own? See self-hosting.