It tells you before your users do
An agent on every machine watches CPU, memory, disk health, services, event logs, logins and uptime around the clock.
MorePulseway is the monitoring, patching and remote-control platform that lets one person run the IT of a whole company from a pocket. We install it, configure it, and collect the logs it doesn't keep - starting at a single computer, priced for a small business.
What you get · The engine
Pulseway is used by more than 13,000 businesses in 80-plus countries, by its own count. Here is what it actually does for the person who gets the 7am "the printer's down" text.
An agent on every machine watches CPU, memory, disk health, services, event logs, logins and uptime around the clock.
MoreWindows updates are approved by rule, by severity, CVE score and age, and installed on a schedule that reboots after hours, not during payroll.
MoreA stuck print spooler, a full temp folder, a service that quit. A workflow fires from the alert and closes the loop with no one touching it.
MoreTake over a screen, transfer a file, chat with the user, or reach a machine that has no agent yet, from a desk or a phone.
MoreThe mobile app is the point. Restart a service from the car, reset a password from the couch, reboot a server from the ballgame.
MoreBehavior that looks like encryption is detected in seconds. By a policy you set in advance, the process can be killed, the machine isolated from the network, or shut down.
MorePC and server image backup, plus Microsoft 365 mailboxes and OneDrive, sold and watched from the same place as everything else.
MorePulseway keeps a list of past alerts, searchable by title and sortable by priority or date. It does not collect the log lines behind those alerts, so there are no logs to search across machines and months. That is where we come in.
See MemoryBuying direct vs. buying through us
Pulseway is built for IT companies that manage hundreds of machines. Its own storefront reflects that. Ours is built for the company with fourteen computers and one person who is responsible for all of them.
Pulseway, direct
Terms as shown on pulseway.com, September 2026.
Pulseway, through Support Your Boxes
The wrapper · What we add
The question that costs a small business the most isn't "is it down?" The phone already answers that. It's "when did this start, and what else happened around then?" Pulseway can show you the alert that fired. It can't show you the log lines around it, or search six months of them across every machine. So every machine we manage also ships its operating-system logs to a central store we run, retained for a year and searchable. Dashboards built for the person who has to explain what happened are a flat add-on.
Ask it things like: how many times has this server rebooted since March · which workstation started failing backups first · what changed the night before the outage
How this is possible at this price: humans designed every check, threshold and runbook. What runs them at 3am, and reads the millions of log lines no small business could pay a person to read, is automation we built and watch. That's the whole trick. It's why the platform can be priced like software instead of like a staffed help desk.
FILESERVER01 · last 90 days · sample view
Illustrative: built from the kinds of events a real fileserver produces.
Questions people actually ask
No, and we say so up front. We provide the ticketing system that connects your users to your IT person, with a trail. We don't staff a help desk. If nobody in your company handles IT, we're not the right fit yet - and we'll tell you so on the quote form rather than after you've signed.
Response times to platform problems, by severity, set out in the service agreement you sign. We don't publish an uptime percentage; we'd rather show you the measured history than quote a number we don't control.
Planned maintenance happens Sundays between 4:00 and 4:30 a.m. Eastern. Services restart one at a time and each is back within a few minutes. Urgent fixes can happen outside that window.
No. Everything is delivered remotely, from Pittsburgh to anywhere in the US. If a job genuinely needs hands on hardware, we'll say so and help you find local hands - but we won't pretend to be them.
Your logs and dashboards run on cloud servers in Ashburn, Virginia. Nightly backups of those servers are kept on SYB-controlled equipment in Pittsburgh, Pennsylvania, with a second copy in SYB's Dropbox account. Pulseway's own service runs in Pulseway's cloud. We'll list every system that touches your data in the agreement, including the automation that reads it.
Any month. When you do, we export your full history in open formats, hand it over, and delete our copy with written confirmation 30 days after the export is delivered. Backup copies expire on their own within 60 days after that. We'd rather you stay because it works than because leaving is hard.
Because we don't sell a staffed help desk, and because the platform is tended by automation we built rather than by billable hours. You pay for the software and the people-designed process behind it. When you actually need a person's time, that's quoted separately and visibly.
By default, the telemetry and operating-system logs from every Pulseway-managed machine. That is the Minimal onboarding tier, and the setup fee covers it. Beyond that it is flexible: application logs from your servers, firewalls and network gear, line-of-business applications, cloud services. We scope those with you in conversation, because the configuration effort scales with what you want kept.
We're not a compliance consultancy and we don't certify anything. The platform does keep the records insurers and auditors commonly ask about: patch reports, a device inventory, twelve months of operating-system logs, alert history, and ticket history if you use the helpdesk. Your IT person can pull them from the logins we give you and hand them to whoever is asking. If you need a formal audit against a framework, we'll point you to a specialist.
It changes which devices we manage, not our price. We never install our agent on a card terminal, a point-of-sale system, or any computer that stores, processes or transmits card numbers. We also stay off anything connected to them or able to affect their security, such as a server that signs them in, a computer used to manage them, the router or firewall their traffic passes through, or a website that sends customers to your checkout. We never collect card data. If your office computers share a network with your payment systems, we check at review that the two are separated. If card terminals are the only things that handle card numbers, we can instead check that they use a PCI-listed point-to-point encryption solution, or their own phone or cellular line with no link to your office network. If none of that holds, the network needs separating first, by you or your network provider, or we're not the right fit. Those payment systems stay with your payment provider and whoever supports them. Before anything is signed we confirm with you, in writing, exactly which devices we manage. We're not a PCI assessor, and we don't take on your payment environment.