CMS & Publishing 3 services 3 GiB RAM 15 GB disk

Bagisto

Laravel ecommerce you extend in PHP - catalog, checkout, multi-channel - on a self-hosted MySQL.

One-click deploy, from $25/mo on a Miget plan.

Bagisto is the ecommerce platform for teams that live in Laravel: a full store - catalog, cart, checkout, multi-channel, multi-currency, admin, and a theme/extension system - built on the framework your PHP developers already know. MIT-licensed, so customizing it deeply is just writing Laravel.

This template runs the official all-in-one image in external-DB mode (pointing DB_HOST at the separate MySQL container auto-disables the bundled one) behind a thin nginx proxy. APP_KEY is set explicitly so sessions and encrypted data survive redeploys.

Like the other stores here, the pitch is zero platform fees: Shopify Basic is $39/month plus per-transaction cuts; Bagisto self-hosted takes nothing per sale. It is MySQL-only (no Postgres), which the bundled MySQL container covers.

#what you get

  • Full storefront: catalog, cart, checkout, multi-channel, multi-currency
  • Laravel-native - extend in PHP, not a DSL
  • Theme system, admin, and an extension marketplace
  • Self-hosted MySQL container (external-DB mode disables the image’s bundled one)
  • Headless GraphQL API available
  • MIT licensed - no platform or GMV fees

#topology

ServiceRolePublic
bagistostorefront + admin at /admin (:80)no
webnginx :5000 -> bagisto:80yes
dbMySQL 8 container (local and on Miget)no

#miget sizing

// this stack needs

3 GiB RAM · 15 GB disk · 3 services

2 GiB suits a typical store; the storage volume holds media and cache. MySQL-only - pair with MySQL, not Postgres.

Hobby - recommended fit

$25/mo

2 vCPU · 4 GiB · 80 GiB disk

Headroom for your own apps: 8 GiB at $49/mo

Professional - production

$43/mo

2 vCPU · 4 GiB · 25 GiB disk

Dedicated resources, production SLOs - plan details

One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.

#vs. the managed service

What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.

ServicePlanMonthlyWhat you get
Bagisto on Miget 4 GiB plan$25this whole stack, flat - no usage meters, and room left for your own apps
ShopifyBasic~$39$39/mo ($29 annual) + 2.9% + 30¢ per transaction
BigCommerceCore~$39$39/mo ($29 annual); auto-upgrades past $30K trailing GMV

Self-hosted Bagisto has no platform fee and no GMV cut - your payment-gateway rates only.

#vs. other PaaS

Estimated monthly cost of running this exact stack (3 GiB RAM, 15 GB disk, 3 containers) elsewhere, from published June 2026 rates.

PlatformEst. monthlyNotes
Miget $25 flat compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan
Heroku ~$150 no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown
Render ~$41 per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service
DO App Platform ~$41 no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here)
Railway ~$32 usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top
Fly.io ~$20 cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra

Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.

#deploy it

On Miget

  1. Create a Compose Stack in app.miget.com pointing at the templates repository
  2. Set the stack path to bagisto
  3. Set the required variables:
    • APP_KEY, base64 key set explicitly (or sessions break on redeploy)
    • APP_URL, the app’s https domain
  4. Deploy. Miget layers compose.miget.yaml (RAM, privacy, volumes, managed services) automatically

Locally first?

Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:

git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/bagisto
docker compose up -d

Same files, same behavior. The template README covers connection strings and scaling notes.

#faq

Bagisto, PrestaShop, or Saleor?

Bagisto if your team builds in Laravel/PHP and wants to extend the store in code. PrestaShop for a turnkey European storefront with a module marketplace. Saleor for headless GraphQL with a custom frontend. All three self-host here with no platform fees.

Why set APP_KEY explicitly?

Laravel uses APP_KEY to encrypt sessions and sensitive data. The image auto-generates one per boot if unset - which would invalidate everything on each redeploy. Set a fixed base64 key (the env example has the one-liner) and state survives.

Does it use the image’s bundled MySQL?

No - the all-in-one image bundles a MySQL, but this template disables it (external-DB mode, DB_HOST off-localhost) and runs a separate MySQL 8 container instead, so the database persists cleanly on its own volume. The app’s storage volume holds media and cache.

Ship Bagisto today

One compose stack, 3 GiB of RAM, from $25/month flat, and it runs on your laptop with the same files.