PD Google Cloud SQL Server for Blesta

PD Google Cloud SQL Server lets a hosting company sell managed Microsoft SQL Server databases as its own product. Your customer orders on your Blesta order form, a dedicated Cloud SQL for SQL Server instance is created in your Google Cloud project, and your customer runs it from your client area: connection details, trusted addresses, databases and SQL Server logins. Google bills you at cost, you set the price, and the difference is your margin.

It is built for hosts whose customers run .NET and other Microsoft-stack applications and want a managed SQL Server database. You offer the product without building a control panel, and your customers never need a Google Cloud account.

Why hosts choose PD Google Cloud SQL Server

Sell the edition that fits the customer's budget. Offer SQL Server 2019 and 2022 in Express, Web or Standard, and SQL Server 2025 in Express or Standard. SQL Server 2022 Standard is the default. Show the choice at checkout, or fix one edition per package, and price each edition as you like.

A dedicated instance for every order. Each order gets its own Cloud SQL instance and credentials, created in the region the customer picked from more than 40 Google Cloud regions. Nothing is shared between customers.

Dedicated-core machine sizes. SQL Server plans are dedicated-core db-custom vCPU and RAM sizes, chosen at checkout or fixed on the package.

Orders set themselves up. A paid order creates the instance with no step from you. It builds in the background and the connection details appear on their own when Google reports it running. A failed create shows Google's reason in the service's activity and never sits on "creating".

Less support for you. Trusted addresses, databases, logins and password changes are all on the customer's own service page.

Nothing left billing. Terminating a service deletes the instance and the module confirms it is gone, even if your licence has lapsed.

How it works

1. Connect your Google Cloud project. Create a service account with the Cloud SQL Admin role, add a Google Cloud account under Settings, Company, Modules with its JSON key pasted in, and press Test Connection. It makes one read-only call. A missing role, a disabled API, a project without billing or an organisation policy blocking key creation is named in plain words, with the Console path and gcloud command for the policy.
2. Create your package. Set a default region, plan, edition and storage, then generate the package options in one click: Region, Plan, Engine version and Storage. Choices start at zero for you to price.
3. Your customer orders. They choose and pay. Blesta provisions the service once its invoice is paid, and the setup guide shows where to keep that task switched on. The instance is created with your name prefix, and the customer sees a "being set up" message until it is ready.
4. You get paid, they manage it. Blesta keeps billing. Upgrades use Blesta's own flow.

What you get in Blesta

Selling and pricing

• Package options generated and linked to the package: Region, Plan, Engine version (the edition) and Storage
• Choose which options customers see; hidden ones are fixed to your package setting
• Prices you set survive a sync; Rebuild from Google Cloud warns that prices return to their starting value
• Storage from 10 GB, which can also be sold as an option
• A name prefix on every instance, so names read as yours
• Regions and sizes from a catalogue curated against Google's published lists

Provisioning you can trust

• Running Create again never builds a second instance; the recorded one is reused
• Plan upgrades and downgrades resize in place and keep the data. Storage grows in place and a smaller size is refused
• A plan and storage change together applies both
• Changes to one instance run one at a time, and a request that arrives mid-change is told to try again in a minute
• Suspend stops the instance and keeps the data; a suspension that arrives while Google is busy is queued, not dropped. Google still bills storage for a stopped instance, so terminate to stop all billing
• An instance deleted outside Blesta is detected and flagged, without changing your billing

Running it day to day

• Clients and Databases lists every instance against its service, with its state
• An activity log of provisioning, upgrades and password resets, each with its outcome
• Read-only assistant tools report a service's instance, engine, edition, size, region and state, and show recent provisioning. They cannot create, resize, delete or restore anything
• Get help in the PD Modules panel attaches a diagnostic report that you preview and can trim before anything is sent

What your customers get

On the service page in Blesta's client area, a menu gives them Information, Trusted Sources, Users, Databases and Activity.

• Connection details to copy: host, port 1433, the sqlserver login, a password to show or copy, and a ready sqlcmd command. Connections can use SSL/TLS
• Trusted sources: a new instance accepts no connections until the customer adds an address. They manage the list, invalid entries are refused with a message, and changes apply within a minute
• Their own databases, created and dropped from the client area, with system databases protected
• Their own SQL Server logins with passwords they choose; the admin login and system accounts are protected
• A new sqlserver password in one click
• Recent activity with the outcome of each action
• Confirmation first in an in-page dialog before anything destructive

Each section is a switch on the package: Firewall, Connection details, Users and Databases. Switch one off and the customer cannot see it and the server refuses it. The pages render on the Blesta client theme and are fully translatable with wording overrides that survive updates.

Every instance is created with automated daily backups switched on. Restores are done by you in the Google Cloud console; customers ask you.

Security built in

• Your Google key is encrypted on the module account and never shown to a customer.
• Each database password is stored encrypted and shown only to the signed-in owner.
• Customer actions need a signed-in owner and a valid security token.
• Failures on your side show the customer a neutral message and put the detail in your log.
• Customer data, credentials and connection details are never sent to us. Only Google's Cloud SQL Admin API and the licence check are called.

One product, every feature

PD Google Cloud SQL Server is one paid module with everything included. There are no tiers and no per-instance fees to us; you pay Google at cost and keep the margin. It adds its own tables and templates, leaves Blesta files alone, and uninstalls cleanly.

If your subscription lapses, your customers' databases keep running. The module never stops, deletes or alters an instance. New provisioning and your management screens are withdrawn while read-only visibility stays, and everything returns once you are in good standing.

Requirements

• Blesta 6 or later on PHP 8.2 or later, with the ionCube Loader
• A Google Cloud project with billing and the Cloud SQL Admin API enabled, and a service-account key with the Cloud SQL Admin role
• PD Modules, the free control panel every PD module installs into