Keep the tools you run. Overseer works beside them.
Overseer does not ask you to replace anything. Its own lightweight agent runs next to your remote management tool, and the tools that already know your clients, computers and people supply the facts your deployments use for targeting.
Beside your current tools
The Overseer agent installs next to your remote management tool. Neither one has to be removed.
Clients brought in
Clients and computers come from the tools that already list them, so nobody enters them a second time.
Facts drive targeting
Aim a deployment at what another tool reports: a directory group, a service agreement, a computer it already tracks.
Build your own
Where no integration exists, write one in PowerShell and use it like the built-in ones.
Every tool keeps its own list.
- The same client, entered againA new client goes into your PSA, then into every other tool, by hand.
- Lists that drift apartOne tool shows a computer the other has never heard of, and nobody knows which is right.
- Targeting kept by handWho gets which software is kept in a list that someone has to remember to update.
- Replace it or go withoutAdopting a new tool often means removing one your technicians already depend on.
Your tools supply the facts. Overseer acts.
- An agent of its ownOverseer does its work through its own lightweight agent, so your remote management tool carries on unchanged.
- Clients matched to tenantsEach client another tool knows is matched to a tenant in Overseer, with its computers under it.
- Targets that keep upWhen a person joins a directory group, the deployments aimed at that group apply to their computer at the next maintenance session.
- Tags where nothing connectsWith no integration for a tool, a tag on the client or computer gives a deployment the same target.
Connect a tool. Use what it knows.
Connect
Open Integrations and connect a tool you already run.
Match
Match the clients that tool knows to tenants in Overseer. Their computers follow.
Target
Aim deployments at what the tool reports, alongside clients, tags and single computers.
What each tool knows. What you do with it.
| Kind of tool | What it tells Overseer | What you do with it |
|---|---|---|
| Remote management tool | Your clients and the computers under each | Bring them in and run the Overseer agent beside it |
| PSA | Your clients and the agreements they hold | Match clients to tenants and aim deployments by agreement |
| Identity provider | People and the groups they belong to | Aim a deployment at a group so it follows the person |
| Security software | Which of your clients and computers it covers | Deploy its agent to the computers that should have it |
| A tool with no integration | Whatever you write your integration to report, in PowerShell | Use it as you would a built-in integration |
Connecting changes no computer.
An integration gives Overseer facts to read. Work on a computer still needs a deployment, and a schedule or a person to run it.
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.