DeviceAutomate network device management
Every device, one current view
Your devices sync straight from the vendor into one live inventory. When one goes down, SmartTile 2.0 alerts and opens the ticket. Firmware, configurations, tunnels and logins stay covered too.
Is device upkeep consuming your team’s time?
Knowing a device exists isn’t the hard part. Keeping every vendor’s inventory, firmware, configurations and documentation current is.
Inventories go stale
Hand-built device lists are wrong within a month, and every new site adds more to keep up with.
Gear you can’t ping
Devices behind NAT can’t be pinged, so they’re easy to miss when you rely on ping alone.
Too many release feeds
Every vendor ships firmware on its own schedule, and nobody can watch them all and still patch on time.
Failures that stay quiet
A tunnel can drop while both firewalls stay green, and a stopped cloud server gets noticed by the customer first.
How DeviceAutomate works
Network device management starts with an inventory you can trust. Connect each vendor once, and SmartTile 2.0 keeps it current, so new sites don’t mean new manual work.
Step by step
- One credential per vendor cloud or controller, and you choose what to import.
- Each device lands in its company and location. Model, serial, firmware and MAC fill in automatically, without overwriting anything your team typed.
- Status comes from the vendor on every poll. Offline or missing counts as down.
- A confirmed outage alerts and opens a ticket, the same as a pinged device.
- If the vendor connection drops, devices turn grey (unknown), never a false green.
Three equal ways to monitor
Vendor API. What the vendor reports on each poll decides up or down.
SNMP. Polling for uptime, interface counters, identity and health, including gear with no API.
ICMP. Ping-based liveness, packet loss and latency, retried before a device is called down.
Whichever source applies, the alerts, tickets and reports work the same way. No inbound ports need to be opened on your side.
What runs on top of DeviceAutomate
Once your devices are in one live inventory, these automations keep them patched, backed up, watched and documented. Pick one to see the problem it solves and exactly how it runs.
Devices & Infrastructure
FirmwareAutomate
The problem
Every vendor ships firmware on its own schedule, and nobody can watch six release feeds and patch on time.
How it works
- Every 10 minutes, compares each device’s firmware with what the vendor offers.
- A newer build raises an advisory with the current and target versions and a 14-day SLA.
- Opens a ticket in your connected ITSM system and emails site contacts.
- Your team picks the maintenance window, and the ticket is updated when it opens.
- Verifies the running version afterward. A match closes the ticket; no match within 4 hours is flagged.
You stay in control. Patching is off by default. Without it, a technician applies the update in the window and SmartTile 2.0 verifies the result. A device that’s down at the window is never upgraded, and a window missed by more than 6 hours is never run late.
ConfigAutomate
The problem
The network configuration you need after a bad change is the one nobody saved.
How common vendors are backed up
| Vendor | How | When |
|---|---|---|
| Cisco IOS, ASA, Small Business, Dell, EdgeOS | SSH | Every 20 minutes, saved on change |
| Fortinet FortiGate | REST API or SSH | Every 20 minutes, saved on change |
| Cisco Secure Firewall (FMC) | REST API snapshot | Daily at the hour you pick, stored only when changed |
| Cisco Meraki | Dashboard API | On demand, versioned on change |
| pfSense | REST API, secrets masked | On demand, skipped if unchanged |
How it works
- Reads the configuration of each device with backups enabled, on the schedule its vendor supports.
- Compares it with the last saved copy. No change means nothing new is stored.
- A change saves a new version with a line-by-line diff, plus who made it and when.
- When you switch it on, one ticket opens with the exact lines added and removed, the author and the time.
- Three failed backup runs in a row send one alert email, with one more on recovery.
No surprise ticket floods. Before auto-ticketing starts, a Preflight shows what the last 30 days would have sent, and a per-hour cap limits volume after that.
VPNAutomate
The problem
A site-to-site tunnel can drop while both firewalls stay green.
How it works
- Lists every tunnel: Meraki AutoVPN, Meraki third-party IPsec peers and SmartTile-provisioned tunnels.
- Polls every 60 seconds. You choose which tunnels to watch and how long counts as down (3 minutes by default).
- Past that window, opens one ticket with both sites, the peer and the drop time, and emails your chosen contacts.
- When the tunnel recovers, a note is added and the ticket closes after 10 minutes of stability.
Only what you choose. Watching is off until you switch it on per tunnel, so nothing alerts that you didn’t ask for.
AccessAutomate
The problem
Who signed in to the firewall at 3 a.m.? Usually nobody knows until the audit.
How it works
- Every 5 minutes, reads admin activity from Cisco FMC, the Meraki dashboard and UniFi controllers.
- Checks each login against your list of authorized admins.
- An unknown admin or 3 or more failed logins opens a ticket and emails your chosen contacts.
- Every event and verdict exports to CSV for your audit evidence.
A ticket either way. If you haven’t chosen any contacts, no email goes out, but the ticket still opens.
CloudAutomate
The problem
Cloud servers sit outside the NOC’s view. A stopped server gets noticed by the customer, not by monitoring.
How it works
- Connects read-only with a least-privilege policy. Every region is scanned unless you specify otherwise.
- AWS EC2, RDS and WorkSpaces, Azure virtual machines (beta) and DigitalOcean droplets become monitored devices.
- Status every 60 seconds. Stopped or missing for two polls counts as down, with the same alert and ticket.
- Metrics every 5 minutes feed health thresholds, and spend and security findings refresh hourly.
Nothing to install. There’s no agent, and nothing is written to your cloud account. Opening a provider support case is off by default.
EndpointAutomate
The problem
“The phones are down” starts an argument about whose problem it is, because handsets aren’t on the board.
How it works
- Connect Grandstream GDMS with an API client ID and secret. A built-in test confirms access and counts handsets.
- Polled every 60 seconds. Each online handset becomes a VoIP phone device at the right location.
- Down is confirmed over 3 polls and restored over 2, with 7-day uptime history per handset.
- Many handsets dropping together at one site is one site event, not dozens of alerts.
- Handsets can be rebooted from SmartTile 2.0, once a day at most and never during a call.
Monitoring and history in this phase. Handset tickets and emails are off by default.
Network Diagrams
The problem
A site diagram drawn by hand is out of date the day after the next install.
How it works
- Drawn from each location’s device records (carrier, gateway, firewall, switches and access points) and colored by live status.
- Every device is labeled with vendor, model, circuit ID, IP, latency and loss.
- Dual-WAN gear appears as one box listing every WAN IP with its carrier.
- Each time a diagram opens or refreshes, the file is saved to the location’s Documents, one current copy per location.
- With IT Glue connected, the diagram is pushed to the mapped organization. An unchanged diagram is skipped.
Your call. Auto-save has its own on/off switch and is on by default. PNG and PDF downloads are available where your plan includes them.
What SmartTile 2.0 delivers
Less time on the work after the alert, with no extra headcount.
48%
faster resolution
3.5×
more ticket capacity, with the same team
SmartTile 2.0 platform results in early use across 6 production environments. Not a service-level commitment.
DeviceAutomate integrations
Connect the firewalls, wireless, cameras, cloud platforms and phones you already run.
Firewalls & gateways
Switches & Wi-Fi
Cameras & access
Cloud & RMM
Phones
Monitoring protocols
One platform, three engines
Each engine works on its own. Together, they carry an outage from the first alert to the verified restoration.
ServiceAutomate
Tickets that arrive ready to work
One ticket per site outage in the ITSM platform you already use, with site, circuit and device details filled in.
Explore ServiceAutomateCarrierAutomate
No more time on hold
Carrier repair tickets opened and chased by API or by Joey, our AI voice agent, with a 24/7/365 U.S. NOC behind them.
Explore CarrierAutomateDeviceAutomate FAQ
What is DeviceAutomate?
DeviceAutomate is the SmartTile 2.0 engine that keeps your network and security devices in one live inventory. It pulls identity and status straight from each vendor, opens a ticket when a device is confirmed down, and adds automations for firmware, configuration backups, VPN tunnels, admin access, cloud servers, handsets and site diagrams.
What if a device doesn’t have an API?
SmartTile 2.0 can still watch it. If a device speaks SNMP or responds to ping, it can be monitored without a dedicated integration. Where a device can’t be pinged, the vendor’s own API is the monitoring source, with the same alerts, tickets and reports.
Do we need to open inbound ports?
No. API connections use outbound HTTPS from SmartTile 2.0, and none of the integrations need an inbound port opened on your side.
Will SmartTile 2.0 upgrade firmware on its own?
Not unless you turn that on. Patching is off by default. Otherwise, a technician applies the update during the window you choose and SmartTile 2.0 verifies the running version afterward. A device that’s down at the window is never upgraded.
What happens if SmartTile 2.0 loses its connection to a vendor?
That vendor’s devices turn grey and show as unknown, never a false green, so your team can see that the data has stopped.
Which vendors does DeviceAutomate support?
Inventory and status sync covers Cisco Meraki, Ubiquiti UniFi, Fortinet FortiGate, Cisco Secure Firewall, Aruba Central, Aruba Instant On, Verkada and pfSense. The wider catalog adds firewalls such as Palo Alto Networks, SonicWall, Check Point, Juniper SRX, Sophos, WatchGuard and OPNsense, plus cloud platforms, handsets and standard monitoring protocols.
Ready to see every device in one view?
See DeviceAutomate running on your stack.