Command centre
One place for what it does.
Home, Inbox, Ask Xovris and Activity show what Xovris found, fixed and is waiting on – on the web and on your phone.
XovrisOn its own
- A lit square is a feature people use today
- Newest: Every control is easy to tap
Every feature in Command centre, strongest first.
What fixes and prevents a problem comes first. Type to find one, or open a plan to see only its own.
Nothing here matches those words yet. Xovris notes the words, with no address and no cookie, so what is missing gets written.Ask Xovris instead
Lit: live and workingOpen: Xovris is still working on it
Every control is easy to tap
Every standalone link and control in the command centre is a comfortable tap target at every width.
Everything Xovris did, hour by hour
The activity page opens on a strip of everything Xovris did by hour, and the same read repeated folds into one line that says how many came before.
Each page leads with what is open for it
A page for one kind of thing leads with what is open for that kind, so the command centre never says two different things.
The emergency stop comes first
The control page opens on the emergency stop, with everything Xovris may do by itself drawn from your real policy, kind by kind.
Dashboards open on your own live tiles
Each dashboard's first screen shows your own tiles, each a ring or a strip fed by live readings.
Ask Xovris starts from what needs you
Ask Xovris opens with a few starting points drawn from your own workspace - what needs you first, worst first.
How sure Xovris is, and what may be stale
Each fact shows how sure Xovris is of it, and whether it may be out of date, with why and since when.
Every fact with where it came from
Every fact Xovris holds is shown with where it came from and the decisions it influenced.
One number for each fact
How many incidents need you is one figure, the same on the home, the sidebar and the board.
A quieter command centre
The command centre has a calm sidebar grouped by what you came to do, search and Ask Xovris in the header, and no running commentary.
Xovris does the work, it does not hand you instructions
For anything it supports and you have authorised, Xovris does the work through its tools and connections and explains what it did.
Autonomy that adapts to you
Xovris reads how much you have let it do over the last 90 days and suggests your autonomy level in Settings, Autonomy. Do it yourself instead: choose the level there.
An incident opens like a review
Every incident opens on a three-line summary - where and since when, why, and what Xovris is doing - with the evidence below it.
Every 'that did not look right' says what to fix
Whenever a form or request is not accepted, the command centre says exactly what to change, in plain words.
Signed out? You are taken straight back
When your session ends, the command centre shows a clear signed-out screen and takes you back to where you were once you sign in.
No access? You are told who can give it
When something needs a different role or plan, the command centre says which, and who in your workspace can change it.
Nothing there? A clear not-found screen
A link to something that is not there opens a designed not-found screen with the way back, never a crash.
A change that clashed says what happened
When two changes clash, you are told plainly that it was changed elsewhere and shown it as it stands now.
Expired links say so
A link or code that has expired opens a clear screen saying so, with how to get a new one.
Every rejected entry says what to change
When an entry is rejected, the command centre names the field and what it needs, in plain words.
A server failure says what Xovris does next
If something fails on Xovris's side, you see what happened and what Xovris is doing about it - never a bare error.
A service that did not answer is said plainly
When a service Xovris relies on does not answer, the command centre says which and that Xovris tries again.
Busy or down, in words
When a service is busy or down for a moment, the command centre says so in words, with when it will try again.
One sentence that tells you how things stand
The command centre opens on one sentence about your systems that is always backed by the record - what is fixed, what needs you, and what is being worked on.
The assistant knows the page you are on
The assistant on every page holds that page in view - ask 'fix this' on an incident or asset and it knows which one you mean.
Xovris answers in your own language
Write in any language and Xovris answers in it and says which, so your browser and voice read it right; pause and cancel work in every one.
No success without its receipt
Xovris never says something succeeded without the verification receipt behind it, linked on the page.
Asked only where Xovris does not know
Once you have set a standing answer, Xovris never asks you that approval again.
A live view of what Xovris is doing
Watch each job's real progress as it happens, and cancel from the conversation to stop every step still to come, with what was already done said plainly.
See everything Xovris is doing right now
One view shows every request and job Xovris is carrying on by itself across your workspace, each with its next step.
Every success links its receipt
Every success message links a verification receipt, and a step that was only attempted is never shown as done.
A refused step says which refusal and what next
When a step is refused, Xovris says whether it was your plan or your own yes that stopped it, and what it does the moment that is given.
Every report shows the time and money it saved
Each request's report shows the time and money that job saved you, from your workspace's own record - never an estimate.
A monthly ledger of what Xovris did and saved
Each month's value ledger lists every incident fixed and request done with its proof, and the hours of IT work they would have taken.
A morning brief of what was fixed while you slept
Open Reports to read what happened since your last visit or 6pm: what waits on you first, what was fixed and proven, and every change made.
Explain an incident to your boss, a client or family
On any incident, press 'Explain it to someone' for a plain-words version written from the incident's own record.
Never a dead end
When a run has not fixed it, Xovris names the next approach or asks one precise question - it never simply stops.
No request ends as a page to read
A request no built-in job covers is carried through to its end: Xovris finds out how, drafts the steps, tests them only with your yes, and keeps going until it is done.
A page with nothing on it yet is a board, not a wall: every section a cell that opens in place
A section with nothing to show is now one cell – a rule, a lamp, its name and what it will show – and on a page that is still empty the sections stand side by side as one board, four abreast on a desk and two on a phone. Press a cell and it opens in place, across the whole row, with everything it held. A lamp stays dark until a real reading lights it, and a section that arrives late takes the next cell and moves nothing.
Ask Xovris reads clearly on a first visit, and a whole conversation holds together
On a first visit the page’s name is the largest words on it, its four filters sit in one row and the buttons under the box take one line each. A conversation – finished, waiting on you, or stopped to ask your consent – reads whole at phone and desktop size.
Incidents and approvals open on what each fix did, with every thing called by its name
Incidents shows one line per incident: what it is, the thing it is on named in words (Front door camera, not camera.front_door), its own cause, its five steps with the live one lit, and Approve the fix on the one that waits. Approvals shows each waiting decision as its five steps stopped at Your yes, over one panel saying what it changes and where. On Workflows, Let Xovris do it for me is now chosen until you choose otherwise.
Databases, traces, status pages and family each open on their own picture
Databases opens on a picture of the database’s own measures. Each colour is explained once beneath it. Traces opens on the slowest trace of the last day, its spans on one line in milliseconds, beside its path’s last 24 hours. Status pages tells one story from one record, with the one next step it leads to. Family shows the whole household in one picture. Each person and device has its own mark, and what needs you is counted in the middle. Each device says when it last checked in.
Your workspace is drawn, not listed: a line for every sequence, a ring for everything you run, a strip for what happened over time
The Overview now shows everything you run as one ring – a lamp for each kind of thing, lit only by a real reading, red only for what needs you – beside the incident that waits for your decision. Every incident shows where it stands as five steps with their real times, on its own page and in small on every row of the incident list, with its own cause beside it. The incident list opens with the last fourteen days as one strip of cells. With motion turned down the same picture stands complete and still.
A weekly summary of what changed and what came of it
Once a week you read what Xovris found, what it fixed and how long each took, what it prevented, what waits on you and what happens next – every number taken from your own workspace’s records and traced back to them.
Ask Xovris on xovris.ai is a full conversation before you sign in
On xovris.ai you can ask Xovris anything before you have an account: the conversation opens full height beside the page, or as its own page at /ask/ with this visit’s conversations in a side rail and the message box pinned at the bottom. Sign in and the conversation carries into your command centre.
Your conversations with Xovris: rename, delete, and carry on where you stopped
Every conversation you have had with Xovris stays in the side list, searchable by what it was about. Give one a name of your own, delete one for good (you are asked once first), or reply under an open conversation and Xovris carries on from exactly where it stopped, with everything said so far. Your conversations are your own record and are never used to train Xovris.
Ask Xovris has its own page: a full conversation with the work shown
Ask Xovris now opens as a full-page conversation: a column at reading width with the message box pinned at the bottom, each answer laid out as its full report – what was checked, what was tried, how to undo it and where it came from – and the steps it took one press away. On a desktop your earlier conversations sit in a side rail; on a phone they open as a sheet, and every control is large enough to press.
Ask Xovris never loses what you typed
The message box in Ask Xovris now grows with what you write: Enter sends and Shift and Enter starts a new line on a keyboard, and on a phone Enter is a new line and the button sends. If a message does not go through, every word stays in the box and Try again sends it. If you are offline, Xovris holds your message and sends it the moment you are back online – or you can keep it as a draft. Reloading the page keeps what you were writing.
Every command-centre page fits every screen, and Ask Xovris works fully by keyboard and screen reader
Every page of the command centre is now checked at every screen width from a small phone to a wide monitor, in light and dark: none breaks into a cramped band of widths and none is ever blank. Ask Xovris reads as a conversation to a screen reader, each answer under its own heading, and works from the keyboard alone – Enter sends, Shift and Enter starts a new line, Escape closes the history on a phone.
The command centre home is never an empty screen, and every link is easy to press
The home now opens with its title and its own sentence already on screen, so you read what it is for at once – on a slow phone network, and even when your workspace cannot be reached. Every link that stands on its own is a full-size target to press, and cards that sit side by side line up at every width.
The command centre opens on what matters, with search and autonomy in plain sight
After set-up, the Overview opens on what needs you first. Incidents take structured search (key:value and comparisons), every automation shows how much it may do on its own, and alerts reach each person on the channels they use.
Every command-centre page now says first what matters on it right now
You can now open alerts, incidents, approvals, errors, monitors, on-call, control, status pages, procedures, family, domains, boards or traces and the first line tells you, in one sentence, the one thing that matters there now – whether your alerts reach you, what needs you, who is on call this minute – with the one press that moves it right beside it. When Xovris could not read something, that line says so instead of guessing.
What Xovris remembers about your systems stays honest – including saying when it does not know
Three things about your setup are now measured rather than assumed: that a correction you make is used in the next answer and the next fix instead of only being stored, that what one workspace knows never reaches another even while many people are working at once, and that Xovris says plainly it does not know something rather than answering from a fact that has gone stale. The measure is Xovris’s own and it is published, so you can hold Xovris to the figures rather than to a promise.
One way to ask Xovris, everywhere
The Ask page and the assistant beside every page now share one composer – words, your voice and up to three pictures – so asking works the same wherever you are.
The website and the command centre now share one design system across every page
Colours, type, spacing and motion now come from one source used by the website, the command centre and Xovris’s own page, so a screen can no longer drift from the rest – a page that types its own value is stopped before it ships. Every command-centre page is also checked for the same sentence shown twice, and every new line of copy lives in the shared catalogue.
Settings, each device, Help, payments, reports and memory now say first what matters
Settings opens on your plan’s state – a payment that did not go through comes first, with Billing one press away. Each device page says whether a check is running, when it was last seen, or that it is ready for your question. Payments lead with any Stripe account Xovris cannot read, then the last day’s problems; reports with how many fixes a test proved after the change; memory with anything that waits for you to confirm. Each page now reads its data once for the line and the blocks below.
A page open during an update loads the new version itself, and a TV code can be typed
If Xovris is updated while you have a page open, that page used to say it had stopped working. It now says Xovris was updated, loads the new version by itself once and brings you back – a real fault still gets its own page with Try again and a reference to quote. Pairing a TV no longer needs a phone camera: type the six letters and digits the TV shows, and with several boards the newest is the one clear choice.
What Xovris has just shipped is read strongest first
The newest changes on xovris.ai are now read strongest first: what fixes or prevents something leads, then what finds a cause, then what warns, then what connects. A new feature takes its place the day it ships, wherever the list is shown, with no page edited to put it there.
See everything people did in your workspace
A workspace-wide record shows what people did – sign-ins, approvals, members, keys, webhooks and autonomy changes – who did it and when.
Everything Xovris’s AI wrote is marked – for you and for the software that reads it
Wherever Xovris’s AI wrote something – an incident’s story, an answer from the helper, a check’s findings, a fix report or an email – it says “Written by Xovris” beside it, and the same mark travels in a form other software can read, so nothing an AI wrote is ever passed off as written by a person.
Domains and email have their own place in the command centre
Domains and email now has its own page in the command centre, in the navigation and in the command palette, beside Backups, Status pages, Reports and Family.
Every page put right at phone and desktop width
Every page of the command centre and of xovris.ai was audited on 3 October at phone and desktop width, and the fixes are now in place: a screen whose read fails says what happened and what to do next instead of going quiet, a figure or a state says the same thing wherever it appears, raw codes and placeholder words were replaced with plain ones, and pages hold their layout at every width.
Whose approval counts when a change needs two people – set by you
For changes that need a second person, you choose which roles can approve – owners, admins or members, never viewers or billing. A change counts only approvals from current members in those roles, and anyone else who tries is told who can approve instead.
Anything that breaks offers the same three ways to put it right
Wherever something needs putting right – a repair that did not pass, software with a known hole, an alert channel that stopped working, a checkout that fails for customers, a connection that needs attention, a domain to look after or the move off Opsgenie – the page offers the same choice in place: let Xovris do it, or do it yourself. Xovris does what your policy allows on its own, and where your policy keeps a step for you, nothing changes until you press one.
Glyph in your command centre shows how things are, live
The same Glyph you meet on xovris.ai now sits in the top bar of your command centre and takes its mood from your workspace’s live state: worried while an incident is open, alert while something serious is waiting, curious when there is something to look at, and at ease only when everything it reads is quiet. The words beside it say the same thing, and it tells you when part of the picture could not be read. Press it to open the assistant. A new incident also appears on your Overview the moment it opens, without a reload.
Every incident’s timeline is kept for the life of your account
The timeline of each incident – every step, decision and check – is now kept for as long as the incident itself, for the life of your account, unless you delete it or the law says otherwise. Memory says how long each kind of your history is kept.
Your own quiet hours, and windows when nothing is changed
Each person sets their own quiet hours. An owner or admin decides what a high alert does during them, and a critical alert always gets through and says so. Maintenance windows and change freezes are set in one place, and every automatic fix checks them before it runs.
Require a passkey for everyone in your workspace
An owner or admin can require every member to sign in with a passkey. It can only be switched on from your own passkey sign-in, so nobody locks themselves out, and Xovris shows first who has not set one up yet. Anyone who signed in another way is shown how to add a passkey, and API keys keep their own permissions.
See everything Xovris knows about you, and change any of it
Memory shows every fact Xovris keeps about your systems and your people – where it came from, how sure Xovris is and when it was last confirmed. Correct one in your own words, delete one and get a signed receipt, or download all of it in one file. Each week you can see what changed, and how often Xovris needed correcting.
Who is told about what, and on which channel – your choice
Under Settings and Control you decide who hears about each alert and where – critical only, high and above, or everything – and who is asked when a decision needs a person. Each rule reads back as a plain sentence before you save it, beside the live health of every channel. Every alert and decision request then follows your rules and reaches only current members of your workspace. A rule can only add people, so an alert always still reaches its usual route.
Every workspace has its own address on xovris.ai, and a renamed one keeps working for 90 days
Each workspace opens at its own address – a workspace named Acme at acme.xovris.ai – shown and copied from Settings > Address and domain. Rename it and the old address forwards to the new one for 90 days, and no other workspace can take it in that time.
Approvals and Activity: every decision waiting on you, and everything Xovris did
Approvals gathers every decision waiting on you – incidents that need your call and Xovris’s offers to do more on its own, each accepted or declined in one tap. Activity lists everything Xovris did in your workspace, with its reason, its proof and the way back. Both sit in the menu on a phone and a desktop alike.
The command centre says exactly what it knows
Every badge and summary now says “Not read yet”, “Nothing found so far” or “All clear” – and all clear only once everything was read in full. Settings fits a phone with every section in view, a workspace with no paid plan says plainly that nothing is being charged, an incident shows the proof mark beside its title only once the fix is proven, and the command centre reports its own crashes to Xovris’s team the same day.
One bar across the top of everything: your workspaces, search, what needs you, and Xovris
Every page of the command centre now has the same top bar: switch workspace, press Ctrl or Cmd K to reach anything, open the list of what needs you right now, and open Xovris beside the page – a sheet on a phone – without losing your place.
Every control over Xovris in one place, each saying what a change will do before you save it
You can now choose for each kind of problem and each system whether Xovris fixes it, prepares it and asks, or just tells you; set spending limits; decide what Xovris may touch and which services are connected; manage team or family members and their roles; see, export or forget what Xovris remembers; and change your plan and billing – on one Control page and in Settings, each change saying what it will do before you save it.
See everything Xovris watches, with countdowns, and every report in one place
The app now shows everything Xovris watches and how healthy it is, with each prediction as a countdown – a certificate that expires in 12 days, a disk that fills in 9 – and how sure Xovris is of it. Incident reports and proofs of prevention, the morning brief and the monthly statement of time and money saved sit beside it, each ready to share or download, the same on a phone as on a desktop.
Your choices about your data hold on every step Xovris takes
Pausing memory, the AI companies allowed to read your data and the region it is processed in are one set of choices, checked on every step Xovris takes for you. Change one and the very next request follows it.
Your data is never used to train our AI
Your systems, files, logs and settings stay yours: they are never used to train any AI, ours or anyone else’s, and nothing of yours ever reaches another customer. Xovris remembers your setup only to help you – pause it, see it, correct it, and delete anything with a signed receipt on your Memory page. The promise is on the trust page, the privacy policy, the terms, pricing and every page’s footer.
What Xovris remembers at home stays yours
If Xovris looks after you or your household, what it remembers about your setup stays in your own memory and is never used to train any AI. Anything you tell Xovris that it never needs to fix something – a password, a key, a card number, a bank account or a National Insurance number – is replaced before it is remembered, and the record of what was remembered says so.
Every email about your account, sign-ins and billing says what happened and the one thing to do
Welcome, invitations, a changed sign-in address, a new or unusual sign-in, receipts with their tax lines, and a payment that did not go through – with the reason in plain words, which try it was, when the next one is and what happens after the last. A card about to expire, a trial starting and ending (never a charge without your say-so), plan changes, refunds, fix packs, account deletion and a data export ready to download all have their own email too. Each has the same clear layout as the rest of Xovris in light and dark, a plain-text version complete on its own, and amounts in your own currency exactly as charged.
Ask for anything in your own words, and Xovris takes it from there
Tell Xovris what you need – “make my Wi-Fi secure”, “my printer says offline” – and it asks only what it needs, one question at a time, asks only for the one act that needs your hands, and asks before it changes anything. On your own router it signs in only with the password you type yourself, checks every connected device is back online afterwards and puts everything back if one is not. It never just says no: if the law, your safety or someone else’s consent stands in the way, it says which, and what would clear it. Nothing of yours ever goes to anyone else.
Ask your logs in plain words, and every answer shows the lines it rests on
You can now type a question – “payment errors this morning” – and Xovris answers first, in sentences, each pointing at the lines and the kind of line behind it, with anything never seen before flagged. Open any line to see what happened around it and the incident it explains, and every source shows how many lines it sent and stored, so you know nothing is being lost.
Every error tells you what to do next, and every email arrives clear and correct
Xovris now lists every email it can send and every error it can answer straight from its own code, on every build: 274 error answers, each saying what happened and what to do next, and 14 emails, each rendered through its template by email, Slack and webhook. Xovris never ships an error without words or an email without its template.
When something cannot be done, Xovris says why, whose problem it is and what to do next
Every answer Xovris can refuse with now opens its own state in place, in its own words: something that changed while the page was open, a code that has expired, a file too large with the limit named, a part of Xovris not switched on yet, a service like Stripe that did not answer – never called Xovris’s own failure – and a brief update that tries again on its own. Alerts that did not go out say why and the one thing to do, from a paused sending switch to a webhook without a signing secret.
Ask Xovris to forget something and it stays forgotten – even after a backup is restored
Delete something Xovris knows about you and it is removed from everything that held it – what Xovris remembers, its history and anything waiting to be reused – with a signed receipt listing each place that was checked and found empty. If Xovris ever restores its own data from a backup, everything you deleted is removed again before anything is served, so a restore can never bring it back.
Your data is never used to train our AI, said plainly on the trust page
xovris.ai/trust now says it in one line: your data is never used to train our AI or anyone else’s. What Xovris remembers about your setup serves only you – you can see it, correct it, pause it and delete anything with a signed receipt – and each card on the page is tested against the control on your Memory page, so the page can only say what the product does.
Xovris remembers what you told it, never what it only guessed
Everything Xovris remembers about your setup now says what kind of knowledge it is – something you told it, something it saw, or only a guess – and only what you told it, or a setup a check proved, can decide what a fix puts back. A sentence like “what if we moved our email?” or text pasted from an error is never kept as your setup, a fact Xovris has not seen for a while is checked again before anything is changed because of it, and something you asked it to forget is never kept again. You can switch off any fact for automatic changes, download everything it knows, and ask what it believed at any moment.
Xovris remembers your systems – and you can see, correct, undo or pause every bit of it
Ask what Xovris knows about your setup and you get every fact with where it came from, how sure it is and when it was last confirmed. Correct a fact once and every later answer and fix uses the correction. Each change to what it believes can be undone like an edit, nothing one person shares reaches another beyond their role, and a session with memory off stores nothing at all. A new account keeps only what your own systems confirm.
Xovris never just says no
Whenever something stands in the way – in the app, the docs, the setup and every alert – Xovris works out a way through, and where only a person can act it says exactly what is needed and who can give it, so there is always a next step.
When Xovris asks you to wait, it says for how long – and when something is too large, it says the limit
Every time Xovris asks you to slow down it now says exactly how long to wait, worked out from your own recent requests, and the command centre counts down to the moment you can try again. When something you send is too large – a log batch, an alert delivery, a pasted error – the answer names the limit, such as 10 MB or 16,384 characters, so you know what to send instead.
Webhooks for the whole life of an incident, with every attempt on record
Your own endpoint now hears when an incident opens, when its alert fires and when it recovers, when a fix is proposed, applied and proven or rolled back, and when it is resolved – each signed so any Standard Webhooks library can check it came from Xovris. If your server answers with an error, Xovris tries again on a published schedule with the same id, and every attempt – its time, your server's answer and why it failed - is listed in Settings and through the API.
One plain letter a week: what was checked, found, fixed and prevented
Every Monday Xovris writes what it checked, what went wrong, what it fixed and proved, what it renewed before it could lapse, what that cost you and what it suggests next – for you, your household or your business. Every number in it comes from your own records, and the same letter is on your Overview with where each number comes from.
You pay only for fixes that work, and no web page can talk Xovris into anything
Every fixed issue on your bill now carries its proof: the test that failed before and the same test passing after. A fix is only held while Xovris works, charged once it is proven, and taken off again if the fault comes back during the follow-up or a person has to take over. And whatever a status page, a web page or an error message says – even text written to trick an AI – it has no say over what Xovris checks, concludes or shows you: in 200 planted attacks, none got through.
One emergency stop, and what each auto-fix choice would have done last month
One press on Control, in Settings or on Automation stops every change Xovris would make in your workspace, and one more lets it carry on – each saying what it does before you press. Before you save an auto-fix choice, Xovris works out from your own last 30 days what it would have fixed itself, asked you about or told you about, beside what your settings as they are did, with your own incidents as examples.
Separate workspaces, roles that decide what each person can do, and a second approval where you want one
Each customer’s workspace is its own environment: every table that holds customer data answers one workspace with its own rows only, and a request with no workspace is refused instead of answered empty. Owner, admin, member, viewer and billing each do what their role allows – a viewer reads and cannot change anything, billing pays but does not operate – and every decision is recorded with what it rested on. A workspace can require a second person for a kind of change from a risk level it chooses; billing and viewer can never give that approval.
Every app you add shows how it is doing
Each app added to Xovris shows where it is called, what reached it and its last failure, with a signed test you can send from its card and a clear way to remove it.
Jump anywhere with Ctrl+K or Cmd+K
The command centre opens a search-and-jump palette from anywhere, so every page and action is a few keystrokes away.
The other areas
Words on this page, in plain English
Each technical word this page uses, said simply.
- A message sent to your own system (webhook, webhooks)
- An automatic message one service sends to an address you choose the moment something happens.
- Program-to-program connection (API, APIs)
- A way for one program to ask another for information or to do something, without a person clicking through a website.
- An address a program calls (endpoint)
- One web address of a service that a program sends its requests to.