How it works
A request comes in.
Nervor understands it.
- User
- e.clarke
- Department
- Quality
- Request
- Access to the Engineering folder
It prepares the action.
Add-ADGroupMember -Identity GRP-Engineering -Members e.clarke
A technician corrects it.
Nervor learns.
- Check the requester’s department
- Quality: read-only, ReadOnly group
- Add the user to the group
Next time, it’s already right.
Add-ADGroupMember -Identity GRP-Engineering-ReadOnly -Members o.bennettFrom the procedure “Engineering folder access”
On your servers. Not ours.
Nervor has no cloud where your data ends up. It runs inside your network, next to the systems it manages.
Nothing runs without a technician.
The full command is shown next to the real state of the system before anyone approves it.
Every decision is on record.
Who approved what, and when. Log entries are chained, so a later change shows.
You can go back.
Reversible actions are undone with one click. The ones that aren’t are declared up front.
Security is built in, not added.
Every feature is designed and checked with people who do information security for a living, before it reaches your servers.
The memory stays
Day 1.
Month 3.
Year 1.
James is leaving.
What he knew is still here.
- Tom H.
- James W.
- Emily C.
- Ryan P.
What it does today.
- Active Directory accounts and groups
- Unlocks and password resets
- DNS records
- DHCP reservations
- Shared folder permissions
- Network printers
- And much more on the way.
Each new system arrives as one more skill, with the same rule: it asks first.
Straight answers.
Do I have to replace my ticketing system?
No. Nervor starts from the helpdesk mailbox and works alongside the tools you already use.
Who decides what gets executed?
Always a technician. They see the exact command and the real state of the system, then approve, correct or reject.
Where does the data go?
It stays on your servers. Only the text of the request reaches the AI model, through an account in your company’s name.
What if it can’t handle a request?
It hands it to a technician for manual review, without proposing any action.
What format is the knowledge in?
Plain text files in an open format, with the history of every change. They’re yours to read, edit and take with you.
What happens when a technician corrects it?
The correction becomes a proposed update to the procedure. It enters the knowledge base only after someone approves it.
How do we get started?
You write to us, we talk to understand how your infrastructure is set up and we show you Nervor at work. Then we install it on your servers and follow it closely from day one.
Let’s meet.
Tell us how your infrastructure is set up: we’ll show you Nervor at work on cases like yours and work out together where it can make a difference.
A reseller or an investor? Pick your profile and tell us what you’re looking for.