A Dropshipping Online Store on Your Own VPS

A rented builder's dropshipping setup comes with a cut of every order, mandatory paid apps for functions that should be basic, and a support team on the other end that can suspend the account mid-campaign with no real appeal process. NitroCart moves the same setup onto your own VPS: the supplier catalog lives in your own database, checkout runs on your own acquiring account, and order alerts land in a Telegram bot without a mandatory fulfillment-app subscription. More on the engine itself is on the NitroCart homepage.

What it is and who needs it

Self-hosted dropshipping means the storefront itself — catalog, checkout, domain, order handling — belongs to the operator and runs on their server, while the supplier only ships the product to the end customer, the same split as a rented dropshipping setup minus the platform sitting between operator and buyer. The difference from a rented builder is no revenue cut on sales, no mandatory paid apps for things like tracking, upsells, or stock sync that many SaaS builders bundle as non-optional add-ons, and no risk of the store account getting suspended by someone else's support desk with no timely way to appeal. It fits dropshippers tired of stacking fees and subscriptions per order, operators in regions where a popular builder's built-in payment processor doesn't work or isn't available, and teams validating a supplier's product line on real paid traffic before committing to warehouse inventory.

Criteria for choosing a self-hosted dropshipping platform

1. Revenue cut. Does the platform take a percentage of every sale on top of the rental or license fee, or is the cost fixed regardless of sales volume?
2. Control over the payment processor. Can you plug in your own acquiring directly, or does the platform lock you into one built-in provider?
3. Speed of swapping the product line. How long does it take to replace a failing test product with a new one from the same supplier?
4. Hero-product vs. catalog format. Can the storefront switch quickly between a single-product test layout and a full multi-SKU catalog as the line grows?
5. Order alerts without a mandatory subscription. Does the operator get notified of a new order for free, without a paid third-party app in the loop?
6. Storefront uniqueness across multiple launches. When several stores run different supplier lines in parallel, do they stay technically distinct enough to survive ad-network moderation?
7. Cost of ownership at scale. Does the price grow linearly with the number of simultaneous stores, or stay fixed inside one license?

Comparison table: where to run a dropshipping catalog

Option	Revenue cut	Own acquiring	Order alerts	Product line swap
Rented SaaS builder (base plan)	Typically 0–2% plus paid apps for tracking/upsells	Often limited to the platform's built-in providers	Via a paid sync app	Fast inside one builder, but subscriptions remain
Marketplace with built-in dropshipping	Marketplace commission, often double-digit percentage	No, payment routes through the marketplace	Through the marketplace's own dashboard	Limited by the marketplace's catalog policy
Open-source CMS on your own VPS, no format-aware engine	0%, but no ready "hero product vs. catalog" toggle	Yes, any processor via integration work	Needs a separate plugin or custom build	Slow — manual template rebuild
NitroCart on your own VPS	0%, license and hosting only	Yes, any provider via a configurable API redirect	Telegram order alerts, included in the license	Fast — Render setting toggles Landing one ↔ Catalog

How it works in NitroCart

The supplier catalog is built manually in the admin — products are added by the operator as SKUs with a name, price, images, and attributes; there is no automatic stock/feed sync or bulk supplier import in the engine, and that's a deliberate boundary, not a gap: the operator fully controls which items the buyer sees and at what price, with no risk of a third-party feed silently changing a price or pulling a product mid-campaign. Checkout is configured in Checkout settings against your own payment URL and merchant account — any acquiring provider connects through a configurable API redirect, with no single built-in gateway forcing a specific processing partner. The storefront format switches with one field in Render setting: Landing one for testing a single hero product on an ad creative, Catalog once the line grows past one SKU. New-order alerts arrive in the Telegram bot as soon as checkout completes — included in the license, no separate fulfillment subscription — though it's an alert to the operator, not an automated handoff of the order to the supplier. When several supplier lines run in parallel, Theme Uniqueness gives each install its own CSS/JS fingerprint, so parallel stores testing different creatives don't share source code that a moderator could match across accounts.

Unique factual block: cost of ownership across three supplier lines

Three parallel supplier lines testing different creatives on the Pro plan ($1,790 billed yearly, up to 5 simultaneous installs): license cost per line is $1,790 / 3 ≈ $597/year with three lines and $1,790 / 5 = $358/year once you add two more, plus a VPS per line (typically $5–15/month at budget providers depending on load) and a domain ($10–15/year). Total cost of ownership for three lines lands between roughly $2,000 and $2,400 a year, with zero percentage taken on sales. Compare that with a rented builder charging a 2% platform cut plus a typical stack of 3–4 paid apps (conversion tracking, an upsell widget, stock sync) — at $10,000/month combined revenue across three lines, the yearly overpay on fees and subscriptions alone easily clears $2,000–3,000, before counting the builder's own plan rental. The gap widens as revenue grows: the self-hosted model's variable costs stay at zero, while the rented model's costs scale with sales.

When NitroCart is not a fit

If the operator needs a genuine automatic supplier-feed import with real-time stock and price sync, NitroCart doesn't have that tool, and calling manual catalog management an auto-sync would be dishonest; that scenario needs a separate sync integration or a platform where the feature is built in from the start. Similarly, if the business model requires fully hands-off order handoff straight into the supplier's system with no operator step at all, a Telegram order alert is a notification to a person, not an automated API integration with the supplier — that part of the process is either handled manually or built as a separate integration. An honest look at the engine's limits is in when NitroCart is not a fit.

FAQ

Is there an automatic catalog import from the supplier? No, products are added manually in the admin — there's no automatic feed import or stock sync in the engine.

Can any payment processor be connected? Yes, through a configurable API redirect in Checkout settings — the engine doesn't lock you into one built-in payment gateway.

Does NitroCart take a cut of dropshipping sales? No, the cost is the license (a fixed plan fee) plus your own hosting — no revenue-based commission.

How fast can a failing test product be swapped out? Swapping a SKU in the catalog takes minutes, and the storefront toggles between hero-product and full-catalog layout with one Render setting field.

Does the order go to the supplier automatically? No, the Telegram alert notifies the operator — handing the order off to the supplier is done manually or through a separate integration the operator builds.

Can several supplier lines run under one license? Yes, up to 15 simultaneous installs on the Enterprise plan, each with its own domain, catalog, and uniquified storefront.

NitroCart pricing — Start from $99/mo for 1 IP, Pro from $199/mo up to 5, Enterprise from $399/mo up to 15 (yearly — −25%). Next: self-hosted store engine: your VPS, your data, no turnover cut, reseller: someone else's catalog, your store, self-hosted checkout: payments by URL and API, category hub self-hosted engine.