// SYS.ONLINE — 2501.AI COMMAND INTERFACE
[STATUS: ACTIVE]

TECHNOLOGY //

Operating systems

Linux fleet automation over SSH

2501 investigates and fixes everyday Linux problems such as full disks, failed services and CPU spikes over SSH, as an account you create, within limits you set.

Repetitive Linux incidents on different hosts, a full partition, a failed service and a CPU spike, are each diagnosed and fixed by 2501 over SSH as a dedicated user rather than root

ServiceNow or another ITSM

Operating systems

Investigate only, with a person, or on its own

On-prem, cloud or hybrid

TECHNOLOGY_BRIEFING

// WHAT 2501 DOES

2501 works on Linux hosts over SSH, as an account you create for it, with only the permissions you grant. It diagnoses and fixes day-to-day failures within limits you set: a full partition, a service that will not start, a CPU spike.

Most Linux incidents are not hard. They are repetitive: the same checks, the same known fix, on a different host at a different hour, followed by the same write-up.

What 2501 does

Linux specialties take these requests from your ticketing system. Disk Manager investigates disk space and carries out safe cleanup and log rotation, and Disk Manager LVM does the same on LVM volumes. Services Manager Linux troubleshoots services running under systemd, Docker and similar runtimes, while SysOps, the baseline specialty, covers general system operations. Hosts can be reached directly, through a bastion, or from inside a network that accepts no inbound connection. Network discovery can propose the hosts on the subnets you choose for you to confirm, and runbooks you upload become rules each agent receives when they apply. What it changed, and why, is always reported.

Deployment view: a ticket reaches 2501, running on-prem, in the cloud or hybrid, which checks every action against your rules before working on your Linux hosts over SSH, and writes the outcome back to the ticket

You stay in control

  • You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
  • The Linux account is the hard limit: a dedicated user, not root, allowed only the privileged commands its job needs.
  • Your rules decide which hosts and services are in scope, and destructive commands can be blacklisted outright.
  • On-prem, cloud or hybrid: 2501 runs wherever you do, including fully air-gapped on-prem networks.

Frequently asked

Does the agent need root? No. It runs as a dedicated user granted only the specific commands it needs, such as restarting named services.

Can it reach hosts behind a bastion? Yes, and hosts on isolated networks that accept no inbound connection at all.

Do we have to register every host by hand? No. Discovery can propose them, or you can import an existing inventory.

Related

> READY_TO_DEPLOY

SEE IT ON YOUR OWN INFRASTRUCTURE

Book a technical demo and walk through your own environment with the 2501 team.

REQUEST DEMO

CONTACT SALES