Choosing how to host Store Console
Two supported ways to run Store Console
Store Console runs on your own server. There are two supported shapes, and the right one depends on what you already have.
Docker on a VPS or dedicated server — recommended
This is the setup we run ourselves and the one the rest of this documentation assumes. You get PostgreSQL with pgvector, Redis, Horizon, Reverb websockets and the digital-product build server, all wired together by the shipped Docker stack. Every feature is available and nothing needs manual configuration.
Shared hosting / cPanel — supported
If you only have cPanel-style shared hosting, Store Console still runs. There is no Docker, usually no Redis, MySQL instead of PostgreSQL, and no ability to keep a long-running process alive. The application handles all of that, but a few capabilities are reduced or need a service you supply yourself.
What actually differs
| Capability | Docker / VPS | cPanel / shared hosting |
|---|---|---|
| Database | PostgreSQL | MySQL — fully supported |
| Queue | Redis + Horizon | Database queue driven by a cron job |
| Cache & sessions | Redis | Database or file |
| Realtime updates | Reverb (included) | Your own Pusher account, or disabled |
| AI assistant | Available | Available |
| AI semantic search | pgvector similarity | Keyword search — embeddings are still stored |
| Digital-product build server | Included in the stack | Run separately, or build releases elsewhere and upload |
Nothing in the list above blocks selling, fulfilling orders, running the ERP modules or using the AI assistant. See Installing on cPanel for the setup, and Running without Docker for the detail on each reduced capability.