Encrypted database and file snapshots
Capture your database and protected file folders into encrypted, checked chunks. The 32-byte recovery key is kept separately and never included in an archive or download.
Take encrypted database and file snapshots, verify them and rehearse selective or full recovery in an isolated target.
Capture encrypted copies of your Botble database and files, verify their integrity and schedule daily captures. Rehearse recovery of selected product and customer fields, or a full recovery, in an isolated site with outbound services kept switched off. The recovery key stays separate from every archive.
Capture your database and protected file folders into encrypted, checked chunks. The 32-byte recovery key is kept separately and never included in an archive or download.
Each snapshot records schema, row counts and file hashes, and verification authenticates the archive before any recovery plan. A queued capture is not reported complete until its verified evidence exists.
Schedule a daily capture at a local time and review the last successful capture, missed runs and failures. Owner alerts keep their own acknowledgement.
Choose product, variation and customer fields, review a fixed plan and restore approved values into a marked isolated target. Stock, orders, payments, credentials and consent are never replaced.
Plan a maintenance window of up to eight hours, keep a final copy of the current site and verify the recovered application in isolation. Outbound services stay disabled and nothing is activated live.
Prepare a deletion plan for expired recovery points that protects dependencies and failed work. Only the unchanged approved plan is deleted, and recovery keys and audit history are kept.
A bulk edit overwrote product descriptions yesterday. Choose those products and fields from a verified snapshot and review each value before restoring it in the isolated target. Stock, orders, payments, credentials and consent cannot be selected, so recovery never replays a sale.
Plan a maintenance window, keep a final copy of the current site and restore the verified snapshot into a fresh isolated database and folder. Recovered workflows and social posts stay paused, and application checks cover login, products, basket and admin pages before the rehearsal is accepted.
Screens from the Botble edition, using sample data. Explore the features and requirements below.
Screenshots and interactive demos are coming soon. Product features and setup requirements are listed below.
WooCommerce screenshots are being prepared. The screenshots under Botble show that edition with sample data.
Check supported engines, limits and the configured protection profile before the first capture.
Queue a snapshot, confirm its verified completion and schedule daily captures.
Plan a selected field or full recovery in the isolated target, approve it and review the verification report.
These details describe the Botble edition. Check the platform, services and equipment your shop uses.
Native WooCommerce edition.
Every plan has the same features. Pick the term that suits your business, or buy a perpetual licence and keep it.
GBP reference prices, including applicable VAT/sales tax. Stripe confirms available local-currency pricing before payment. Local currency estimates use current Stripe FX quotes.
Plugin, updates and support — one monthly price
Launch price · save 25%a month
For new customers after the offer: £8 a monthYour rate stays while your subscription remains active
Plugin, updates and support — one yearly price
Launch price · save 25%a year
For new customers after the offer: £80 a yearSame purchased rate on uninterrupted renewals
Yours to keep
Launch price · save 20%once
£249 after the offer
Perpetual licences include 12 months of updates and support. After that, extend them a year at a time for £40 a year, whenever you like, even before the current year ends. Monthly and yearly plans always include updates and support.
Prices include applicable VAT/sales tax. One plugin and one platform edition per licence.
Marketplace, hosting, hardware and external API charges are separate. No payment processing surcharge. See how licensing works →
The workflow, its limits and what is separate.
Still need a hand?Recovery is planned, approved and applied in a marked isolated target, with outbound email, payments, prints and workflows kept switched off. Switching a live site over remains a separate decision.
In a configured location outside the protected site files on your own hosting. Scheduled off-site replication and managed storage are not included, so download encrypted snapshots to storage you control.
Published workflows become disabled drafts and pending social posts pause, while confirmed publication history is kept. A recovered workflow can be added back as an extra disabled draft for review.
No. Capture, integrity verification and an isolated recovery check are shown separately in the health review, with due or stale evidence highlighted.
Cookie preferences