Can I import scripts I already have?

Yes. Paste in, upload as a file, or pull from a Git URL (post-GA).

Are scripts sandboxed?

Scripts run with agent privileges (SYSTEM / root). They are not sandboxed — they are admin tools. RBAC controls who can author, edit and run.

Can I run a script on the whole fleet?

Yes. Multi-asset selection. Concurrency limits per organisation prevent thundering-herd events.

How long can a script run?

Per-script timeout. Default 5 minutes. Tunable up to 30. Long-running tasks should be background scripts that emit telemetry, not 4-hour blocking runs.

Can scripts be scheduled per asset?

Yes. Per-asset cron, with overrides per client and per organisation.

Scripts & automation

PowerShell. Bash. Python. On demand or on schedule.

A script library that lives with your fleet. Run on demand, on schedule, or triggered by an event. Output captured to the ticket or asset. Alerts when exit codes go non-zero.

Apply for closed beta

Three runtimes
PowerShell on Windows, Bash on Linux, Python where the runtime is present. Cross-platform via shebang.
Triggers
Manual, scheduled (cron), event-triggered (telemetry threshold), webhook (post-GA).
Output captured
Stdout / stderr per run. Exit code stored. Auto-ticket on failure with output attached.

Cross-OS scripts with metadata, schedules and run history.

How it runs

One library, three runtimes.

Windows — PowerShell (with execution policy override at the agent level)
Linux — Bash; alternative shells via shebang
macOS — Bash / zsh / Python where installed
Cross-platform — Python where the runtime is present
Scripts stored as first-class objects with metadata: name, language, target OS, expected runtime, exit-code semantics, output capture mode.

Triggers

When scripts fire.

Manual — operator runs against a single asset or a fleet selection
Scheduled — cron-style schedule per script per asset
Event-triggered — agent telemetry threshold crosses (e.g., disk free < 5%)
Webhook (post-GA) — external trigger via API

Output handling

Capture, alert, ticket.

Stdout / stderr captured per run
Exit code stored
Failure threshold per script (e.g., exit code != 0 → alert)
Optional auto-ticket on failure with the output attached

Library

Built-in starter library (disk space, service restart, common admin scripts) plus your own. Per-organisation; no cross-tenant script leakage.

Pairs well with

Other things in the platform

RMM agent

Single binary for Windows, macOS and Linux. Real-time bidirectional. Stays up across reboots.

Learn more

Patch management

Windows Update, Linux package manager, third-party software. Policy-driven. Audited.

Learn more

OpsMerge vs NinjaOne

Where each one wins, where each one doesn't.

Common questions

Can I import scripts I already have?
Yes. Paste in, upload as a file, or pull from a Git URL (post-GA).
Are scripts sandboxed?
Scripts run with agent privileges (SYSTEM / root). They are not sandboxed — they are admin tools. RBAC controls who can author, edit and run.
Can I run a script on the whole fleet?
Yes. Multi-asset selection. Concurrency limits per organisation prevent thundering-herd events.
How long can a script run?
Per-script timeout. Default 5 minutes. Tunable up to 30. Long-running tasks should be background scripts that emit telemetry, not 4-hour blocking runs.
Can scripts be scheduled per asset?
Yes. Per-asset cron, with overrides per client and per organisation.

Bring your script library home

Apply for closed beta