PD DigitalOcean PostgreSQL for Blesta

PD DigitalOcean PostgreSQL lets a hosting company sell DigitalOcean managed PostgreSQL as its own database package. Your customer orders on your Blesta order form, a dedicated PostgreSQL cluster is built on your DigitalOcean account, and your customer manages it from the service page in your client area under your brand. You set the price, DigitalOcean bills you its own price, and you keep the margin.

PostgreSQL is where application developers, agencies and SaaS builders put data they care about, so it suits hosts whose customers are building things rather than installing them. It is for hosts who want a PostgreSQL product with failover, daily backups and access control built in, and who do not want to operate database servers themselves.

Why hosts choose PD DigitalOcean PostgreSQL

Production-grade customers, production-grade cluster. Every order gets its own PostgreSQL cluster, never shared, in the region, plan and version the customer picked. Versions are read live from DigitalOcean, so customers see what DigitalOcean currently offers.

Standard or Advanced Edition. Choose the edition per package as its Engine. Advanced Edition needs no partnership with DigitalOcean and offers dedicated plans from 8 GiB RAM, so you can sell a small starter tier and a larger dedicated tier side by side.

Failover as a checkout option. High availability adds a primary and one standby on both editions, priced by you, and the customer's page says how many standby nodes they have.

Backups the customer can see. DigitalOcean takes a backup every day, and a Standard Edition database's Backups page lists them with date and size, so customers know a backup exists without asking. You do the restores.

Access control without tickets. Trusted sources are the first thing a PostgreSQL customer asks to change. They add and remove allowed IPv4 addresses and ranges themselves, and the change applies within a minute.

Nothing left billing. Cancelling deletes the cluster at DigitalOcean with its users, databases and backups, then confirms it is gone.

How it works

1. Connect your DigitalOcean account. Add your DigitalOcean API token once under Settings → Company → Modules, using a token with Full Access, then press Test Connection.
2. Create your package. Create a package with the module, pick PostgreSQL as the Engine (Standard or Advanced Edition), then set a default region, plan and name prefix. Blesta's cron activates the service after payment.
3. Generate the checkout options. Open the module's Products page and press Generate options. It builds the package's Region, Plan, High availability and Engine version options from DigitalOcean's live catalogue, all priced at zero for you to set.
4. Your customer orders. They choose their options and pay. The cluster is built on your DigitalOcean account in the background, and the connection details appear on their own once it is online, usually within a few minutes.
5. You get paid, they manage it. Blesta keeps billing as usual, and the customer copies the connect command and sets their own trusted sources.

What you get in Blesta

Selling and pricing

• Checkout options for PostgreSQL generated from DigitalOcean's live catalogue: Region, Plan, High availability and Engine version
• Standard Edition and Advanced Edition as separate engines, each its own package with its own price
• Plans quoted as vCPU and RAM with storage included; a blank version means DigitalOcean's default
• High availability as a priced checkout option
• Generated choices start at zero in every currency and you price each one under Packages → Configurable Options; a sync never changes a price you have set
• Choose which choices customers see at checkout; anything hidden uses your package's default and keeps its price
• Clusters are named with your own prefix and the service number

Provisioning you can trust

• A paid order creates a dedicated PostgreSQL cluster on your own DigitalOcean account, with no step by you
• High availability provisions a primary and one standby, on Standard and on Advanced Edition
• An order DigitalOcean would refuse is stopped with a clear message before anything is created; Atlanta, Richmond and Kansas City carry only Premium plans
• Every cluster is recorded before DigitalOcean is asked to create it, and pressing Create again never builds a second one
• A provisioning failure appears in the service's activity with its reason, never left at "Provisioning"
• A plan change through Blesta's own plan-change flow resizes the running cluster in place; host, port and data are kept
• Suspend replaces the trusted sources with a rule nothing matches: the cluster keeps running (DigitalOcean still bills it), the data is untouched, and the customer cannot lift the lockdown. Unsuspend restores exactly the sources saved
• Terminating deletes the cluster at DigitalOcean with its users, databases and backups, and confirms it is gone. There is no retention period, so tell customers to take their own backup first

PostgreSQL editions and backups

• Advanced Edition offers dedicated plans from 8 GiB RAM and needs no DigitalOcean partnership
• A database keeps its edition: moving a service to a package of the other edition is refused with a message, never resized
• The Overview lists every Standard Edition package set to a plan over 4 GiB or to high availability, so you can move it before a customer orders
• Every cluster enforces TLS in transit, and the connect command already uses it
• Standard Edition databases get a Backups page listing the daily backups with date and size; Advanced Edition databases show none

Running it day to day

• A Clients & Databases panel lists every cluster against the service paying for it, with engine, plan, region, endpoint and state
• An Activity panel records every provisioning and lifecycle action with its outcome
• A report shows your licence, whether a DigitalOcean account is connected and how many databases you run
• A cluster deleted outside your billing system is flagged to you

What your customers get

On Blesta the customer's pages are tabs on the service: Information, Trusted Sources, Backups (where the engine lists them) and Activity.

• Connection details in one window: host, port, username and password (masked until Show, with Copy beside each), plus a ready-to-use psql command with SSL required
• The CA certificate as a download, for clients that ask for one; the connect command already uses TLS
• Regenerate password in one click behind an in-page confirmation; the new password appears in the connection details
• Trusted sources: add and remove the IPv4 addresses and ranges allowed to connect, with bad entries refused and changes applied within a minute
• Recent activity: their latest actions, up to 40, each marked done or not
• Cluster layout in plain words: how many standby nodes a highly available database has

The firewall, connection details and backups pages are each a switch on the package: turn one off and it is hidden and refused. The pages render in Blesta's client theme, and every line of customer text is translatable, with overrides that survive updates.

Security built in

• Your DigitalOcean API token is stored encrypted, only ever sent to DigitalOcean, and never shown on a customer page or in a customer message.
• Each database password is stored encrypted and shown only to the signed-in owner of that service.
• Every customer action needs a signed-in owner of the service and a valid security token.
• When something fails at DigitalOcean, the customer sees a neutral message and the reason goes to your activity log.

One product, every feature

PD DigitalOcean PostgreSQL is one paid module with everything included: both editions, high availability, backups listing, trusted sources and password reset. There are no add-on tiers to compare. It installs into PD Modules in one click, updates itself, and uninstalls cleanly: its own tables and settings are removed and no Blesta files are modified.

If your subscription ever lapses, your customers are not cut off. A running database is never stopped, deleted or altered. New provisioning and admin configuration lock first, customers see a neutral "temporarily unavailable" message with their connection details still visible, and cancellations still complete. Renewing restores everything with nothing lost.

Requirements

• Blesta 6.0 or later on PHP 8.2 or later, with the ionCube Loader
• A DigitalOcean account with billing enabled and an API token with Full Access
• Blesta's cron running every minute, which finalises new clusters and confirms cancellations
• PD Modules 0.2.322 or later, the free control panel every PD module installs into