SMB IT Off-Ramp / Documentation Scanner

$65.00

the founder or office manager who quietly became the IT department and now has to document it or hand it off. It’s what you’d write yourself if you had the week to sit down and do it.

Local-firstNo telemetry — nothing phones homeNo lock-inNo migration

Run it once and it writes four files: an asset inventory, a prioritized risk checklist, a fill-in-the-blanks MSP handoff runbook, and the raw inventory.json behind them.

It reads the machine and changes nothing.

$65 a month, or a $250 one-time audit if you just need the document once and never again. Cancel any day. The output is markdown and JSON on your disk, so it stays yours either way.

The person who set up the wifi and now owns all of it

You picked the laptops, you named the shares, you know which account the old printer runs under. None of it is written down, because it never had to be. It lives in your head.

Then you want to hire an IT person, or bring in a managed-service provider, or just go on holiday without your phone ringing. And the first thing anyone asks for is documentation you’ve never had a reason to produce.

The cost isn’t the tools. It’s the week of your life you’ll spend reconstructing from memory what the machine could just tell you.

What one read-only pass actually does

  1. It runs a fixed set of read-only inventory commands. Each one is invoked with execFile and a hard-coded argument list, so no config string ever reaches a shell and there’s nothing to inject into.It runs entirely on your own machine, and nothing it does phones home.
  2. It folds in your vendors. Point VENDORS_FILE at a CSV or JSON of your SaaS and suppliers and they land in the same runbook as the hardware.
  3. It redacts, then writes. Captured output passes through secret redaction before anything hits disk, and the package is written at 0600 under {Org} IT Documentation/.

What lands in the folder

  • ASSET_INVENTORY.md, covering system, disks, network, installed software and local accounts, so the stuff only you knew is finally written down.
  • RISK_CHECKLIST.md, with findings ranked high, medium, low and info, each carrying a concrete fix, so you work the list from the top instead of guessing where to start.
  • MSP_HANDOFF_RUNBOOK.md, a fill-in-the-blanks runbook covering access and accounts, network, vendors, backups and open risks. Your next hire or MSP starts from a document, not an interview.
  • Secret redaction that strips private keys, AKIA-style AWS keys, Slack and GitHub tokens, and password= patterns before the write, so credentials don’t end up in a file you email around.
  • Any probe it can’t run on this OS or privilege level is reported as unknown, not guessed, so nobody gets a false all-clear.
  • inventory.json, the raw machine-readable version, and cross-platform support on Windows, macOS and Linux with nothing to install past dotenv.

Who should run it, and who already has this covered

Any shop of roughly 1 to 50 people where one non-specialist set up the technology and is now on the hook for it. Owner-as-IT, office manager wearing the ops hat, the person who says “I’ll just do it.”

Not for you if an MSP already keeps you in IT Glue or Hudu and updates it as things change. Those are built to be the living record, and a maintained record beats a snapshot. This is for the shop whose documentation is a folder that doesn’t exist yet.

What it replaces, and where those tools win

IT Glue and Hudu are the real documentation platforms, and they’re better at staying current: an MSP updates them continuously and links every asset to a ticket. But they’re priced and shaped for the MSP, not the owner, and they assume someone is already doing the documenting day to day.

The honest competitor here is the runbook that lives only in your head, and the night before you hand someone the keys and try to write it all down at once. This produces the first real draft from the machine itself, in one run.

Where the data goes, and what gets stripped first

There’s no cloud call in this one at all. The package is written to a local folder and nothing is uploaded, because nothing was built to upload it.

The output legitimately holds hostnames, account names and IPs, which is useful to an MSP and equally useful to an attacker. So it’s written at 0600, the whole IT Documentation folder is git-ignored by default, and secret redaction runs before the write rather than as a cleanup after.

The price, and what shows up when you run it

$65 a month, or $250 for a single audit. You set two values in .env and run it. On a normal workstation the first package is ready in a few minutes.

It’s a single-machine scan today. Network-wide discovery across several machines is on the roadmap, not in the box, and the docs say so plainly rather than implying it’s there.

Security and privacy

This tool inspects a business machine and writes documentation about it. It is designed to be safe to run on a production office PC.

Principles
Read-only. It never changes a system setting. It only *reads* inventory data via a fixed set of OS commands and files.
No shell injection. Every command is invoked with execFile using a hard-coded binary name and fixed argument array — no user/config string is ever interpolated into a shell. There is no shell.
Local by default. Nothing is sent anywhere; the documentation package is written to the local OUTPUT_FOLDER. (No cloud calls in this product.)
Fail soft. Every probe is wrapped and time-bounded; anything unavailable is reported as unknown rather than crashing or guessing.

Protections implemented (v0.1.0)
Secret redaction — captured command output is passed through redactSecrets() which strips private keys (-----BEGIN … PRIVATE KEY-----), AWS keys (AKIA…), Slack/GitHub tokens, and password=/api_key=/secret= patterns before anything is written to disk.
Command allowlist + timeouts — only a fixed set of read-only inventory commands run, each with a CMD_TIMEOUT_MS bound and a capped output buffer.
Path-traversal defense — the org name is sanitized (safeSegment) and every write is checked with assertWithinRoot(), so output can’t escape OUTPUT_FOLDER.
Restrictive permissions — all generated files are written 0600.
Secrets discipline.env, key files, and the generated … IT Documentation/ folder are git-ignored.

Sensitivity of the output
The generated documentation legitimately contains hostnames, account names, IPs, and security posture — useful to an MSP but also useful to an attacker. Treat the output folder as sensitive: keep it access-controlled and share the runbook only with the intended MSP/owner.

Distribution / AV trust

Known limitations / roadmap
– Single-machine scan in v0.1.0; network-wide discovery is on the roadmap.
– Software/account enumeration depth varies by OS and privilege level (reported honestly as unknown when a probe can’t run).
– Risk checks are heuristic and intentionally conservative; they prompt verification rather than asserting compromise.

Reporting
Report suspected vulnerabilities privately to the maintainer before public disclosure.

Frequently asked questions about SMB IT Off-Ramp / Documentation Scanner

What does SMB IT off-ramp software do for the accidental IT admin?

SMB IT off-ramp software is built for the person who never signed up to run IT but ended up doing it anyway. That is the owner, the office manager, or the operations lead who holds every password and knows where the server sits in the closet. The tool points at your network, your accounts, and your file locations, then builds a plain inventory of the systems you actually run. You get a written picture of what exists, what each part does, and where the risk sits, without paying an outside shop just to tell you what you already own.

The scan works in a clear order. First it walks your systems and files to build a self-serve IT inventory, so critical knowledge stops living only in your head. Next it flags backup, security, and documentation gaps before they turn into an emergency at the worst possible moment. Then it produces an MSP-handoff runbook, so when you do bring in outside help, they onboard in hours instead of a week of interviews. Owner-facing tools like this fill a real gap, because the products they compete with were built for managed service providers, not for the business owner sitting at the desk.

That inventory step matches how the U.S. National Institute of Standards and Technology frames the first job of any security effort. The model is plain: you cannot protect what you have not identified. You can read the six functions in the NIST Cybersecurity Framework, and the Identify function is the exact gap this scanner closes for a small shop with no dedicated admin. A written record of hardware, software, accounts, and data locations is where that function starts, and it is the piece most small businesses simply never wrote down.

The point is to give you a defensible record instead of a mental map that vanishes the day you are out sick. When an auditor, an insurer, or a new hire asks how your systems are set up, you hand them a document, not a shrug. SMB IT off-ramp software turns scattered knowledge into something you can review, share, and hand off cleanly. To see how the inventory, the risk flags, and the runbook fit together, visit the off-ramp scanner product page and walk the workflow before you commit to anything.

The tool does not try to replace your judgment or your future IT partner. It replaces the guesswork. For an accidental admin, the hardest part is rarely fixing a problem, it is knowing which problems exist and which ones deserve attention first. By sorting findings into a single inventory and a short list of gaps, the scanner lets you act on the items that carry real risk and park the ones that do not. That is a practical starting point for any owner who has been meaning to write all of this down for years and never once found the time to sit and do it. A short, honest inventory today is cheaper than a frantic reconstruction later, and it is the kind of work that only gets harder the longer a business puts it off. The tool exists to make starting easy.

How does it help me protect customer information the way the FTC expects?

Most small businesses are surprised to learn they fall under formal data-security duties. If you handle customer financial details, you may be treated as a financial institution under federal rules and owe a written security program. The SMB IT off-ramp software helps by first showing you what customer data you actually hold and where it lives, which is the honest starting point for any program. You cannot write a policy about systems you have not mapped, and the scanner maps them for you in one pass.

The Federal Trade Commission spells out what that program must contain. Under the FTC Safeguards Rule, a covered business must develop and maintain an information security program with administrative, technical, and physical safeguards designed to protect customer information. The rule assumes you know your systems, your access points, and your risks. The scanner produces that raw material, so the written program describes something real instead of a generic template pulled off the internet.

Here is how the tool supports each side of that duty. On the technical side, it flags weak spots like missing backups, stale accounts, and undocumented services that an attacker would find first. On the administrative side, the MSP-handoff runbook doubles as documentation you can attach to a security plan, showing who does what and how systems are configured. On the physical side, the inventory records where machines and data sit, which is the first thing an assessor asks about. The SMB IT off-ramp software does not write your policy for you, but it removes the excuse that you did not know what you had.

This matters because the alternative is a plan built on memory. Memory is where small businesses get caught, because the one person who understood the setup is exactly the person who leaves, retires, or gets sick during an audit. A current inventory and a gap list give you evidence that you took reasonable steps, which is the standard regulators actually look for. You are not expected to run an enterprise security team. You are expected to know your risks and address them in a documented way.

To understand how this fits a broader operations and compliance posture, it helps to see the tool inside its category rather than on its own. The IT, operations, and compliance overview shows how an inventory feeds risk tracking, backups, and handoff, so a single owner can carry the load without an MSP contract. SMB IT off-ramp software gives you the first artifact almost every framework and rule asks for, which is a written, current picture of your environment. From there, closing gaps becomes a checklist instead of a scramble. That shift, from guessing to documenting, is the whole reason an owner-facing tool exists in a market that otherwise only sells to service providers who never talk to the business owner directly. Regulators do not expect a small business to run like a bank, but they do expect you to know your systems and to act on the risks you find. A current inventory and a documented gap list are exactly the kind of reasonable, provable steps that hold up when someone asks what you have done to protect the data you keep.

Where does my inventory data live, and who can get to it?

This is the right question to ask before you run any scanner across your own network. The tool builds an inventory of sensitive things, including accounts, systems, and where your data sits, so how that inventory is stored and who can reach it genuinely matters. The off-ramp scanner is built to keep that record close to you, the owner, rather than exposing it across a shared MSP dashboard that a dozen technicians can open. The inventory is yours, and the point of an owner-facing tool is that you control who sees it.

Access control is not a nice-to-have detail here, it is a recognized security requirement. The U.S. National Institute of Standards and Technology treats it as a core control family. In NIST SP 800-171, the security requirements for protecting sensitive information in nonfederal systems begin with Access Control, meaning you limit system access to authorized people and to the functions they actually need. An inventory of your environment is exactly the kind of sensitive record those controls are meant to guard, and the tool is designed with that principle in mind rather than against it.

In practice that means the inventory and the risk findings are scoped to you and the people you choose. When you hand a runbook to an outside firm, you decide what goes in it and when they get it, rather than granting standing access to everything. That is a real difference from tools built for service providers, where broad, always-on visibility is the default because the provider, not the owner, is the intended user. The SMB IT off-ramp software flips that model so the business keeps the keys.

Keeping the record close also reduces your blast radius if something goes wrong elsewhere. A single owner-held inventory is a smaller, more contained target than a multi-tenant platform holding hundreds of clients. It is easier to reason about who can reach your data when the answer is a short list of names you recognize. That containment is a security feature in itself, not an afterthought, and it lines up with the principle of least privilege that the access control requirements describe.

None of this replaces good habits on your side. You still choose strong credentials, you still decide who on your small team can open the inventory, and you still control when an outside partner receives the handoff runbook. What the SMB IT off-ramp software gives you is a setup where those choices are yours to make, backed by an audit trail of what the tool did and when. If you want to see how access, storage, and the handoff export are handled in detail, the product page walks through where the data sits and how you keep control of it. For an owner who is already stretched thin, knowing the sensitive map of your business is not floating around a vendor’s shared console is worth a great deal of peace of mind. The safest sensitive record is one only the people who need it can reach, and that is the standard the tool is built to keep for your inventory. Control over the map is control over the risk.

How is this different from IT Glue or Hudu, and does it help me respond when something breaks?

The short answer is who the tool is for. IT Glue and Hudu are documentation platforms built for managed service providers, the outside firms that manage IT for many clients at once. They are excellent at what they do, but they assume a technician is the user. The off-ramp scanner is built for the opposite person, the owner or ops lead running IT themselves, who needs a plain inventory and a risk list without learning a provider-grade platform or signing a provider-grade contract.

That difference shows up in the output. Instead of a sprawling knowledge base meant for a team of technicians, the tool gives you a focused inventory, a short list of gaps that carry real risk, and an MSP-handoff runbook you can send when you finally do hire help. It scans your systems and files to build the inventory automatically, rather than expecting you to type everything into templates by hand. The SMB IT off-ramp software meets you where you are, which is busy and untrained, not staffed and specialized.

Readiness to respond is where the gap really bites. When an account is compromised or a system fails, the questions come fast: what do we have, what is affected, what do we do first. The Federal Trade Commission’s Data Breach Response guide tells businesses to move quickly to secure operations and fix the vulnerabilities that may have caused the breach. You cannot move quickly if you do not know what you own. A current inventory and a gap list are precisely the documents that turn a panicked scramble into a set of concrete steps.

The tool supports response before an incident, not after. By flagging backup, security, and documentation gaps early, it helps you fix the weak points that response guides tell you to close, while there is still time to close them calmly. The handoff runbook means that if you need an outside firm mid-incident, they onboard from your document instead of interviewing you while systems are down. That readiness is the practical payoff of doing the inventory work in advance rather than under pressure.

So this is not a smaller IT Glue. It is a different product aimed at a buyer those platforms were never designed to serve. The SMB IT off-ramp software gives an owner the inventory, the risk view, and the handoff artifact in one place, priced and scoped for a business without an IT department. If and when you graduate to a managed service provider, the runbook is what you hand them, and nothing you documented goes to waste. To see how the inventory and the handoff runbook are structured for exactly this moment, the IT, operations, and compliance overview shows where the tool fits alongside backup and risk tracking for a one-person IT shop who cannot afford to be caught flat-footed. The practical test is simple. Ask whether a tool expects a trained technician or a busy owner, and you will know which side of this divide it sits on. The off-ramp scanner is built for the owner, and the SMB IT off-ramp software gives that owner the inventory, the risk view, and the handoff runbook without demanding skills they were never hired to have.

Can it help me securely retire old machines and drives when I off-ramp equipment?

Retiring equipment is where the off-ramp part of the name earns its keep. When a laptop, a server, or a drive leaves your business, the data on it does not leave just because you deleted a few files or dragged them to the trash. Old hardware is one of the most common ways sensitive records walk out the door, because owners assume a quick format is enough. The SMB IT off-ramp software helps by keeping that gear in your inventory until it is genuinely accounted for, and by flagging retirement as a documentation step rather than an afterthought.

There is a recognized standard for doing this right. The U.S. National Institute of Standards and Technology publishes NIST SP 800-88, Guidelines for Media Sanitization, which explains how to render data on storage media unrecoverable when you dispose of or repurpose a device. The core idea is to make access to the target data infeasible for a realistic level of effort, whether that means clearing, purging, or physically destroying the media. The tool does not wipe the drive for you, but it makes sure the drive is on your list and that its disposal is a tracked, deliberate action instead of a forgotten box in a storage room.

Here is how that plays out. The scanner builds and holds an inventory of your systems and storage, so when a machine reaches end of life you can see it, mark it, and record what happened to the data on it. That record is the difference between an off-ramp you can defend and one you cannot. If an auditor or insurer later asks how you handled a retired device holding customer data, you have a documented answer that points to a sanitization step, not a guess about what a former employee may have done with the old server.

This matters even more during a bigger transition, such as switching providers, closing a location, or handing IT to a managed firm. Those are exactly the moments when equipment changes hands quickly and data gets left behind by accident. By tying retirement into the same inventory and MSP-handoff runbook it already produces, the SMB IT off-ramp software keeps disposal from falling through the cracks while everything else is in motion. The runbook can note which devices were sanitized and which still need attention.

None of this asks you to become a security specialist. It asks you to treat a retired drive with the same care you treat an active one, and it gives you the list and the reminders to make that realistic for a busy owner. Secure disposal is not glamorous, and it is one of the first things a stretched business skips, which is exactly why building it into the off-ramp workflow matters. To see how equipment retirement, inventory, and the handoff runbook connect, the off-ramp scanner product page lays out the full flow from active system to safely retired device. Retiring a device the right way is a small, unglamorous habit, and building it into the same workflow you already run is what makes the habit stick. A tracked disposal today prevents a hard question tomorrow.

Attributes Value
Deployment

Hybrid

Platform

Web, Windows

License Type

Subscription

Billing Period

Monthly

Target Customer

IT, Ops & Compliance

Free Trial

Yes

Reviews

Be the first to review “SMB IT Off-Ramp / Documentation Scanner”

Your email address will not be published. Required fields are marked *