<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xovris changelog</title><link>https://xovris.ai/changelog/</link><atom:link href="https://xovris.ai/changelog/rss.xml" rel="self" type="application/rss+xml"/><description>Every change to Xovris, newest first.</description><language>en-gb</language><item><title>A failing request is compared with the ones that worked</title><link>https://xovris.ai/changelog/#errors-compared</link><guid isPermaLink="false">xovris-changelog-errors-compared</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Errors</category><category>AI change</category><category>Built, not yet released</category><description>When requests start failing, Xovris sets them beside the ones that succeeded and names the release and the repository the difference points to, so you start from the change that matters.</description></item><item><title>Every incident is investigated before you are asked anything</title><link>https://xovris.ai/changelog/#investigation</link><guid isPermaLink="false">xovris-changelog-investigation</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Investigation</category><category>AI change</category><category>Built, not yet released</category><description>When something breaks, Xovris works out what happened from your own records and the providers you depend on, and shows you the cause in plain words, with the records that prove it.</description></item><item><title>Repairs run step by step, and anything that does not hold is put back</title><link>https://xovris.ai/changelog/#repair-recovery</link><guid isPermaLink="false">xovris-changelog-repair-recovery</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Repair</category><category>AI change</category><category>Built, not yet released</category><description>A fix runs only within what you allowed, each step recorded; if it does not pass its re-check, the change is put back exactly as it was and the next approach starts – the incident stays open and visibly progressing until a fix is proven.</description></item><item><title>Tested before, tested after, checked by a separate verifier</title><link>https://xovris.ai/changelog/#resolution-guarantee</link><guid isPermaLink="false">xovris-changelog-resolution-guarantee</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Repair</category><category>AI change</category><category>Built, not yet released</category><description>Your own failing outcome is reproduced before anything changes, re-run after the fix with the checks around it, confirmed by a verifier separate from the fixer, and re-checked again later; a fix that does not pass is put back and the next approach starts, and you pay nothing for it until the after-test passes.</description></item><item><title>Every log, check and change in one place, in order, with secrets masked</title><link>https://xovris.ai/changelog/#logs-whole-story</link><guid isPermaLink="false">xovris-changelog-logs-whole-story</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Monitoring</category><category>Built, not yet released</category><description>Logs from your apps, the result of every check and every change Xovris makes land in one searchable place, kept in the order they really happened across machines, with passwords and keys masked before anything is stored – and every kind of line counted, so a new one stands out.</description></item><item><title>Connect by address alone, by app install or from your coding agent</title><link>https://xovris.ai/changelog/#connect-any-way</link><guid isPermaLink="false">xovris-changelog-connect-any-way</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Setup</category><category>Built, not yet released</category><description>Start with nothing but your website address, install the app on your platform, or let your coding agent set Xovris up – each connection is read back before it counts, and a connection that stops answering says so instead of staying green.</description></item><item><title>Uptime, APIs, journeys and scheduled jobs watched from outside</title><link>https://xovris.ai/changelog/#uptime-journeys</link><guid isPermaLink="false">xovris-changelog-uptime-journeys</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Monitoring</category><category>Built, not yet released</category><description>Pages, APIs, sign-in journeys and cron jobs are checked from Xovris’s probes on a schedule; a job that stops checking in is noticed by the silence, and every result is kept with where and when it was measured.</description></item><item><title>Domains, DNS and registration watched – and every change explained</title><link>https://xovris.ai/changelog/#domains-watched</link><guid isPermaLink="false">xovris-changelog-domains-watched</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Monitoring</category><category>Built, not yet released</category><description>Xovris reads each domain’s registration from its registry – expiry, renewal, transfer lock and registrar – and its DNS, and tells you in plain words when anything changes or is about to lapse.</description></item><item><title>Alerts that say what happened, why, and what is already being done</title><link>https://xovris.ai/changelog/#alerts-read-back</link><guid isPermaLink="false">xovris-changelog-alerts-read-back</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Alerts</category><category>Built, not yet released</category><description>Every alert carries the exact error, what it means, the cause once found and what Xovris is doing about it; a test alert shows each provider’s own acceptance, built-in email is one press, and a failed channel falls back to email and says so.</description></item><item><title>API tokens that always expire, with their life shown</title><link>https://xovris.ai/changelog/#api-tokens</link><guid isPermaLink="false">xovris-changelog-api-tokens</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Plans</category><category>Built, not yet released</category><description>Named tokens, read-only or read and write, lasting 1 to 365 days with their remaining life as a meter; a token that never expires is not issued.</description></item><item><title>Every incident has a live tracker, like a parcel delivery</title><link>https://xovris.ai/changelog/#fix-tracker</link><guid isPermaLink="false">xovris-changelog-fix-tracker</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Repair</category><category>Built, not yet released</category><description>Detected, cause found, fix ready, approved, applied, verified – each step appears when its record exists, with its time, so you always know where a problem stands.</description></item><item><title>A Fix Report in plain words for every fix</title><link>https://xovris.ai/changelog/#fix-report</link><guid isPermaLink="false">xovris-changelog-fix-report</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Repair</category><category>Built, not yet released</category><description>What was wrong, how it was found, what changed and the before and after side by side – plain words first, the technical line under each, built only from the incident’s own records.</description></item><item><title>About 1,470 services from open catalogues, each licence checked</title><link>https://xovris.ai/changelog/#adopted-catalogue</link><guid isPermaLink="false">xovris-changelog-adopted-catalogue</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate><category>Integrations</category><category>Built, not yet released</category><description>The services Xovris connects to come from permissive open catalogues, each install-tested and carrying its licence read from its source; the build refuses one whose licence does not allow it.</description></item><item><title>Investigations read the providers your site depends on</title><link>https://xovris.ai/changelog/#public-record</link><guid isPermaLink="false">xovris-changelog-public-record</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Investigation</category><category>AI change</category><category>Built, not yet released</category><description>When your site fails, Xovris now checks the public status pages, advisories, release notes and issue trackers of the providers in front of it, and cites what it found with the date it was published. An outage at your provider is named as the cause, and your own settings are kept exactly as they are.</description></item><item><title>A fix is proved on the request that failed – and on the pages around it</title><link>https://xovris.ai/changelog/#fix-proved-adjacent</link><guid isPermaLink="false">xovris-changelog-fix-proved-adjacent</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Repair</category><category>AI change</category><category>Built, not yet released</category><description>After you change something to fix an error, Xovris re-runs the exact request that failed and each workflow next to it, and keeps watching through a window before it calls the issue fixed. A fix that breaks something nearby is caught before it is called done.</description></item><item><title>The free website check shows what the outside world sees</title><link>https://xovris.ai/changelog/#website-check</link><guid isPermaLink="false">xovris-changelog-website-check</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Monitoring</category><category>Built, not yet released</category><description>Type an address on xovris.ai and Xovris checks it from its own probes outside your network – the certificate, the page and DNS – beside what your browser can see, and says plainly what it could not confirm.</description></item><item><title>Set up from your coding agent</title><link>https://xovris.ai/changelog/#agent-setup</link><guid isPermaLink="false">xovris-changelog-agent-setup</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Setup</category><category>Built, not yet released</category><description>Claude Code, Cursor and other agents that speak MCP can install Xovris in your project and confirm it is working: setup only counts once a real event from your app is stored.</description></item><item><title>Connect Vercel: every environment gets its own key, read back</title><link>https://xovris.ai/changelog/#vercel</link><guid isPermaLink="false">xovris-changelog-vercel</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Integrations</category><category>Built, not yet released</category><description>Connecting Vercel writes a separate key into production, preview and development, reads each one back, and removes them all when you disconnect.</description></item><item><title>Slack alerts, and a disconnect that proves the access is gone</title><link>https://xovris.ai/changelog/#slack</link><guid isPermaLink="false">xovris-changelog-slack</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Alerts</category><category>Built, not yet released</category><description>Alerts post to the Slack channel you choose. When you remove Slack, Xovris revokes its access and checks with Slack that the access really is gone before saying so.</description></item><item><title>Your existing browser tests become monitors</title><link>https://xovris.ai/changelog/#checks-as-code</link><guid isPermaLink="false">xovris-changelog-checks-as-code</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Monitoring</category><category>Built, not yet released</category><description>An existing Playwright test runs unchanged as a check from Xovris’s probes, so the journey you already test is the journey Xovris watches.</description></item><item><title>Know when a certificate is issued for your domain</title><link>https://xovris.ai/changelog/#ct-watch</link><guid isPermaLink="false">xovris-changelog-ct-watch</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Monitoring</category><category>Built, not yet released</category><description>Xovris watches the public Certificate Transparency logs and tells you when a certificate is issued for one of your domains – including one you did not ask for.</description></item><item><title>The same error stays one issue across releases</title><link>https://xovris.ai/changelog/#grouping</link><guid isPermaLink="false">xovris-changelog-grouping</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Errors</category><category>Built, not yet released</category><description>Errors from Next.js, Node.js and React apps are grouped the same way when a release changes file names or chunk numbers, so one fault is one issue, not a new one every deploy.</description></item><item><title>A flood of one error never hides the first of another</title><link>https://xovris.ai/changelog/#first-occurrence</link><guid isPermaLink="false">xovris-changelog-first-occurrence</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Errors</category><category>Built, not yet released</category><description>When one fault floods your app, Xovris drops only the repeats: the first occurrence of every other error still arrives in full.</description></item><item><title>Free has no AI anywhere – and every release proves it</title><link>https://xovris.ai/changelog/#free-no-ai</link><guid isPermaLink="false">xovris-changelog-free-no-ai</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Plans</category><category>Built, not yet released</category><description>Checks, alerts and diagnostics on the Free plan never call an AI model, and each release is checked to make sure none does.</description></item><item><title>Jump anywhere with Ctrl+K or Cmd+K</title><link>https://xovris.ai/changelog/#palette</link><guid isPermaLink="false">xovris-changelog-palette</guid><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>Command centre</category><category>Built, not yet released</category><description>The command centre opens a search-and-jump palette from anywhere, so every page and action is a few keystrokes away.</description></item></channel></rss>
