help_center Frequently Asked Questions

Got questions?
We've got answers.

Everything you need to know about NTS - pricing, remote support, security, setup, and more.

search
campaign Our Take

How do NTS's features compare to other RMMs?

Honestly, we don't know, and we're not chasing anyone's feature list. Because you don't need another spec sheet, you need your actual problems fixed. We looked at what SME and SMME IT service providers deal with daily, found the patterns, and built for those specifically: tools that cost too much, platforms bloated with features nobody uses, and no affordable way to pass costs on to clients.

That doesn't mean we're light on features. But we are specific. That's still the only thing driving the roadmap today. Nothing has changed.

flag General & Company

Brainwave Software Labs, a South African development house with close to 20 years of experience. NTS is based on direct input from their sister company - a South African MSP that's been operating for the same 20 years.

Proudly South African. We are Saffas building a ZA-first platform with data/servers located in South Africa. We're not an international company staging in ZA - we're South Africans building for South Africa first, with plans to expand internationally in due course.

To solve four core problems MSPs face:

  • Tools cost too much - RMM + remote support licenses
  • Platforms are too complicated - built for enterprise teams with dedicated admins
  • Historical visibility is poor - "how was this machine doing on Saturday?"
  • Pricing punishes growth - per-technician seats, annual increases

Honestly, we don't know, and we're not chasing anyone's feature list. Because you don't need another spec sheet, you need your actual problems fixed. We looked at what SME and SMME IT service providers deal with daily, found the patterns, and built for those specifically: tools that cost too much, platforms bloated with features nobody uses, and no affordable way to pass costs on to clients.

That doesn't mean we're light on features. But we are specific. That's still the only thing driving the roadmap today. Nothing has changed.

payments Pricing & Billing

R5.75 per endpoint per month inc VAT (R5 ex VAT). That's less than 20 cents per device per day. Remote Support is included at this price.

100 endpoints minimum per Agency, which equals R575/month inc VAT. Below that threshold you still pay R575. Above it, every additional endpoint adds exactly R5.75. Start with your own office and grow from there - there's no rush.

No. Unlimited technicians and unlimited concurrent remote support connections are included. You pay per endpoint, not per technician.

Any device you monitor for stats consumes one endpoint license. This includes:

  • Workstations & Laptops (Windows)
  • Servers (Windows)
  • Network Devices (routers, switches, firewalls)
  • CCTV Cameras & VoIP Phones
  • Cloud Instances
  • Anything with an IP address

ZAR native pricing. No exchange rate risk, no international payment headaches. What you see is what you pay, every month.

Yes. NTS is designed so you can transfer 100% of costs to clients and build a profit margin on top. We just need R5.75/endpoint - how you price it for your clients is entirely up to you.

No contracts. Cancel any time. We earn your business every month, or we don't and you move on.

None. Self-service onboarding. No consultants, no setup invoice, no "onboarding fee".

Not currently, but we are open to having this conversation if it comes up. Contact us to discuss high-volume pricing.

Clear communication in advance - no stealth increases. Pricing is subject to change should markets force it, but we'll always tell you before it happens.

deployed_code Features & Capabilities
  • CPU, RAM, disk, GPU, network interfaces, and running processes
  • 15-second collection intervals
  • Trend detection and automatic anomaly notifications
  • Full 10-day granular rewind per device
  • 90-day history (10 days full resolution, 90 days condensed daily averages)

We record running services but are not actively displaying this in the current version. We do record the top 10 processes with their average CPU usage across 3 minutes - you'll always see the top 10 most active processes.

Yes. The agent records startup applications on each workstation, allowing you to see what software is configured to launch when a device boots. This helps identify unauthorized startup programs, troubleshoot slow boot times, and maintain standard configurations across your fleet.

Live topology mapping, continuous ping monitoring, wireless zone analysis, switch health diagnostics, and historical uptime/latency data for any device with an IP. You explicitly add devices by IP - no auto-discovery, no surprise billing.

You can monitor any IP-addressable device: routers, switches, firewalls, CCTV cameras, VoIP phones, wireless access points, and cloud instances. Network nodes are added explicitly by IP address - no auto-discovery, no surprise billing. Each network node consumes one endpoint license and provides uptime, latency, and historical performance data.

Yes. You can configure monitoring thresholds at the agency level, which determine when the system generates notifications for CPU, RAM, disk, and network metrics. Thresholds set alert levels and time windows for averaging data. These apply across your agency but can be adjusted as your needs change.

We don't slap an AI badge on features just to look cool. We use AI where it's genuinely useful - machine learning for trend detection, AI report generation for site summaries, and pattern recognition. But we also rely on strict engineering rulesets and trend discoveries physically designed by our engineers. AI is integrated where it provides real value, not as a marketing gimmick. Going forward, AI will be more tightly integrated into the platform where it would actually be useful for technicians and MSPs.

Planned: Extended uptime monitoring - website uptime, domain expiry alerts, SSL certificate monitoring, mail server health checks. Automated scheduled site health reports delivered by email.

support_agent Remote Support

Yes. Remote support is built on UltraVNC as the underlying session engine. We did not simply bundle a copy and call it done. NTS implements a purpose-built remote control process on top of that technology stack: agent-initiated sessions, one-time codes, and a secure relay we built and operate in the NTS cloud. The robust UltraVNC engine makes it possible. The implementation, the relay infrastructure, and the NTS platform integration are ours. From your technician's perspective the experience is seamless: a one-time session code, full keyboard, mouse, clipboard and file transfer, no separate account, no separate install.

The remote support is agent-licensed, not per-technician, which is why it's included at R5.75/endpoint - no separate AnyDesk or TeamViewer license required.

The remote support client is built into the agent, so any workstation running the NTS agent can be remotely supported. This is why we don't limit technicians or concurrent connections. Our implementation cannot be used on random PCs not running NTS - it only works on managed endpoints with the agent installed.

Yes - with an important distinction. Unattended mode does not hide anything from the user. The same Windows remote access prompt appears on screen, the same one-time code is generated. The only difference is that instead of the user reading the code to the technician, the agent relays it back to the control panel automatically so the technician can connect without needing the user present.

If someone is sitting at the machine, they will see exactly what is happening. This is by design - we are not comfortable with truly invisible access to client workstations and we do not implement it. Unattended mode is intended for workstations where no user is present: after-hours maintenance, servers, or machines that need attention while the user is away.

You should engage at least one user-initiated remote control session before unattended access will work. The initial user control request configures and installs all the necessary components required for later unattended access. Once one standard session has completed successfully, unattended mode will function on that workstation.

Yes. Every unattended session is logged with full attribution: technician, station, timestamp, and result. Only authorised admin users can queue unattended tasks. The Windows remote access prompt is always visible on the endpoint - the only difference from standard mode is the code travels via the CP rather than being read out by the user. This log cannot be altered or deleted.

engineering Remote Management & Automation

One-Run Tasks (ORT) are on-demand actions you queue from the CP and the agent executes on next check-in:

  • Remote CMD - open a persistent remote command prompt session, run multiple commands
  • Start Application - launch any app with optional arguments, command logged (not output)
  • Send Message - pop a message on the user's screen
  • Clear Temp Files - clear Windows temp folders
  • Reboot - restart the workstation
  • Remote Support - trigger the remote access flow (standard or unattended)

Every ORT is admin-gated and permanently logged with technician, station, and timestamp.

Automation Tasks run continuously and respond to conditions automatically:

  • Service Monitor - watch a Windows service, fire a configurable recovery action if it stops
  • Process Monitor - watch for a process running or not running, trigger recovery
  • Network Node Monitor - monitor any IP device (router, switch, camera, VoIP) for uptime and latency
  • Scheduled Commands - run a command on a recurring day-of-week schedule with configurable time windows

Triggers and executions are plotted on a time-scale chart so you can see the pattern of events alongside your workstation metrics.

Yes. Site ORT lets you select a task and broadcast it to all chosen stations on a site simultaneously. One action queued, every machine receives it on next check-in. Useful for site-wide reboots, pushing a message, clearing temp files across all endpoints, or any other task you'd otherwise have to queue one by one.

Yes. Every ORT and automation action is permanently logged: which technician queued it, which station it ran on, when it was queued, and the result. Only admin-level users can queue management actions. This log cannot be altered or deleted.

rocket_launch Trial & Setup

14 days free, full platform access, up to 100 endpoints, no credit card required. Not a limited demo - exactly what you'd pay R575/month for after the trial. No hidden features behind paywalls.

If you continue, your first invoice is R575/month inc VAT. No hidden step-up, no forced annual commitment. If you don't continue, walk away with zero friction - no auto-billing, no "gotcha" renewals.

5-minute setup:

  1. Create your Agency (instant provisioning)
  2. Create a Site (client office, your office, branch)
  3. Download & install the Agent (same binary for every site)
  4. Metrics start flowing immediately at 15-second intervals
  5. Open the Control Panel and watch live metrics appear

During installation you enter three things:

  • Your Agency identifier (3-5 letter code of your choosing)
  • Your Site code (specific to this location)
  • A Security Key

Same installer binary for every site - no site-specific build needed.

Windows-native and lightweight. No Java, no Electron, no 400MB RAM footprint. Runs quietly in the background without impacting your users.

No! The NTS agent dials out from the device - the system never dials in. This means no ports forwarded, no specialist VPNs, no network configuration required. Each agent dials out and adds its stats to the cloud. You access stats in the cloud, not on the actual agents.

settings Technical Details

One lightweight Agent installed on each device dials out to the Secure NTS Cloud, which feeds into your dashboard and tools. No on-premises server required, ever.

10 days of full-resolution data at 15-second intervals. After 10 days, data is rolled into daily averages (24 data points per metric, per day) for 90 days of condensed historical rewind.

The agent queues metrics locally and sends them as a pool every 60 seconds. If a cycle is missed due to connectivity, the pool grows and metrics are pushed when internet is restored. Note: this buffer is not persisted across agent restarts or workstation reboots.

Technically yes, but we have disabled this in the current version. All devices currently collect at 15-second intervals. We may re-introduce configurable intervals in a future update.

Devices are grouped by "site". For a large business, we recommend creating a site per department. Networked nodes can be filtered and grouped via device type, status, etc.

When a laptop enters sleep mode it stops sending stats. Stats resume automatically when the device wakes.

The agent checks in every 30 seconds. During each check-in, it sends collected metrics and retrieves any pending tasks (One-Run Tasks or automation triggers). This 30-second interval ensures near real-time responsiveness while keeping bandwidth usage low - approximately 30-70 MB per workstation per month.

Not currently, and that's a deliberate choice. Running as a background Windows Service would strip out the features that depend on an active desktop session, including Remote Support, on-screen custom messages, and interactive prompts. Those features are core to what makes NTS useful day to day, so we've kept the agent tied to a real user session rather than shipping a version with reduced capability by default.

If you're monitoring a VPS or physical server that you only ever access over RDP, see the next question for how to keep the agent running continuously without needing a Windows Service.

We may release a dedicated, limited-functionality "service mode" agent in future if platform clients need it for unattended servers, at the cost of losing Remote Support and other interactive features on that specific machine.

The agent keeps running as long as the Windows session it's installed under stays logged in, even while disconnected. Follow these rules for reliable, always-on monitoring on a VPS or physical server accessed via RDP:

  • Disconnect, don't log off. Close the RDP window or use the X button to end your session. Never click "Sign out" or "Log off" on the account running NTS, that ends the session and stops the agent with it.
  • One agent per machine, not per user. NTS runs as a singleton per OS install. Whichever user session starts it first "wins" for that machine. It won't start a second copy under a different profile if it's already running, so pick one dedicated profile per server and stick to it.
  • Watch for forced restarts. Scheduled reboots (Windows Update, third-party maintenance tasks, or a habit of restarting the server) will end the session and the agent along with it. Check Task Scheduler and Windows Update settings on the server if you notice regular gaps in monitoring data.
  • Session Time Limits are rarely the cause. If a server keeps disconnecting that profile, check Group Policy idle/disconnect session limits first, but in practice we've found forced restarts to be the far more common culprit.

Run gpresult /h report.html on the server first to see exactly which policy and which GPO is winning, rather than guessing. A few rules that trip people up:

  • Computer Configuration always beats User Configuration. If a Session Time Limits policy is set under both, the Computer Configuration value wins on that machine for every session, regardless of which user is logged in. Setting a longer limit on the user or account won't help if a shorter one is enforced at the computer level.
  • To exempt one account (e.g. the profile running NTS) while keeping limits for everyone else: set the Computer Configuration policy back to Not Configured, then apply the limit at User Configuration instead, scoped so it excludes your monitoring account.
    • Domain-joined: use Security Filtering on the GPO, apply it to a group containing your regular users only.
    • Workgroup/standalone server: use Local Group Policy's "Non-Administrators" object (mmc.exe → Group Policy Object Editor → Browse → Users tab) and leave the account running NTS untouched.
  • RD Session Host Collection settings can also override individual account settings if "Override user settings" is checked in the collection's Session properties, but a configured GPO (Computer or User) still overrides the collection setting on top of that.
shield Security & Privacy

All data is stored in South Africa. We are a ZA-first platform with South African data infrastructure.

Yes, by design - everything is co-located in South Africa.

Data is transmitted through secure SSL connections to the NTS cloud. Metric data for an agency is not encrypted at database level, but user account credentials and authentication data are. Only authorised users of an agency can see their agency metric data when logged in.

Yes. You can create multiple users for your agency and assign different access levels. Users can be restricted to specific sites, and not all users have permission to perform administrative actions like queuing remote management tasks. This allows you to give junior technicians view-only access or limit them to specific clients while senior staff have full control.

We currently store no user-specific data, purely metrics as collected through the Windows WMI interfaces.

Every remote support session routes through a secure relay we built and host in the NTS cloud. No peer-to-peer, no direct exposure. In standard mode the user initiates the session and reads the one-time code to the technician. In unattended mode the technician triggers it from the CP and the code is relayed back automatically - but the Windows remote access prompt is always visible on the endpoint. Full keyboard, mouse, clipboard and file transfer run over this encrypted relay. Every session is logged with technician attribution, timestamp, and station.

business_center Business & Operations

Yes! Both the NTS dashboard and NTS agent can be branded with your agency name and logo. It will still be an "NTS" product under the hood, but your agency name and logo is prominently displayed.

Yes. You can grant clients "view only" access to specific sites. This allows them to log in and see their own device health, notifications, and historical data without being able to make changes or perform management actions. This transparency helps build trust and keeps clients informed about their infrastructure.

We aim for 100% uptime, but technology happens. For support queries we operate on a 1 business day model, weekdays. We mostly answer queries within minutes or hours depending on staff availability.

No formal program, but by using NTS and passing costs through to clients, you are in effect acting as a reseller. We do not offer a program where you can sell NTS to other MSPs.

You can set where email notifications are sent via an email address. It's entirely up to you. Most MSPs send this to their ticketing systems and handle client communication from there as required.

We are actively working on getting this live. We feel it's a crucial part of being able to generate a monthly report to share with your clients. Contact us to tell us exactly what you need.

We have comprehensive and extensive metrics available in the CP through charting, historical time-based data, along with a comprehensive notification system (CP and/or email delivery). Full user audit log, critical and warning notifications (CP or email). We do have an AI-generated summary feature that provides a "what's happening on this site" overview, but this is designed for internal technician use rather than client-facing reporting. We do not currently have automated monthly report generation or client-facing report delivery. This is something we think might be a good feature to add. Let us know what you want and how you want it so that we can make sure we are aligned with what our users need, not what we think we can build.

No. No existing API is available for this. If it's requested and becomes popular, it will be added to the roadmap.

No. No existing API is available for this. If it's requested and becomes popular, it will be added to the roadmap.

speed Performance & Scalability

Because NTS is distributed, you never feel any performance impact. You're not hosting the NTS system on-prem. Your statistics are stored on scalable, modern VPS servers managed to account for scale as required. For you as the client, 1 endpoint = 10,000 endpoints. For very large sites, we recommend splitting into multiple smaller sites for easier management.

  • Workstations & Servers: 30-70 MB per device, per month
  • Network Nodes: 10-20 MB per device, per month
move_down Migration & Onboarding

We don't have a migration roadmap, as NTS is just too different from other existing platforms. The good news is the setup is so fast that starting fresh is often simpler than a migration would be.

There is no reason why this should not be possible.

No, not at this time. Our platform is just too different from what is currently out there to support a meaningful import.

devices Specific Use Cases

Not currently. If this is a popular request, we'll work on adding this.

Yes.

We do not support mobile devices for running agents. NTS is currently Windows-based.