Commerce
A store on your own WordPress
Deploy WordPress with managed MariaDB and a public HTTPS URL, then turn on WooCommerce from wp-admin. You own the store. You pay for compute — not per order.
TemplatesWooCommerce
What you get
A private store, packaged to ship
WordPress is ready on deploy. WooCommerce installs from wp-admin. MariaDB, uploads, and the public URL are already wired.
Products and checkout
After the WooCommerce wizard, the catalog, cart, and checkout run on this instance.
Plugins you choose
Install WooCommerce from Plugins → Add New. Payment and shipping gateways are plugins, not a locked marketplace.
Public HTTPS URL
WP_HOME and WP_SITEURL are your https://…stackblaze.app hostname so checkout and admin resolve.
Dedicated instance
Orders, customers, and product images stay on this instance — not in a shared vendor account.
WordPress installer first
The first open is the WordPress installer. You create the admin, then activate WooCommerce.
Managed MariaDB
Posts, products, and orders live in MariaDB. wp-content — plugins, themes, and uploads — persists on a volume.
See WooCommerce in action
Deploy in seconds
One click. WordPress and MariaDB pre-wired.
Pick the WooCommerce template. StackBlaze creates WordPress and MariaDB, sets the public URL, and gives you a hostname. You install the plugin from wp-admin.
This stack
Web
WooCommerce server
MariaDB
managed database · TCP:3306
platform SMTP when the pipeline has mail
- Stack
- WordPress + WooCommerce + MariaDB
- First login
- WordPress installer, then Plugins → Add New
- Address
- HTTPS hostname is already the site URL
After you deploy
- 1
Finish the WordPress installer
Open the public URL. Set the site title, username, password, and email.
- 2
Install WooCommerce
In wp-admin, go to Plugins → Add New, search WooCommerce, then install and activate it.
- 3
Run the store wizard
Set the store address, currency, shipping, and a payment gateway. Rotate the MariaDB password and the WordPress salts before the store takes real orders.
Running WooCommerce on StackBlaze
How the instance is wired
This template is WordPress plus MariaDB. WooCommerce is a plugin you activate. The public hostname is the storefront and wp-admin.
MariaDB holds the store
Products, orders, and customers live in the attached database. Restart WordPress and the catalog is still there.
Product images sit in wp-content
Plugins, themes, and uploads — including WooCommerce — persist on the volume at /var/www/html.
Payments and mail are plugins
Add a payment gateway for checkout. Add an SMTP plugin when order mail must leave the store.
One URL for shop and admin
The public hostname is the storefront and /wp-admin. Attach a custom domain from the dashboard when the shop should use your domain.
Compare
WooCommerce on StackBlaze vs a hosted store
| Feature | WooCommerce on StackBlaze | Hosted store |
|---|---|---|
| Data location | Products, orders, and uploads live on your StackBlaze instance. | Store data lives in vendor-operated infrastructure. |
| Install model | One-click WordPress. WooCommerce from wp-admin. | Create a vendor account and use their shared platform. |
| Plugins | Any WordPress or WooCommerce plugin you install. | Often limited to the host’s app catalog or plan. |
| Operations | You control updates, scale, backups, and the instance lifecycle. | The vendor operates the platform and the limits. |
| Billing | Compute, storage, and bandwidth. No per-order fee. | Usually priced per order, transaction, or plan. |
This template is WordPress plus MariaDB. WooCommerce is installed from wp-admin after the WordPress installer.
FAQ
Common questions
Open the public URL and finish the WordPress installer. Then sign in at /wp-login.php with the username you just created. WooCommerce is not active until you install it from Plugins → Add New.
Ready to deploy WooCommerce?
One click. Dependencies pre-wired. No infrastructure to manage.