DESIRED-STATE ENDPOINT MANAGEMENT

Endpoint automation.In full view.

PROVISION · CONFIGURE · VERIFY

Tell Overseer what every computer should look like. It reads each machine, puts right whatever has drifted, and checks the result before it calls the job done.

Ask about launch See how it works
In development — not yet available. Launch inquiries are welcome.
The Overseer owl above a Fleet Command view: declared software and settings flowing to every computer
A standard you declare once, not a script you run again
Every change checked on the computer itself
Nothing runs without a decision someone made by name
HOW IT WORKS

Say what should be true. Overseer keeps it true.

Four steps, the same every time — on one computer or across every client you look after.

The Deployments screen: each row declares what should be installed, for which clients and computers
1

Describe the standard

Pick the software, settings and tasks a computer should have — for every client, one client, a tag or a single machine. New computers in scope pick it up on their own.

A detection pass: each application read from the computer and marked compliant
2

Read the computer, not a report

Overseer asks each machine what is really there and compares it with what you declared. This pass changes nothing — it only tells you where things stand.

The Schedules screen: when detection and maintenance are allowed to run for each client
3

Put it right when you say

What is missing gets installed, what is old gets updated and what should not be there comes off — inside the maintenance window you set, or the moment you press Run.

A finished session: 100 percent complete, every action accounted for
4

Checked before it is called done

After every action Overseer looks again. A computer is only marked compliant when the check passes, and the whole session is kept for you to read back.

ONBOARDING

Bring every setup into formation.

One view of progress, blockers and readiness.

A new computer goes from the box to ready for its user in a single run you can watch: assigned to its client, software installed, restarted where it has to be, then verified.

  • See a whole batch of computers at once
  • Know exactly what is stopping a machine
  • Hand it over only when it is verified ready
Read about onboarding →
An onboarding board: six computers moving through assign, install, restart, verify and ready
Three steps of an authorisation: a named decision, a preview of what would run, and a record of who authorised it
STANDING AUTHORISATION

Automation. On your terms.

Define the scope. Preview the work. Trace the authority.

Overseer only acts on its own where somebody has said it may: this client, this item, this action. See exactly what would run before anything does, and afterwards see which decision allowed it.

  • Scoped permission
  • Execution preview
  • Traceable decisions
Read about standing authorisation →
SOFTWARE AND SCRIPT LIBRARY

Start from the library. Add what is missing.

Search the Windows Package Manager catalogue by name and add an application in one step, or upload your own installer. Built-in scripts cover diagnostics, maintenance, networking, patching and pre-flight checks — and the editor is there when you want to write your own.

WINGET CATALOGUE YOUR OWN INSTALLERS POWERSHELL SCRIPTS
Browse the script library →
The software library: applications ready to deploy, with their source
Built-in scripts grouped by purpose: diagnostics, maintenance, network, patching, pre-flight

In development. Launch inquiries welcome.

Overseer is still being built and is not available yet. If you would like to hear when it launches, get in touch and we will keep you posted.

Ask about launch Read the documentation