InfraReplica
Pricing How it works→
What it looks like Pricing How it works Documentation
How it works→

Back up every customer’s fleet.
Each under its own key.

Their firewalls, switches, routers and Linux servers — collected, versioned and locked, on infrastructure you own.

How it works→ Pricing↓

Cisco Meraki · FortiOS · PAN-OS · Panorama · BIG-IP · Junos · AOS-CX · OmniSwitch · Infoblox NIOS · Linux servers

Fleet status for one customer: thirty devices, twenty-eight compliant, then the two needing attention — each with its platform, its last success and the reason it is being reported.Fleet status for one customer: thirty devices, twenty-eight compliant, then the two needing attention — each with its platform, its last success and the reason it is being reported.
12platform families, from Meraki to F5
0inbound flows towards your customers’ networks
30 dwrite-once lock on every version, and it can be set to years
3levels of policy: platform, customer, device

What it looks like

Three screens, and the questions they answer.

One search field: a device name typed in part, and its state, its customer and its last backup returned before the page has loaded.One search field: a device name typed in part, and its state, its customer and its last backup returned before the page has loaded.
“Where is that switch?”One field. The state arrives before the page does.
A month of backups, day by day: successes, the day a device failed, and the retries that followed.A month of backups, day by day: successes, the day a device failed, and the retries that followed.
“What did we have on the 14th?”A month at a glance, and the day a backup did not run.
One device: its platform, its schedule, its versions and the changes between them, on a single screen.One device: its platform, its schedule, its versions and the changes between them, on a single screen.
“What changed on this firewall?”One device, its whole history, on one screen.

Isolation · Immutability · Independence

Three things you can verify, rather than take on trust.

Isolation

One customer’s data cannot reach another’s.

PostgreSQL bounds every query to the user’s customer. No screen has to remember to. Each customer holds their own key and their own repository.

How isolation is enforced →

Immutability

Yesterday cannot be rewritten.

Agents may only append, and the storage locks the objects. Whoever takes an agent cannot destroy the history it wrote.

The write-once path →

Independence

Nothing in the restore path belongs to us.

PostgreSQL and Kopia, on your own infrastructure. The licence is checked offline. No server of ours decides what you may do.

What happens if we disappear →

Collectors

Collectors for twelve platform families.

Each platform below has its own collector, built for the way that platform exposes its configuration.

  • Merakidashboard api
  • FortiOSssh · api
  • FortiSwitchOSssh
  • FortiAPssh
  • PAN-OSapi · ssh
  • Panoramaapi
  • BIG-IPicontrol · ssh
  • Junosnetconf · ssh
  • AOS-CXssh
  • OmniSwitchssh
  • NIOSwapi
  • Serverssh · rsync

Where a platform offers two ways in, both are supported: if one is unavailable the other takes over, and the report says which was used. Some offer only one — a Meraki organisation keeps its configuration in the cloud, a Panorama exposes nothing restorable on its command line, an Infoblox grid gives up the same full grid backup its grid master produces for itself, which restores the whole grid at once and is applied by hand, never by the platform — and the platform says so, rather than passing off a lesser artifact as a good one.

Pricing

One annual licence, everything included.

Unlimited customers, agents and users. The price depends only on the number of devices backed up. No volume billing, no per-seat surprise.

Up to 2,000 devices

€35,000/ year

The shape of a provider running the fleets of several dozen customers.

  • Unlimited customers, agents and accounts
  • Every supported platform
  • PDF reports and API
  • Updates and fixes
Request a quote→

From 2,000 to 4,000 devices

€45,000/ year

Same platform, same functional scope, a fleet twice as wide.

  • Everything above
  • Support with using the platform and with its evolution
  • We size the object store with you: retention, lock and growth
  • Annual compliance review
Request a quote→

Beyond that

Bespoke

Wider fleets, several storage sites, particular contractual requirements.

  • Sizing worked out together
  • Negotiated service commitments
  • Support in taking over an existing fleet
Get in touch→

Perpetual licence on request. The storage stays with you: nothing to migrate on exit, no billing by volume.

Write to contact@infrareplica.com — a fleet inventory and the platforms in it are enough to size a quote.

Everything above, argued.

The security model and what enforces it. The exit path. Retention resolved across three levels. The API, the reports, and every screen of the product.

Written twice — once for the team that will run it, once for the people who sign for it.

How it works, in detail→ Documentation↗