What this means for your team
Four things DataFrugal does for everything your systems push into it.
A stolen login cannot wipe your backups
Files are immutable for their retention period: an attacker who takes over an account can upload, but cannot change or remove what is already there. Deleting early needs a request approved by two different administrators, nobody can approve their own request, and every step is recorded.
Automated, with no password in a script
df-agent pushes database dumps, exports and system backups from cron jobs and CI pipelines using a secret key made for automation. No one's password sits in a script, there is no storage code to write, and no cloud credentials to hand out.
Employee records with access you can prove
Payroll files, contracts and ID documents sit behind roles, are shared only with people in your organisation, and cannot be passed on by the recipient. When someone asks who opened the salary file, you answer from the record rather than from memory.
Reports kept exactly as issued
Month-end reports, audit exports and log archives stay as they were when produced, for as long as your policy needs. Earlier versions are kept and can be restored, so a bad overwrite is not the end of the story.
The three questions IT gets asked
Usually on a bad day, by someone who wants an answer in minutes.
"Can we get last Tuesday's database back?"
Every version you pushed is kept, so you pick the one you need and download it. Files up to 5 TB are supported, and on plans without download fees, pulling a large backup back does not produce a surprise bill.
"Who downloaded the payroll file?"
Every download is recorded against the person who asked for it, with the file and the time. If that record cannot be written, the download is refused — so there is no quiet way to take a copy.
"Are we safe if an admin account is taken over?"
Protected files stay protected: no single administrator can delete them early. You can also restrict storage access to approved IP addresses, so a stolen download link is useless from outside your network.
Where teams start
Three jobs IT usually brings to DataFrugal first.
Long-term backup retention →
Cloud database backups stop at 35 days and sit in the same account an attacker controls. Keep restore points for years, somewhere else.
Partner file exchange →
Replace the FTP server with a scoped identity and an API — set up in minutes, withdrawn in one action, every transfer recorded.
Contracts & recordings →
Signed contracts, NDAs and knowledge-transfer sessions kept unchanged for years, visible only to the people you choose.
What DataFrugal does not do
- It does not run your backup jobs. You schedule them; df-agent or the API does the upload.
- It does not restore into your database. You download the version you need and restore it with your own tools.
- It does not watch for suspicious behaviour. It records what happened; reviewing it is yours.
DataFrugal is the destination, not the backup software. It is where a copy goes so that it survives a mistake, a departing employee or an attacker with valid credentials.
Pricing follows the data you protect, not the number of people or servers, so adding another database or another automation account does not add a licence fee.
Frequently Asked Questions
Common questions from IT and platform teams about backups, automation and access.
Does this replace our backup software?
No. Keep the tools that produce your dumps and snapshots. DataFrugal is where those files land so they cannot be changed or deleted, and so every access to them is recorded.
How do nightly dumps get in?
df-agent runs from a cron job, a scheduled task or a CI pipeline and uploads with a secret key belonging to an automation identity, not a person. You can also use the API directly. Large and multipart uploads are supported, up to 5 TB per file.
What if ransomware reaches the server holding the agent key?
That key can upload, but it cannot change or delete files that are inside their retention period. A new upload becomes a new version and the earlier ones remain, so you still have clean copies to restore. You can shut down the automation identity without disturbing anyone else's access.
Can we keep backups for years?
Yes — you set the retention period, and you pay for the data you protect rather than per user or per server. Plans on Wasabi have no download fees, which matters when a restore means pulling terabytes back.
Who can see employee records we store?
Only the people you give access to. Sharing works inside your organisation and recipients cannot pass files on. Role changes are recorded with the permissions before and after, and DataFrugal does not read file contents.
Point one backup job at it
Start with a single nightly dump and see it locked, versioned and recorded. No change to the rest of your setup.
Talk to us