mimic.
OPEN SOURCE. UNDER YOUR CONTROL.

Your network.
With a memory.

Configurations change.
The peace of mind of a backup stays.

Automate configuration backups for switches, routers, OLTs and firewalls. Know what changed, with the history always at hand.

Get started with Mimic Explore the platform
AGPL-3.0 licenseOn your infrastructure

One memory.
Different networks.

CiscoIOS
MikroTikRouterOS
HUAWEIVRP
JuniperJunos
Check
compatibility ↗
CLARITY FOR NETWORK OPERATORS

Fewer scattered files.
More context.

Inventory, backup runs and versions in one place.
Because saving is only the beginning.

mimic / operations overviewILLUSTRATIVE DEMO
YOUR NETWORK, IN PERSPECTIVE

Everything within reach.

Monitoring active
Devices24in inventory
Recent backups23configurations saved
Need attention01last capture failed
A sample workflow with fictional data.Click the tabs to explore
BUILT FOR EVERYDAY OPERATIONS

Be ready for
the unexpected.

[ 01 — 06 ]
01

Backups on your schedule

Capture configurations over SSH, manually or with scheduled routines for each device.

02

Every change, visible

Browse the history and compare added and removed lines between versions.

03

An organized inventory

Organize devices by vendor, group and tags. Import and export your inventory as CSV.

04

Alerts that reach you

Set up change, failure and recovery notifications through Telegram or Webhook.

05

Access with accountability

Encrypted credentials, access roles and audit logs for your team.

06

A copy beyond Mimic

Sync backups to an external SFTP destination as part of your operations workflow.

FROM SSH TO VERSION HISTORY

Connect. Capture.
Remember every change.

Built for network teams, ISPs
and the people keeping infrastructure running.

01 / CONNECT

Introduce your network.

Add a device, assign an SSH credential and set its backup schedule.

02 / CAPTURE

Let the capture run.

The driver runs vendor-specific commands and captures the device configuration.

03 / TRACK

See what changed.

When something changes, a new version is saved for browsing, comparison and export.

Mimic preserves configurations. Restore them by following the device vendor’s procedure.

YOUR NETWORK. YOUR DATA.

A good memory
starts here.

Host Mimic on your own infrastructure with Docker Compose. The code is open, and you stay in control.

Read the installation guide Explore the code on GitHub ↗
terminal
# 01. Bring Mimic to your infrastructure
git clone https://github.com/brunoavila55/mimic_backup.git
cd mimic_backup

# 02. Prepare the environment
cp .env.example .env

# 03. Configure secrets in .env
# POSTGRES_PASSWORD and SECRET_KEY (32+ characters)

# 04. Start the application
docker compose up --build -d
Requires Git, Docker and SSH access to your devices.
BEFORE YOUR FIRST BACKUP

Good to know.

Is Mimic a cloud service?

You install and run Mimic on your own infrastructure. Docker Compose starts the application and PostgreSQL with persistent volumes.

Which devices can I connect?

The project includes drivers for Cisco, MikroTik / RouterOS, Huawei and Juniper / Junos. Devices must accept SSH connections and allow the capture commands. Validate compatibility with your device model and operating system version.

Can I use and contribute to the project?

Yes. Mimic is distributed under the AGPL-3.0 license. Read the terms and contribution guidelines in the project repository.

How do version history and restoration work?

Mimic compares each captured configuration with the latest version and saves a new version when changes are detected. You can browse and compare the files. To restore, reapply the configuration using the vendor’s procedure; Mimic does not perform this step automatically.

Your next configuration change
deserves to be remembered.

↗