Skip to main content
Redstor protects your clients’ servers, endpoints, Microsoft 365 and Google Workspace from the RedApp, and can email you scheduled backup error reports. Connect Redstor to Neo and your agents can check each failure against the RedApp: close the ticket once the failed backups have succeeded since, and tell a technician which accounts are still failing, and why.
Redstor uses one RedAPI service account per MSP. Connect it once and every agent you enable can use it, with permissions you control per agent.

What Neo can do with Redstor

Backup and Restore Status

Read the recent backups of each backup account, with their result and errors, and the outcome of recent restores, per client.

Clients

Find the client in your RedApp, add a new one, or enable or disable one.

Products and Subscriptions

See which Redstor products a client has, add a product or a trial, and convert a trial.

Consumption

Read the data protected, seats and workloads per client and product.

Your clients are mapped automatically

Neo matches your Redstor clients to the companies in your PSA and keeps the mapping on the Redstor card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching is by name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail. A name match, or one you confirm, is handed straight to your agents, so they read the backups of the right client. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

Next steps

Connect Redstor

Create a RedAPI service account, save it in Neo and turn Redstor on for your agents.