Sloth-ninja gets JessicaOSS ready for a real pilot

JessicaOSS now has the hosting groundwork to move from local setup toward a live, dependable legal-AI service.

infrastructuresecurity

Sloth-ninja has chosen Fly.io, a cloud hosting platform, for the backend and Cloudflare Workers for the frontend. The setup keeps the service in London, adds basic health monitoring, and keeps a small instance running so streamed chat answers are less likely to cut off midway.

Backend hosting is configured with the browser connection locked to the intended public site.
Frontend hosting is prepared to serve the application and collect operational signals once deployed.
Production guidance now calls for fresh secrets to protect signed downloads and encrypted user API keys.

The final live deployment still needs the relevant provider accounts, and the custom web address remains a decision for later.

So what Firms and legal-product teams assessing JessicaOSS can now see a credible path from a codebase to a continuously available pilot, with sensible attention to location, reliability, and basic security.

View this fork on GitHub →

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

Commits in this thread

3 commits from Sloth-ninja/JessicaOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`f84e7c35`	Add deployment config: backend fly.toml + frontend wrangler.jsonc	sloth-ninja	2026-07-14	↗ GitHub
commit body Owner decided Fly.io (14/07/2026). Backend: app jessicaoss-api in lhr, one warm shared-cpu-1x/1GB machine, /health checks, TRUST_PROXY_HOPS=1, CORS pinned to the production frontend origin. Frontend: Worker jessicaoss via @opennextjs/cloudflare with nodejs_compat and the .open-next assets binding; custom-domain route left commented pending the DNS decision. DEPLOYMENT.md §1/§8 updated to record both. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KsUrp6sw58RCSeqJtx5RH6
`e5fa220b`	CI: make frontend lint non-blocking (inherited upstream debt)	sloth-ninja	2026-07-14	↗ GitHub
commit body First real CI run showed npm run lint has never been green on the upstream codebase; hard rule 8 forbids wholesale style fixes there. Keep the step and its log for review visibility, but do not gate. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KsUrp6sw58RCSeqJtx5RH6
`e96c1047`	Pin canonical frontend origin to apex jessicaoss.com	sloth-ninja	2026-07-19	↗ GitHub
commit body Owner decision 19 July: apex is canonical, www 301-redirects to it, api.jessicaoss.com for the backend. FRONTEND_URL/CORS is single-origin, so the redirect (not a second serving hostname) is load-bearing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

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-1182.md from inside the repo you want the changes in.

⬇ Download capture-thread-1182.md