Skip to main content

​
General

2501 runs autonomous AI agents on your infrastructure. You point it at machines, give it a few rules about how your environment works, and it handles tickets from your ITSM — investigating, fixing, and reporting back in the ticket itself.
Yes. ServiceNow is the default gateway and what most deployments run, but custom-built gateways are available for other ticketing systems — contact your account team. You can also drive 2501 from the CLI or the Command Center UI directly.
Yes — a built-in free tier caps your tenant at 50 lifetime tasks and 10 hosts (gateways are unlimited). Once you apply a license, those caps are replaced by your contract’s. See Licensing.

​
Agents and safety

Three layers, used together:
  1. Permissions — give agents the least-privileged credentials that still let them work.
  2. Blacklists — programmatic blocks for specific command patterns, always on.
  3. Read-Only Agents — pin a specialty to investigate-only so the agent literally cannot alter the system.
Investigate is read-only — the agent diagnoses and reports without changing anything. Remediate is the default; the agent can act. Set per ticket with @2501:investigate or pin a whole specialty to investigate-only. See Read-Only Agents.
A Specialty shapes how the agent thinks about a domain — vocabulary, priorities, approach. An Operational Rule tells it what is true in your environment and what that implies. Specialty: “Kubernetes Operator”. Rule: “On this cluster, rollbacks go through helm rollback, never re-applying manifests.”Rules outrank specialties in conflicts. See Prompting an Operational Rule.
Hard limit, set after observing thousands of tickets. Most jobs need 1–3 tasks; headroom for 2 more covers multi-host coordination or deep investigation. If 5 tasks aren’t enough, the agent is going down a wrong path — better to fail and let a human take over. See Agentic Flow.

​
Models and providers

Native: OpenAI, Anthropic, Mistral, DeepSeek, Cohere, OpenRouter, TogetherAI. Compatible: any OpenAI- or Anthropic-shaped API via openai-compatible / anthropic-compatible, and Azure OpenAI (including APIM). Self-hosted endpoints (vLLM, Ollama) work through the compatible types. See Providers.
Yes. Each agent picks its main and secondary engine from the tenant catalog. The tenant has its own defaults for gateway routing and the AI Assistant. See Engine & Agents.
The main engine does the work (commands, file edits). The secondary engine plans, watches, and judges every command for compliance and read-only enforcement. Separating execution from oversight improves both accuracy and safety. See Engine & Agents.

​
Deployment

Docker Swarm is the default — 2501 infra deploy manages the full lifecycle. Kubernetes (any distribution: vanilla, OpenShift, k3s, EKS, etc.) is generate-only: the CLI renders manifests you apply with kubectl or your distribution’s equivalent, so GitOps tooling stays in charge. See Kubernetes.
Run an interactive 2501 infra deploy. It lists published releases newest-first, self-updates its own binary to match the version you pick, and then deploys. No separate update command. See Troubleshooting → Upgrading.
LLM API keys live in /etc/2501/env.engine. Per-host credentials (SSH, WinRM, gMSA, vault paths) live in Command Center → Credentials, encrypted at rest. Agents only access them programmatically — values are never displayed in the UI after creation. See Credentials.

​
Knowledge and rules

PDF, DOCX, CSV, and Markdown. Max 200 MB per file. PDFs with diagrams need a multimodal model on the tenant to capture the visual content. See Knowledge.
Manual rules always win. The auto-extracted rule is replaced when you re-upload the same document, but your hand-written rules are untouched. See Working with Knowledge.
Each task’s detail page in Command Center shows a matching trace — which operational rules were applied, which were skipped, and why each skip happened. Use it to debug rules that are too broad, too narrow, or mistagged.