What's new
What changed in Joring, newest first, written for the people who use it and the people who run it.
Changes to Joring that you can see, posted after each release. Security and reliability improvements that affect how you use Joring are listed here too. Internal changes are not.
5 October 2026
Managed deployment
- Enterprise teams can roll Joring out through their MDM. Download the install files under Settings → Deployment, push them, and each machine registers with your team and signs in through your identity provider with nobody clicking anything. Jamf Pro, Kandji, Intune, Mosyle, Addigy, Fleet, Workspace ONE, JumpCloud and Group Policy are covered. Read the guide.
- The browser extension and the desktop agent are separate streams: push either one alone, or both.
- Installs that people set up themselves appear under Devices as not managed, so you can see which machines are outside the rollout.
- The install files page is one numbered column: what to download and where to push it, in order.
Security
- Every Joring site and the API send strict security headers and a content security policy, and sit behind a web application firewall.
- Database backups are kept for 35 days and copied to a second region.
- Administrator access to the production database runs only over a private network. The database has no public path.
25 September 2026
Administration
- The new Overview page summarises adoption, impact and risk for the whole team in one place, and you can ask it questions about what it shows.
- The policy builder is a paged editor: rules read as a document, a policy can apply to groups or to applications, drafts are kept until you publish, and use of an application can be a trigger.
- Trails have a one-section editor with a publish review step. A published trail keeps its snapshot, so edits do not change what people see until you publish again.
- Invite up to fifty people at once from the Members page.
- Applications show which model answered a request, not only which one was asked for.
- Admins can run diagnostics on a device from Settings → Diagnostics when capture is not working.
Desktop agent 0.1.36 and 0.1.37
- Capture on a Mac recovers on its own after the machine sleeps and wakes.
- Conversations on claude.ai are captured again after a change to how the site talks to its servers.
- The certificate Joring installs is named "Joring CA" and stays in place when capture is stopped, so other applications are not interrupted.
- Windows: stopping capture pauses it cleanly, the capture service stops with the app, and an upgrade keeps your profile and asks for one elevation.