How do I add a new device type to Jazigo?

You need to implement a Go model interface by creating a new file in the dev directory, following examples like the Cisco IOS model. The README states it's very easy, but requires basic Go programming skills to define connection and data retrieval logic.

Jazigo vs RANCID: which is better for network backups?

Jazigo is written in Go with a single-binary deployment and built-in web UI, offering simplicity and concurrency. RANCID is Perl-based with a longer history and larger community. Choose Jazigo for modern, extensible setups in Go environments, or RANCID if you prefer established Perl scripts and broader legacy support.

Can Jazigo backup configurations to AWS S3?

Yes, Jazigo supports direct storage in AWS S3 buckets. Configure an IAM user with access keys, then point the config and repository paths to the S3 ARN, as detailed in the Using AWS S3 section, enabling scalable cloud retention.

How to automate adding hundreds of devices in Jazigo?

Use the -deviceImport command-line option with a text file formatted with columns for model, id, hostport, transports, username, and password. The README provides an example table, but this bypasses the web UI for bulk operations.

Does Jazigo work with Windows servers or custom APIs?

Jazigo doesn't have built-in Windows support, but you can use the external program model (run) to call custom scripts that fetch configuration. Credentials are passed as environment variables, allowing integration with virtually any system or API.

What are the security risks with Jazigo backups?

Jazigo handles credentials via environment variables or config files and supports SSH cipher customization. However, it lacks native encryption for stored backups, so ensure secure storage practices, especially when using S3 or external repositories.

Open-Awesome

jazigo

MITGov0.13.0

A Go-based tool for retrieving and backing up configuration from multiple network devices and servers via SSH, Telnet, and HTTP.

GitHub

230 stars31 forks0 contributors

What is jazigo?

Jazigo is a configuration backup tool written in Go that automates the retrieval of configuration files from network devices, servers, and other endpoints. It solves the problem of manually backing up device configurations by providing a centralized, concurrent, and extensible system that supports SSH, Telnet, HTTP, and custom external programs.

Target Audience

Network administrators, DevOps engineers, and system operators who manage large fleets of network devices (routers, switches, firewalls) and servers, and need automated, reliable configuration backup solutions.

Value Proposition

Developers choose Jazigo for its simplicity, single-binary deployment, built-in web interface, and extensibility—offering an open-source alternative to commercial tools with support for many platforms, concurrent operations, and cloud storage integration.

Overview

Jazigo is a tool written in Go for retrieving configuration for multiple devices, similar to rancid, fetchconfig, oxidized, Sweet.

Use Cases

Best For

Automating configuration backups for heterogeneous network environments
Managing backups for large-scale device fleets with concurrent connections
Integrating configuration backup storage with AWS S3 for cloud retention
Extending backup support to custom devices or APIs via external programs
Providing a web-based interface for non-technical staff to view backups
Replacing manual SSH/Telnet scripts with a unified, maintainable tool

Not Ideal For

Teams requiring advanced backup scheduling with custom triggers or event-driven workflows, as Jazigo relies on basic interval-based scanning.
Organizations needing a fully graphical interface for all operations, since bulk device imports and advanced configurations depend on command-line tools.
Projects where out-of-the-box support for every device type is critical, as adding new platforms requires Go programming knowledge and implementing custom models.
Environments prioritizing minimal setup and zero manual file management, due to the need to copy static files and configure directories manually.

Pros & Cons

Pros

Broad Device Support

Supports a wide range of network devices like Cisco IOS, Juniper JunOS, and Linux via SSH, Telnet, or HTTP, as listed in the Supported Platforms section, reducing the need for multiple tools.

Efficient Concurrent Processing

Uses Go's lightweight goroutines to handle many devices simultaneously, with adjustable maxconcurrency settings for fast, scalable backups in large deployments.

Integrated Web Management

Provides a built-in web UI for viewing backups, comparing file differences, and administering devices without manual file editing, enhancing accessibility for non-technical users.

Easy Extensibility

Adding support for new platforms is straightforward by implementing simple Go model interfaces, with examples like the Cisco IOS model provided for guidance.

Cons

Bulk Import Limitations

The web UI is not designed for importing many devices; bulk additions require using the -deviceImport command-line option with a text file, as admitted in the Importing Many Devices section.

Manual Setup Steps

Initial installation involves copying static CSS and image files to specific directories and setting environment variables, adding complexity compared to drop-in solutions.

Limited Advanced Features

Lacks built-in support for backup encryption, detailed audit logs, or integration with version control systems beyond basic file storage, which may be needed for compliance-heavy environments.

Frequently Asked Questions

Related Projects

fasthttp

Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http

Stars23,420

Forks1,841

Last commit3 days ago

webrtc

Pure Go implementation of the WebRTC API

Cloudflare Tunnel client

Stars14,949

Forks1,363