Open-Source Observability · eworm-de

routeros-scripts

RouterOS Scripts is a GPL-3.0-licensed collection of RouterOS automation scripts for MikroTik networking devices, covering tasks like backup, DHCP, DNS, monitoring, and certificate management. The project has 1,819 stars and receives active maintenance, with last push in July 2026 and minimum RouterOS 7.21 requirement.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/eworm-de/routeros-scripts

1.8k

GitHub stars

369

Forks

RouterOS Script

Primary language

GPL-3.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	eworm-de/routeros-scripts
Owner	eworm-de
Primary language	RouterOS Script
License	GPL-3.0 — OSI-approved
Stars	1.8k
Forks	369
Open issues	13
Latest release	Unknown
Last updated	2026-07-07
Source	https://github.com/eworm-de/routeros-scripts

What routeros-scripts is

A RouterOS Script repository providing task-specific scripts for MikroTik RouterOS v7+ devices, featuring modular configuration overlay pattern, scheduler-based execution, and certificate-pinned HTTPS fetch for script distribution. Requires RouterOS device-mode with scheduler and fetch enabled; tested against stable and long-term release channels.

Quickstart

Get the routeros-scripts source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/eworm-de/routeros-scripts.git2cd routeros-scripts3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Automated RouterOS Device Management

Deploy consistent backup, certificate renewal, health monitoring, and update workflows across multiple MikroTik devices using centralized script distribution and scheduler-based automation.

Network Monitoring & Alerting

Implement netwatch-based health checks with integration to Telegram and SMS notifications for equipment voltage, link status, and connectivity events without third-party monitoring platforms.

Dynamic DNS & DHCP Management

Automate DHCP pool management, DNS updates, and certificate provisioning for RouterOS-based ISP or enterprise networks with minimal manual intervention.

Implementation considerations

Requires explicit device-mode configuration with scheduler and fetch enabled; some scripts may require additional device-mode features (review per-script requirements).
Certificate trust establishment is mandatory for fetch-based updates; use RouterOS builtin trust store or manually import CA certificates with fingerprint verification.
Configuration is split between global-config (base) and global-config-overlay (user edits) plus optional .d/ snippets; plan configuration strategy and test changes before applying to production.
RouterOS time must be accurate for certificate validity checks; configure NTP before deploying scripts that verify server certificates.
Scripts are push-based via scheduler; no pull/webhook mechanism. Plan for periodic execution intervals (default 1d for updates); adjust for your change frequency needs.

When to avoid it — and what to weigh

Non-RouterOS Environments — These scripts are RouterOS-specific. If your network runs Cisco IOS, Juniper Junos, or other platforms, this project provides no value.
RouterOS < v7.21 Deployments — The main branch targets v7 only and requires at least 7.21. Older installations (v6) require switching to the routeros-v6 branch; backward compatibility is not guaranteed.
Devices with <16MB Storage or ARM CPU Constraints — The project acknowledges that RouterOS package and script sizes strain memory-limited hardware. High configuration or many scripts on old ARM devices introduce stability risk.
Proprietary or Closed-Source Deployment Requirements — GPL-3.0 licensing requires modifications and distributions to remain open-source. If commercial embedding or proprietary derivatives are needed, license compliance is essential.

License & commercial use

GPL-3.0 (GNU General Public License v3.0). Source code is open and free to use, modify, and distribute, provided all derivative works and distributions remain under GPL-3.0.

GPL-3.0 permits commercial use of the software itself, but any modifications or derivative works distributed to third parties must remain under GPL-3.0 with source code disclosure. Internal use of unmodified scripts in commercial deployments is allowed. Requires legal review before embedding in proprietary products or creating closed-source derivatives.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Strong
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

Scripts are distributed via HTTPS with certificate pinning (fingerprint verification encouraged). RouterOS device-mode restricts script capabilities to enabled features only. Review scripts for external API calls (Telegram, SMS, fetch operations) and ensure credentials in global-config-overlay are protected. No formal security audit or CVE history is provided; assume standard script injection and command-execution attack surface applies to RouterOS scripting. Automatic update scheduler (optional) introduces supply-chain risk if rsc.eworm.de is compromised; consider manual review before auto-updates in production.

Alternatives to consider

MikroTik CHR / Cloud Hosted Router custom Python/Bash scripts

If you can run Linux containers or CHR instances, general-purpose scripting languages (Python, Bash) offer more flexibility and wider ecosystem support than RouterOS Script, but require separate infrastructure.

For monitoring and alerting at scale across heterogeneous networks. Higher operational overhead but industry-standard and support multiple vendor devices.

Software development agency

Build on routeros-scripts with DEV.co software developers

Review the README, test scripts in a lab environment with RouterOS 7.21+, and follow the initial setup guide. Join the Telegram community for support.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

oryx gateway gogo

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Observability DevOps / Infrastructure Automation Custom Software Development Talk to DEV.co

routeros-scripts FAQ

Can I use these scripts on RouterOS v6?

Main branch is v7 only (requires 7.21+). Switch to the routeros-v6 branch for v6 compatibility, but it is no longer actively maintained.

Do I need to modify scripts to use them?

Most scripts work out-of-the-box, but require configuration via global-config-overlay. Telegram, SMS, and other integrations need credential setup. Custom device configurations may require per-script tweaks.

What if my RouterOS device is low on storage?

The project acknowledges storage constraints on ARM devices with <16MB. Test script count and size in a lab environment first. Disable unused scripts and monitor free space after updates.

How do I report bugs or request features?

Use the GitHub Issues (13 open as of the provided data). Community support is also available in the Telegram group @routeros_scripts.

Software development & web development with DEV.co

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If routeros-scripts is part of your open-source observability roadmap, our team can implement, customize, migrate, and maintain it.

Ready to Automate Your MikroTik Network?

Review the README, test scripts in a lab environment with RouterOS 7.21+, and follow the initial setup guide. Join the Telegram community for support.

Talk to DEV.co Schedule a Consultation