Deploy and Host self hosted WordPress WooCommerce (Open-Source CMS) on Railway

This template runs WordPress 7.1.3 on PHP 8.4 with a Valkey object cache, OPcache and MariaDB. Install WooCommerce from Plugins, then keep cart, checkout and my-account out of any page cache. It suits small stores leaving hosted builders.

About Hosting WordPress WooCommerce open-source software on Railway (self hosted WordPress WooCommerce template)

You own the database, the orders and the uploads. Orders and customers live in MariaDB, so back up that volume and the WordPress volume together.

Why Deploy WordPress WooCommerce, the Shopify alternative on Railway (Railway Free Trial)

Shopify bundles hosting, checkout and support into one monthly bill, and you pay for that convenience whether your store is busy or quiet. Start on the $5 trial and measure the real load first.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying WordPress WooCommerce on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

Railway vs Other Hosting Providers and VPS for WordPress WooCommerce self hosting

Railway ships the tuned stack as one project; the providers below hand you raw compute and leave the assembly to you.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	Tuned WordPress, MariaDB, and Valkey in one deploy	Droplets or App Platform; you install and wire Redis yourself
AWS	Same tuned deploy, billed by usage	EC2, RDS, ElastiCache; control at the cost of setup and upkeep
Hetzner	Same tuned deploy with a dashboard and volumes	Cheap VPS; you own the LAMP stack, backups, and cron

Common Use Cases for hosted WordPress WooCommerce

Small catalog store with card payments: a few dozen products, WooCommerce installed from Plugins, and Stripe or PayPal in test mode until the first real order clears.
Digital downloads: virtual products with no shipping, delivered by WooCommerce's download permissions, with files kept on the /var/www/html volume so they survive a redeploy.
A store bolted onto an existing content site: you already publish posts on this WordPress install, so adding WooCommerce keeps blog and shop on one domain and one login.
B2B catalog with custom fields: wholesale pricing tiers and account-only visibility handled by plugins, while HPOS keeps order lookups fast as order volume grows.
Moving off a hosted builder: you want the product and order data in your own MariaDB, with the cart and checkout excluded from page caching so totals stay correct.

Dependencies for WordPress WooCommerce Docker hosted on Railway

This template runs three services. MariaDB 12.3.3 keeps data on /var/lib/mysql. Valkey 9.1.2 is the object cache, password protected, with no volume.

Deployment Dependencies for Managed WordPress WooCommerce Service (CMS)

You need a Railway account; the template builds the rest. WooCommerce itself is a free GPL plugin from wordpress.org, added after the installer runs. Railway restricts outbound SMTP on some plans, so use an email API plugin for order mail.

Implementation Details for WordPress WooCommerce (Using WordPress official docker image)

The image is built in github.com/onepush-dev/wordpress with OPcache at 256 MB, so shop pages skip recompiles. Set WP_REDIS_DISABLED to true to turn the Valkey object cache off. It caches queries, not pages, so cart and checkout still reach MariaDB. Uploads sit on /var/www/html.

How does WordPress WooCommerce compare against other e-commerce platforms

WooCommerce vs Shopify (Shopify Alternative)

Hosting: Shopify runs servers, payments and upgrades. Here you own the install, backups and plugin updates.
Costs: WooCommerce and WordPress are free GPL software; you pay Railway and your gateway. Shopify charges a plan plus app fees.
Checkout: Shopify's checkout rarely breaks. WooCommerce checkout is a page you control, so you also debug it.

WooCommerce vs BigCommerce (BigCommerce Alternative)

Setup: BigCommerce is hosted with no server work. WooCommerce needs the install done first, then the wizard.
Customization: WooCommerce themes and plugins are open PHP you can edit. BigCommerce limits you to its app market and theme layer.
Scaling: BigCommerce absorbs traffic spikes. Here you watch RAM, and a spike can hit the PHP 512M limit before you tune it.

WooCommerce vs Wix (Wix Alternative)

Site and store: Wix bundles a builder with its store. WooCommerce shares one WordPress database and login with your blog and docs.
No-code vs PHP: Wix wins for non-technical owners. WooCommerce templates are PHP and CSS, more work and more control.
Plugins: Wix's commerce tools are curated. WooCommerce installs anything, including plugins that slow the site down.

WooCommerce vs Squarespace (Squarespace Alternative)

Design: Squarespace templates look sharp out of the box; WooCommerce needs theme choice and CSS work to match.
Ownership: Squarespace manages hosting. Here you hold order tables and uploads, and restore them yourself.
Tax and payments: Squarespace handles tax and gateway setup simply. WooCommerce needs a gateway plugin in test mode plus tax rates.

How to use WordPress WooCommerce (the OSS open-source CMS)?

Open your Railway domain and finish the WordPress installer.
Set Settings, Permalinks to Post name.
In Plugins, Add New, install and activate WooCommerce.
Run its setup wizard for address, currency and product types.
Confirm HPOS under WooCommerce, Settings, Advanced, Features.
Check Tools, Site Health for the Valkey object cache drop-in.
Add a gateway plugin and leave it in sandbox mode.
Install an email API plugin; outbound SMTP is restricted.
Place a test order and confirm it lands in the orders table.

How to self host WordPress WooCommerce on other VPS Services (WordPress self hosting guide)

Same stack, your hardware. Roughly 512 MB to 1 GB RAM gets WordPress plus MariaDB going on a small shop, and Valkey wants up to 256 MB on top.

Clone the Repository

Clone the tuned image repo onto the box; it holds a Dockerfile and rootfs, no compose file:

git clone https://github.com/onepush-dev/wordpress.git
cd wordpress

Install Dependencies

Docker is enough. Build the image, then run MariaDB and Valkey containers on one Docker network.

docker build -t wp-tuned .
docker network create wp

Configure Environment Variables

Put these in a wp.env file: WORDPRESS_DB_HOST, WORDPRESS_DB_NAME, WORDPRESS_DB_USER and WORDPRESS_DB_PASSWORD for MariaDB, WP_REDIS_HOST and WP_REDIS_PASSWORD for Valkey, the eight auth keys and salts, and WP_HOME.

WP_HOME=https://your-domain
WP_REDIS_HOST=valkey

Start the WordPress WooCommerce Application

Start the app, finish the WordPress installer in the browser, then install WooCommerce from Plugins, Add New. Check Tools, Site Health shows the object cache drop-in active before you add products.

docker run -d --name wp --network wp --env-file wp.env -p 80:80 wp-tuned

Railway runs this same image and handles the domain, TLS, MariaDB and Valkey wiring, and the health checks for you.

Official Pricing of WordPress WooCommerce (WordPress pricing)

WooCommerce itself costs nothing: it is a free, GPL-licensed plugin, and so is WordPress. There are no license fees, no per-order cut, and no monthly platform charge.

WordPress WooCommerce cloud vs self hosted comparison (Pricing, features, costs, and more)

Hosted store builders bundle hosting into a plan and decide what you install. Self hosting keeps WooCommerce free and GPL; you pay Railway for the resources the stack uses.

Monthly cost of self hosting WordPress WooCommerce on Railway

Expect about $5-20/mo for a small to medium store, depending on traffic and RAM, and the $5 Railway trial covers the first experiments. Nothing charges per product, per plugin or per order, because WordPress and WooCommerce are GPL software.

System Requirements for Hosting WordPress WooCommerce on a VPS

Plan for 512 MB to 1 GB RAM for WordPress plus MariaDB, and PHP 8.4 with OPcache.

Frequently Asked Questions (FAQs)

Do I need a page cache for WooCommerce?

Not to launch. If you add a page cache later, exclude cart, checkout and my-account pages, and skip requests that carry a WooCommerce session cookie.

Is the Valkey object cache safe for carts and sessions?

Yes. It's a cache only, with no volume, so nothing important is stored there for the long term. Orders, customers and sessions live in MariaDB, and a Valkey restart just means a cold cache.

How do I send order emails?

Order emails need working outbound mail, and Railway restricts SMTP on some plans, so use an email API plugin such as Postmark, SendGrid, Mailgun or Brevo rather than raw SMTP.

What is HPOS?

High-Performance Order Storage keeps orders in dedicated tables instead of posts and postmeta. It's on by default for new stores since WooCommerce 8.2 and is managed under WooCommerce, Settings, Advanced, Features.

How many products can it handle?

A small to medium catalog, roughly a few thousand products, sits fine on 512 MB to 1 GB of RAM. Past that, watch MariaDB memory and add a page cache before you blame the object cache.

How do I back up orders?

Back up MariaDB for orders and customers and the /var/www/html volume for uploads and plugins, together. A database-only backup leaves you restoring a store with missing product images.