Dokan Hosting

Dokan hosting for a marketplace with many sellers writing at once.

A single-admin store has one person editing products. A marketplace has dozens, all authenticated, all writing, none of them cacheable.

Vendor dashboards never cachedPer-vendor storage limitsFree migration
Multi-author write tuningPer-vendor quotasPlatform payout cronDaily backupsFree SSL24/7 support
Many sellers, one site

Everything a multivendor marketplace asks of a host.

Every vendor is a logged-in user doing administrative work, which is the traffic a normal store barely has.

One vendor never sees another

Vendor dashboard and order URLs bypass the page cache completely. A cached dashboard shows one seller another seller's orders, which is the failure a marketplace cannot survive.

Cache bypassedPer-vendor scoping

Sized for concurrent authors

Dozens of people editing products simultaneously is a write pattern a single-admin store never produces, so the connection pool is sized for it rather than for page views.

Storage counted per vendor

One seller uploading thousands of product images otherwise consumes the allowance every vendor shares. Limits are applied per account and enforced on upload.

Per-account quotas

Payouts that calculate on time

Commission and withdrawal jobs run on the platform scheduler. Vendors notice money before they notice anything else, and cron that waits for traffic pays late.

Signup that is not a spam target

Open seller registration is attacked from the day it opens, and each fake vendor creates a user, a store and a public page. Rate limits run at the edge.

Operations

See the marketplace, not just the store.

The numbers that matter here are per vendor: who is uploading, whose payouts ran, and which stores are actually active.

  • Per-vendor storage and activity
  • Payout run status
  • One-click admin login
  • Restore any daily backup from the dashboard
Active vendors
Trading
312
Vendor dashboards
Cache bypassed
live
Payout run
Platform-scheduled
02:30
Nightly backup
Replicated offsite
running
Performance

Fifty vendors editing at once.

Marketplace load is authenticated and write-heavy on both sides — shoppers on the front, sellers in the back — and neither half can be served from cache.

Write-sized
connection pool
Per-vendor
storage quotas
NVMe
storage on every plan
MagicWP170 ms
Read-tuned pool under vendor load1180 ms
No object cache540 ms

Illustrative comparison of a vendor dashboard request under concurrent editing. Your numbers depend on vendor count and catalogue size.

Configuration

What we change for Dokan

These differ from a standard WooCommerce site on the same plan, and each follows from the store having many authors rather than one.

SettingWhat we doWhy
Vendor dashboard URLsBypass the page cache entirelyA cached vendor dashboard shows one seller another seller's orders, which is a data breach rather than a performance bug.
Database connectionsPool sized for many simultaneous authorsA marketplace has dozens of people editing products at once, which a store with a single admin never generates.
Vendor mediaStorage and upload limits applied per vendor accountOne seller uploading thousands of images otherwise consumes the allowance the entire marketplace shares.
Withdrawal and commission jobsRun on the platform schedulerPayout calculations that depend on visitor-triggered cron run late, and vendors notice money before they notice anything else on the site.
Vendor registrationRate-limited at the edgeOpen seller signup is a spam target from launch, and every fake vendor creates a user account, a store and an indexable page.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Can vendor dashboards be cached at all?
No. Those URLs bypass the cache completely, because a cached dashboard would show one seller another seller's orders. That is the one thing a marketplace genuinely cannot risk.
How many vendors can the site support?
The limit is concurrent write capacity rather than a vendor count. Dozens of sellers editing products at once is the load that matters, and it is what we size the connection pool against.
Can I stop one vendor filling the disk?
Yes, with per-account storage and upload limits enforced before the file is written. Shared limits mean the most prolific seller sets the ceiling for everybody.
Do vendor payouts run reliably?
They run on the platform scheduler rather than WP-Cron, so they fire on time whether or not anyone visited the site. Late payouts are the complaint that reaches you fastest.
How do you handle fake vendor signups?
Rate limits and challenges at the edge, before WordPress loads. Open registration is attacked from launch day, and each fake vendor leaves a user, a store and a public page behind.

Run your marketplace on a host that expects many sellers.

Free migration, dashboards that stay private, and payouts that calculate on schedule.