Discover & identify
Find reachable services and identify supported device interfaces. Move from an address and a port to a structured device record.
Service probing / Device detection
Network operations · In development
Know your network.
Know your network.
Control what
happens next.
Discover devices, verify services and manage connections through one repeatable workflow. NetToolSet brings fragmented network operations into a modular platform.
Working prototype · Selected devices validated in live tests
NTS / WORKFLOW EXPLORERILLUSTRATIVE DEMO
Service discoverySAMPLE RESULT
target192.0.2.10 / lab-router
serviceHTTPS · management interface
next stepdevice identification
Sample data and interface concept. No live scan is performed.
THE ENGINEERING FOUNDATION
Async PythonDevice adaptersShared database stateDistributed workers
01 / The problem
A network is a system.
Your tools should be, too.
Network teams often work across discovery scripts, vendor interfaces, tunnel clients and separate logs. Each handoff means more manual work and less confidence in the current state.
We are building NetToolSet to connect those steps: from an observed service to an identified device, a verified connection and a recorded result.
- 01Different devices. Different interfaces.
Firmware and authentication differences complicate even routine management tasks.
- 02A connected tunnel is only half the story.
The management path still needs to be checked at the application level.
- 03Standalone scripts lose the bigger picture.
Discovery, device operations and connection checks need a shared record of what happened.
02 / The platform
One foundation.
Three connected capabilities.
Built for network engineers who need repeatable operations across devices and connection types.
Connect & verify
Manage connection lifecycles and verify the path to a device. SSH, VPN and SOCKS5 components form the connection layer.
Connection adapters / Path checks
Operate & record
Use modular device APIs for supported settings and lifecycle operations, with shared database state and worker coordination.
Device APIs / Cluster control
Available behavior depends on the device, firmware and adapter. NetToolSet is in active development; it is not yet a generally available hosted service.
03 / How it works
From observation
to a verified outcome.
The engineering workflow is built around explicit results. Unsupported capabilities remain visible instead of being assumed.
01 / DISCOVER
Observe services
Probe an authorized network scope and capture reachable ports and service signals.
Output: service observations
02 / IDENTIFY
Resolve the device
Select a supported device adapter and its authentication or API implementation.
Output: device context
03 / VERIFY
Check the path
Use configured credentials and supported connections to test device management access.
Output: connection result
04 / OPERATE
Apply supported actions
Read settings or run supported device operations, then check the outcome and retain state.
Output: recorded outcome
04 / Who it is for
Built around real
network work.
Our initial focus is technical teams managing their own networks or infrastructure they are authorized to operate.
Understand the estate
Turn scattered service observations and device interfaces into a clearer operational picture.
Repeat the routine
Standardize supported checks and device operations across customer or internal environments.
Validate the connection
Test connection lifecycles and management paths in controlled labs before wider deployment.
05 / Where we are
An engineering prototype.
A clear next chapter.
We are turning an existing modular codebase into a product for network operations teams.
Current foundation
Core modules exist.
Validation is ongoing.
The codebase includes discovery, service probing, device adapters, connection modules and cluster coordination. Selected device workflows have been tested on real hardware.
- Async Python workers and shared database state
- Device and authentication adapter architecture
- Selected TP-Link settings and VPN workflows
- SSH, VPN and SOCKS5 connection components
Next / Product layer
A unified operator experience
Bring the workflow into a cohesive interface with controlled provisioning and clearer operational reporting.
Planned / Intelligence layer
Explain connection quality
Develop separate privacy, reputation and quality assessments using public data and our own measurements.
Planned / Cloud & AI
Scale the workflow, understand failures
Evaluate cloud-hosted workers, managed persistence and AI-assisted exception analysis as the product matures.
Roadmap items are planned development, not released features. Cloud deployment and AI analysis are not presented as current production capabilities.
06 / A few practical answers
Before we talk.
Clear expectations make for better technical conversations.
Can I start using NetToolSet today?
NetToolSet is a working engineering prototype in active development. There is no public self-service signup yet. Contact the founder to discuss your use case and whether an early technical evaluation is a fit.
Which devices are supported?
Current device work is focused on selected TP-Link firmware and authentication implementations. Coverage varies by model and firmware; it is not a claim of universal support. Additional adapters are part of ongoing development.
What is the intended business model?
We are developing NetToolSet as a B2B software product. The planned model combines team subscriptions with deployment options for controlled environments. Commercial plans and pricing have not been released.
Does the website scan my network?
No. This site introduces the project and shows an illustrative workflow. It does not run network probes, receive credentials or connect to devices. Product operations are intended for owned or explicitly authorized infrastructure.
Is NetToolSet already running on AWS?
AWS is being evaluated for the next cloud phase. The current prototype is not represented as an AWS-hosted production service. Compute, managed storage and observability are the initial infrastructure areas under consideration.
Build with us
Bring us a network problem
worth solving.
Have an infrastructure workflow that needs a better tool? We welcome conversations with network teams, potential early users and technical partners.