How a security robot works
A security robot can work in the real world or in the cloud. Its form defines how it operates: it can be a physical robot, like a guard that rounds and patrols, ground-based, humanoid or not, or flying like a drone, or a virtual robot, which operates on the agentic intranet or on a cloud with internet and watches the network, the nodes and the other agents when that function is available. The same platform supports the forms and each one works where it performs best. It connects to the cloud to add what it does not bring from the factory. Depending on its manufacturer, you can configure it to be compatible with the platform, update it or start with one of the brand, and the panorama stays open: any robot that meets the schema works.
One requirement is that the robot has internet access and that its manufacturer allows connecting it to external networks: with that it can use the tools, talk with the agent or join the agents that the user has in their cloud and the ones created on natuleadan.app. The connection uses API key or OAuth 2.1 depending on what the tool or the manufacturer requires, and the tools that require it are verified on demand when needed and may be subject to other terms and conditions.
What the robot can do
There is no closed list: what it can do depends on the form, the manufacturer and what it already has installed. A robot that is not native to security can become native with the application, or stay as it is depending on what you decide.
- Rounds: perimeter route per point and shift in the physical form, if the robot has it or adopts it.
- Patrolling: surveillance of areas and routes by schedule in the physical form, if the robot has it or adopts it.
- Digital surveillance: network, VPS, nodes and clouds in the virtual form, if the robot has it or adopts it.
- Agent control: accompanies the surveillance of the other agents when that function is available, if the robot has it or adopts it.
- Alerts: notice of intrusion, anomaly or deviation with context, if the robot has it or adopts it.
- Log: evidence of every round, event or finding, if the robot has it or adopts it.
How the robot works
Here is the difference with the agents: the agents operate in the cloud and the robot works wherever it falls to it, in the real world or in the cloud itself when its form is virtual. When it is online, it is empowered: it can talk with agents that the user creates or use the tools directly in its robot-to-tool relationship, and chain a complete process, from the order to the execution and the closure. It is not limited to a single task or a single agent: it adapts to what is enabled for it. Every action stays in the account’s usage log and, if it loses the connection, it keeps its last safe state until it returns.
How to use the robot
Once connected to the platform, the robot is used according to its form and its role: a physical one rounds and patrols, a virtual one watches the network, the nodes and the agents; and both can escalate their task when the case requires it. A professional can operate it within the shift, or a person who integrates it into their own work, without going through a specialist. You can change the modality, pause tasks or remove a point from the program without losing its history, and every adjustment is recorded with its date. The robot never orders an exit or brakes another agent on its own: it proposes and escalates when needed.
How to be safe with your robot
Safety is shared between what you define and what the manufacturer offers. These fronts are worth reviewing before putting a robot to operate.
- Access: who can operate it, with which role and with which permission; rotation of API keys or OAuth.
- Approvals: sensitive actions ask for approval per operation, as in API Connect.
- Data: what leaves the robot toward the cloud, how it is encrypted, how long it is kept and with what consent.
- Physical safety: emergency stop, speed and force limits, sensors and restricted zones in the physical form, according to the manufacturer.
- Network and updates: encrypted connection, signed updates and a safe behavior if it loses the connection.
- Log and audit: log of every action and notices upon an anomalous behavior.
Start now
You can configure your robot to be compatible with natuleadan.app, update it or buy the brand’s one to start with one ready. If you use the application, create your account and apply your security robot to the pilot. The robot is paid separately and its connection, together with the use of the tools, is covered by the tokens of your monthly plan or your prepaid. The detail lives in pricing.