Deployment and IT health

Use deployment for your first IT health review.

Rebasoft goes onto infrastructure you already run, and the first collection already shows rejected credentials, coverage gaps and out-of-date assets to put right.
Time to value

From uncertainty to assurance in 3 days

With no agents to roll out, the clock starts once access and collection accounts are in place. These are your first results, and coverage keeps improving from there.

Day 1
See what you have

Discovery builds your asset, user and SaaS inventory, and shows the gaps nobody knew about.

Day 2
Focus on what the business runs on

Define your first business services, and vulnerabilities rank by the importance of the service they affect.

Day 3
Show where you stand

Check your controls, find configuration gaps and draw the evidence for your IT health review.

Simple setup

Three VMs, network access and collection accounts are all it takes

Your existing infrastructure

Three VMs in production on your VMware, Hyper-V, Proxmox or Azure, sized to your estate, with storage, IP addresses, DNS and NTP.

Network access

A console certificate and approved firewall paths, read-only SNMP on seed switches and routers (SNMPv3 recommended), and outbound paths for cloud sources, feeds and updates.

Collection accounts

A dedicated Windows account with local administrator rights for full collection, with WinRM preferred. An SSH account on Linux, Unix and macOS, without root. Read permissions for hypervisors, cloud and Microsoft Graph.

No endpoint agents to deploy or maintain, and no SPAN ports or packet capture.
What you see first

Your team sees results from the first collection

This sequence is your first IT health review. Partners can deliver it as a fixed-scope project.

  1. Install

    The appliances go in

    Three VMs are imported onto your hypervisor, host roles are set and the licence is loaded, with nothing touching your endpoints.

  2. Connect

    Your sources come online

    The team adds seed switches and routers, tests credentials and connects APIs. Site rules place devices by subnet and hostname, with no manual sorting.

  3. First collection

    Your estate takes shape

    Assets appear on a discovery ladder with counts at each stage, so your team sees what is present and how much is known about it.

  4. First full cycle

    Discovery explains itself

    Where most tools leave a list of failures, Rebasoft groups them by cause and owner. A scatter of unreachable hosts points to powered-off desktops, the same count in one subnet to a routing change, and rejected credentials stand apart from missing ones.

  5. Next

    Coverage climbs and the value follows

    Each resolved issue moves assets up the ladder, and vulnerabilities and Today’s Work fill in behind it. Alongside this, your team refines its first business services.

An illustrative sequence. Timing follows your access, sources and collection schedules.

Control

You stay in control from day one

Your choice of who deploys

Your team or your partner deploys Rebasoft, with Rebasoft’s support behind them.

Your access, your decision

Your infrastructure, network and identity owners decide what each source can reach.

Your existing resilience

Each role runs as a single instance on your hypervisor, so its high availability protects Rebasoft with no separate cluster to run. Name owners for backups and upgrades.

Questions
How soon will information appear?
Information appears as your first sources collect, so your team sees results during deployment. One full collection cycle gives a sound view of coverage.
Must every source be connected and every service modelled before starting?
No. Teams begin with the sources they have to hand and one business service that matters, and build from there.
What does collection do on the network?
Rebasoft learns hosts from network tables and feeds, then probes selected management ports and collects over standard protocols, so there is no agent footprint on your endpoints.
Where is our data held?
Your data is held on your deployment’s hosts, wherever you place them, and you choose where backups go. The credential vault and documents are encrypted, and your host, storage or hypervisor encryption protects database volumes and backups, so control stays with you.
Can it run on a restricted network?
Yes. Offline feed import and offline upgrade packages keep a restricted site current, and cloud sources use a connection to the provider.

More questions? See the full Rebasoft FAQ — answers by topic and by role, or how Rebasoft is priced.

See what a first collection delivers on an estate like yours

A 30-minute walkthrough of a live console shows the discovery ladder at work and what your team would need to provide.