Summary

  • Prapl's September 10 announcement promotes scheduled Windows database backups to the user's own local or supported cloud storage.
  • The commercial offer separates software from storage charges; recovering a useful database still depends on the chosen method, access and testing.

Who keeps the copy?

A backup held in an account the buyer controls can offer a route away from a hosted backup service. Prapl's September 10 announcement makes that separation its pitch: Windows software schedules database backups, while users choose local or supported cloud destinations. The vendor-supplied release also advertises unlimited servers and databases, alerts and job-status tracking. It is an announcement of the offer, not independent evidence of recovery performance or proof that the product first became available that day. The supplied release.

The distinction changes who pays whom. Prapl says customers use their own storage accounts and pay those providers directly, without its per-gigabyte markup. Its explicit subscription price is US$9 a month billed annually; the PostgreSQL page states US$108 a year. This should not be budgeted as a perpetual purchase or free storage. A local disk still has capacity and operating costs; cloud retention and transfers retain their own economics. “Unlimited” database coverage does not remove those constraints. Official product site.

A portable format needs a usable recovery path

The supplier describes locating the copy, decrypting and decompressing it, then rebuilding the database with native tools. Its PostgreSQL page names custom-format exports through pg_dump and restoration through pg_restore. It separately describes a whole PostgreSQL-server recovery path for self-hosted version 17 and later physical backups. Those are different methods, not interchangeable promises that every managed database has the same recovery options. The site also describes restoring into another target rather than replacing the original. None of those workflows was executed for this report. PostgreSQL product description.

PostgreSQL's own documentation supplies an important boundary. pg_dump makes consistent exports during concurrent use, but covers one database; cluster-wide objects such as roles and tablespaces require separate treatment through pg_dumpall. The documentation also cautions that, except in simple cases, pg_dump is generally not the right choice for regular production backups. That is a reason to match the method to recovery requirements, not evidence that Prapl lacks its separately advertised physical-backup path. An archive file is not automatically a complete server or application recovery plan. PostgreSQL documentation.

Control of the storage account is only part of custody. Prapl describes client-side encryption, database credentials in Windows Credential Manager and optional online reporting of job name, outcome, size and duration. These are supplier claims, not a security audit. The encrypted outer copy still needs its decryption route before a native restore tool can use the database archive inside. Database logins and the password protecting a backup are different dependencies.

That leaves a sharper buying question than how many databases fit under the subscription: can an authorized operator recover the required data if the original backup workstation is unavailable? A green job record or an intact file can help answer parts of that question. Neither, alone, establishes that the application will return to service.