Answers the two questions that actually matter at 3am.
Is anything on this server about to break — and did last night's backup actually run? Not "is the server up". Both of those failures are quiet, and most monitoring doesn't look for them.
$ vaultcheck audit Vaultcheck audit — web-01 — overall: CRIT generated 2026-10-31T02:04:11+00:00 CRIT backup newest artifact is 22d 4h old (threshold 26h) WARN disk /var at 87% (5.2 GB free) OK inodes max 31% (/) OK memory 1.4 GB / 8.0 GB used OK load 0.42 / 0.31 / 0.28 CRIT systemd backup@daily.service failed OK cron crontab present, 6 jobs WARN clock not synchronised (drift ~184s) OK logs log growth within limits WARN updates 14 pending, reboot required summary: 5 ok, 3 warn, 2 crit, 0 skipped
🔒 Secure checkout by Creem. 14-day money-back guarantee.
See what it checksOne-time payment. No subscription, no account, no telemetry. Linux only.
Ten read-only checks, one report
Vaultcheck reads. It never writes to your configuration, never installs an agent, and nothing runs between invocations.
You can prove that by running a single check and watching it: vaultcheck audit --only disk.
| Check | What it actually looks for |
|---|---|
| backup | Age of the newest artefact in your backup target, compared against a threshold you set. This is the one that catches a job which exits 0 and writes nothing. |
| disk | Volume usage and time-to-full, not just a percentage. |
| inodes | Inode exhaustion. A filesystem at 40% used with 100% inodes cannot be written to. |
| memory | Memory and swap pressure. |
| load | Load average relative to core count. |
| systemd | Units in a failed state — the failure that can sit unnoticed for months. |
| cron | That your scheduled jobs still exist and are enabled, rather than having been dropped by an upgrade. |
| clock | NTP synchronisation and drift. Bad clocks break TLS, cron timing and log correlation. |
| logs | Abnormal log volume growth. |
| updates | Pending package updates and whether a reboot is required. |
Standard library only
No pip install, no virtualenv, no compiled extensions. A single 38 KB .pyz you can copy to a server and run.
No agent, no daemon
There is no background process and no state to corrupt. It runs, prints, exits.
Built for automation
--fail-on warn|crit returns a non-zero exit code so cron, systemd timers or a heartbeat service can page you.
Machine-readable output
Text for humans, JSON to diff day against day, HTML to attach to a ticket.
How it works
Requires Python 3.8 or newer. Nothing else.
1 · Get the file
After checkout you receive a download containing vaultcheck.pyz, a .whl package, a README, a licence text and a quickstart, plus a licence key.
2 · Activate once per machine
vaultcheck license activate --key YOUR-KEY3 · Run the audit
python3 vaultcheck.pyz audit # full text report
python3 vaultcheck.pyz audit --format json # for pipelines
python3 vaultcheck.pyz audit --format html -o report.html
python3 vaultcheck.pyz audit --fail-on crit # exit non-zero on critical
python3 vaultcheck.pyz audit --only backup diskTry before you buy
Without a licence the audit command still runs and prints the overall verdict and a per-severity count,
so you can confirm it detects what you expect on your own server. Per-check detail, JSON and HTML output require an activated licence.
Who builds this
Hi, I'm Renhua. I'm a solo developer based in Sichuan. I build simple, practical CLI tools to solve real operational problems like silent backup failures and data extraction. If you run into any issues or have questions, just reply to this email and I'll get back to you personally.
renhua.wei@zohomail.com
Pricing
You get the tool, one licence key, and updates within the 1.x series. No account to create, no recurring charge.
Secure checkout handled by Creem, who act as the merchant of record.
14-day money-back guarantee — see Terms.
FAQ
What exactly is it not?
Not a replacement for Prometheus, Zabbix or Netdata — there is no time-series database, no graphing and no long-term storage. Not cross-platform: Linux only. Not open source. If you already run a mature observability stack with alerting on backup freshness, you probably don't need this.
Does it replace my monitoring?
No. Vaultcheck is a point-in-time audit you run on demand or from cron. Monitoring tells you continuously whether things are up; this tells you whether the things you assume are happening actually are.
Does it send my server data anywhere?
No. The audit runs locally and reads local system state. The only network call is licence activation/validation, which sends your licence key and hostname. No report content, no hostnames from your infrastructure listings, no telemetry.
Is it safe to run on production?
It is read-only: it inspects filesystem usage, unit state, load, clock and similar signals. It does not modify configuration, restart services or write outside a state directory used to store your licence.
How many machines can I use one key on?
One licence is intended for one machine. Activation binds the key to a hostname; you can deactivate and move the
licence to another machine using vaultcheck license deactivate.
Which Python versions are supported?
Python 3.8 and newer, on Linux. It uses only the standard library.
Can I get a refund?
Yes — within 14 days of purchase, no reason required. Email renhua.wei@zohomail.com with your order number and we will refund it.
Do you offer support?
Email renhua.wei@zohomail.com. This is a small, independently developed tool, so replies are usually within two business days.
Privacy Policy
Last updated: 31 October 2026
This policy explains what data is collected when you visit this website or purchase Vaultcheck, and what the Vaultcheck software itself does and does not do.
1. Who is responsible
Vaultcheck is developed and sold by Renhua Wei, an independent developer operating from Sichuan, China ("we", "us"). Creem acts as the merchant of record for all purchases and handles payment processing. For privacy questions, contact renhua.wei@zohomail.com.
2. What this website collects
This website is a static page. It sets no cookies, loads no third-party scripts, no analytics, no advertising pixels and no external fonts. We do not build profiles of visitors.
Our hosting provider records standard server access logs (IP address, timestamp, requested URL, user agent) for security and abuse prevention. These logs are retained for a limited period and are not used for marketing.
3. What is collected when you buy
Checkout is hosted by Creem. When you purchase, Creem collects and processes:
- your email address (to deliver the licence key and receipt)
- your name and billing country where required for tax purposes
- payment details — handled entirely by Creem and its payment providers; we never see or store card data
- the transaction record (order number, product, amount, currency)
We receive from Creem only what is needed to fulfil your order: your email address, the order identifier, the licence key issued to you, and the amount paid. Creem's own privacy policy governs the data it collects as merchant of record.
4. What the software collects
The Vaultcheck audit itself collects nothing. It reads local system state, produces a report on your machine, and transmits nothing.
The only network communication from the software is licence activation and validation. On those calls we receive your licence key, the hostname of the machine being activated, and an instance identifier derived from it. This is used solely to enforce licence limits and to let you deactivate and move a licence. We do not receive your audit results, your files, your configuration, or a list of the things we checked.
There is no telemetry, no usage analytics, no crash reporting, and no remote kill switch in the audit path.
5. Why we process data and on what basis
- Performance of a contract — to deliver the software and licence you purchased, and to provide support.
- Legitimate interests — to prevent licence abuse and fraud, and to keep the service secure.
- Legal obligation — tax and accounting records, handled by Creem as merchant of record.
6. Sharing
We do not sell personal data. Data is shared only with: Creem (payments and order fulfilment), our hosting provider (serving this page and the licence endpoint), and where required by law.
7. Retention
Purchase records and support correspondence are kept as long as needed to provide support, honour refunds, and meet accounting obligations. Licence activation records are kept while the licence is active. Server access logs are kept for a short security window and then discarded.
8. Your rights
Depending on where you live, you may have the right to request access to, correction of, or deletion of your personal data, to object to or restrict processing, and to data portability. To exercise any of these, email renhua.wei@zohomail.com. We will respond within a reasonable period and in any case within the time required by applicable law. You may also have the right to lodge a complaint with your local data protection authority.
9. International transfers
Our service providers may process data in countries other than yours, including the United States and the European Union. Where required, transfers rely on appropriate safeguards such as standard contractual clauses.
10. Children
Vaultcheck is a developer tool intended for professional use and is not directed at children.
11. Changes
If this policy changes materially, the "last updated" date above will change and, for significant changes, we will note them on this page.
Terms of Service
Last updated: 31 October 2026
These terms govern your purchase and use of the Vaultcheck software ("the Software"). By purchasing or using the Software you agree to them. If you do not agree, do not purchase or use it.
1. The product
Vaultcheck is a command-line tool for Linux that performs read-only system health and backup-freshness checks and
produces a report. It is delivered as a downloadable archive containing a self-contained .pyz
executable, a Python wheel, documentation and a licence key.
2. Purchase and merchant of record
Purchases are processed by Creem, which acts as the merchant of record. Your payment is subject to Creem's terms and privacy policy in addition to these terms. The price shown at checkout is the total price; applicable taxes are handled by Creem according to your billing country.
3. Licence grant
On payment we grant you a non-exclusive, non-transferable, perpetual licence to install and use one copy of the Software on one machine per licence purchased, for your own internal or professional use.
You may not:
- redistribute, resell, sublicense, rent or lend the Software or your licence key
- publish the Software or its source in whole or in part
- circumvent, disable or remove the licence mechanism
- use the Software to provide a competing commercial product or service
4. Delivery
Delivery is electronic. After successful payment you receive a download link and a licence key, by email and on the order confirmation page. If you do not receive them, contact renhua.wei@zohomail.com with your order number and we will resend them.
5. Updates
Your purchase includes updates released within the 1.x series of the Software at no extra cost. Major versions may be offered separately.
6. Refunds
If the Software does not work for you, email renhua.wei@zohomail.com within 14 days of purchase with your order number and we will refund the purchase price. Refunds are processed by Creem back to your original payment method. We may decline refunds where there is evidence of licence abuse.
7. Acceptable use
You are responsible for how you use the Software. You must have authorisation to run it on any machine you point it at. The Software is read-only by design, but you remain responsible for complying with your own organisation's policies and with applicable law.
8. No warranty
The Software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and non-infringement.
In particular, Vaultcheck is a diagnostic aid, not a guarantee. It can only report on the checks it implements and on the state of the machine at the moment it runs. A passing report does not mean your system is secure, correctly configured, or that your data is recoverable. You remain responsible for your own backups and for testing that they restore.
9. Limitation of liability
To the maximum extent permitted by law, we are not liable for any indirect, incidental, special, consequential or punitive damages, or for any loss of data, profits, revenue or business, arising out of or related to the use of or inability to use the Software. Our total aggregate liability for any claim relating to the Software is limited to the amount you paid for it.
Nothing in these terms excludes liability that cannot be excluded by law.
10. Support
Support is provided by email at renhua.wei@zohomail.com on a reasonable-effort basis. There is no service-level agreement and no guaranteed response time.
11. Termination
This licence terminates automatically if you breach these terms. On termination you must stop using the Software and delete your copies. Sections 8, 9 and 12 survive termination.
12. Governing law
These terms are governed by applicable law, without regard to conflict-of-law rules. Nothing here removes any mandatory consumer protection rights you have in your country of residence.
13. Changes to these terms
We may update these terms for future purchases. The version in force is the one published on this page at the time of your purchase.
14. Contact
Questions about these terms: renhua.wei@zohomail.com.