Know your fleet.
Client health, inventory, services, logs and files. Move from a fleet-wide view to the machine that needs your attention.
WindowsLinuxmacOS
Explore fleet management v0.1.2 is hereMeet the latest stable release Your infrastructure.
Daily service check Completed
Infrastructure, on your terms
Your infrastructure.
Under your control.
One home for your fleet, scripts and workflows. Run NetRatel on your infrastructure. Bring AI into the work when you choose.
Open source · Self-hosted · AI optional
netratel / operationsExample workspace
One place. Your entire fleet.
Demo tenant / ProductionConnected clients
24 ↗ onlineActive alerts
02Completed jobs
18 today| Client | Platform | Status | Health |
|---|---|---|---|
| web-01 | Linux x64 | Connected | Healthy |
| workstation-08 | Windows x64 | Connected | Healthy |
| db-02 | Linux x64 | Connected | Disk alert |
Make the routine repeatable.
Demo run / web-01Collect service inventoryCompleted
Run approved health-check scriptCompleted
Capture the resultCompleted
$ ./service-health-check.sh
Services checked. Output saved with this run.
Services checked. Output saved with this run.
Your operator. Your assistant.
Demo conversation● Tenant-scoped accessSelf-hosted. Fully yours.
Illustrative workflow with sample data · Explore the operator guides ↗
One connected workspaceWindows x64 clientsLinux x64 clientsmacOS Apple Silicon.NET + Akka.NET
The platform
Less switching.
More doing.
See what is happening, run the work and follow the result. Keep the day-to-day in one operator workspace.
Make work repeatable.
Build a script library. Combine steps into jobs, collect the inputs and set a schedule. Every run keeps its own result.
Reusable scripts and parametersManual runs and schedulesStep-by-step execution output
Build your first job Get closer to the issue.
Open a remote terminal, inspect a log or run a targeted check. Work from the browser or bring your own command-line tools.
$ netratel doctor
✓ profile and connection checks
$ netratel clients-v2 --help
Explore operator tools ✓ profile and connection checks
$ netratel clients-v2 --help
Monitoring & workflows
An alert should lead somewhere useful.
Watch CPU, disks and services. Route an alert through a reviewed flow to the people and tools that can act on it.
Create a RatelDesk ticket, send a Slack or Discord notification, or bring Netclaw into an investigation—with the tenant and context attached.
See how alert flows workFrom signal to next step
A monitoring rule firesClient · Tenant · Alert context
Published flow
Netclaw investigation · Optional
RatelDeskCreate a ticket
SlackNotify the team
DiscordSend a notification
Choose the destinations. Preview the mapping. Publish when it is ready.
Connected by design
Your tools.
Your access rules.
Connect assistants through HTTP MCP or a local stdio process. Use Netclaw for tenant conversations and investigations. Keep credentials, permissions and approvals under your control.
Find your integration pathStart here
A clear path
to your first run.
Start with a server. Add a client. Build from there.
01 / SERVERLinux x64 · Docker Compose
Start with the stable release.
The Compose bundle includes the server stack and pinned image digests. Download it, verify the checksum, then follow the setup guide.
curl -fLO https://github.com/BostonTechnologies/netratel/releases/download/v0.1.2/netratel-compose-0.1.2.tar.gzThe quickstart covers verification, configuration, signing keys and your first administrator.
Follow the deployment guide02 / CLIENTWindows · Linux · macOS
Connect your first computer.
Set the public site and gateway addresses. Import the release client pack, then generate a protected installer for the right tenant.
1. Configure Site URL + Gateway URL
2. Import the release client pack
3. Clients → Artifacts → Generate script
2. Import the release client pack
3. Clients → Artifacts → Generate script
The client joins your tenant and appears in the fleet after enrolment.
Connect your first client03 / ASSISTANTScoped tools · Explicit access
Give your assistant a defined role.
Choose remote HTTP MCP or a local stdio connection. Configure a separate credential for each consumer and review its tenant access.
HTTP Assistant → /mcp → NetRatel API
stdio Assistant → local process → NetRatel API
stdio Assistant → local process → NetRatel API
Start with authentication status and a permitted read before enabling actions.
Choose an MCP connectionDocumentation that gets to the point
Find the next thing you need.
01 / DEPLOY
Run it your way.
Compose, HTTPS, external PostgreSQL and reverse proxies. Choose the setup that fits your environment.
Deployment scenarios 02 / OPERATETurn a task into a routine.
Manage clients, write scripts and schedule jobs. Follow output from the first step to the final result.
Operator guides 03 / UNDERSTANDSee how it fits together.
Understand the architecture, identity model and integration boundaries before extending your setup.
Architecture & referenceBuilt by Boston Technologies
Own the way you operate.
Deploy NetRatel. Connect your first client. Make the next task easier.
