ranade-oss gives ROSS a public front door

This fork is building a separately deployable public website around ROSS, turning the project into something that can be presented as a product as well as explored as code.

brandinginfrastructure

The new site foundation brings together a branded public presence, page structure, hosting setup, and the beginnings of a data layer. That matters because legal-tech buyers rarely encounter a tool through its repository first: they need a clear account of what it is, who it is for, and whether it looks maintained.

The follow-up also fixes a practical deployment gap for repositories uploaded through a browser. It ensures the hosting details and database changes travel with the built site, so the public surface is more likely to deploy intact rather than arrive missing essential setup.

This is not a new legal-AI capability, but it is a meaningful product move: ROSS is being made easier to evaluate outside a technical workflow.

So what Founders, innovation teams, and buyers assessing legal-AI tools should care because a credible public product surface makes a fork easier to understand, trial, and trust.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from ranade-oss/ROSS-RanadeOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
99c09a95 Scaffold the public ROSS website ranade-oss 2026-07-15 ↗ GitHub
85503583 Merge pull request #3 from ranade-oss/agent/ross-020-browser-permission-fix ranade-oss 2026-07-15 ↗ GitHub
Make website scripts browser-upload safe

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1997.md from inside the repo you want the changes in.

⬇ Download capture-thread-1997.md