# Vulpy Commerce

- [Vulpy Commerce: an AI-run shop in a box](https://docs.vulpy.io/index.md): Vulpy Commerce is a self-hostable ecommerce product with the Fox AI operator built in: Medusa v2, Next.js and Payload storefront, self-hosted Matomo.
- [Quickstart: your first Vulpy Commerce shop](https://docs.vulpy.io/quickstart.md): Clone Vulpy Commerce, run pnpm bootstrap, start the storefront and Medusa, then bring up Fox in the Vulpy WebUI, all in about ten minutes.
- [Install Vulpy Commerce on your machine](https://docs.vulpy.io/installation.md): Set up Vulpy Commerce locally with pnpm bootstrap, understand the .data layout, and configure data directory overrides for NTFS or exFAT hosts.
- [How Vulpy Commerce is structured](https://docs.vulpy.io/architecture.md): The Vulpy Commerce stack: Fox as the driver, plus a Next.js and Payload storefront, Medusa v2 commerce engine, and consent-gated self-hosted Matomo.
- [Meet Fox: your Vulpy Commerce AI operator](https://docs.vulpy.io/fox/overview.md): Fox is the Hermes agent container inside Vulpy Commerce. It boots the shop, runs it day to day, and grows with you through a guided missions system.
- [The Vulpy WebUI: your Fox control surface](https://docs.vulpy.io/fox/webui.md): Tour the six built-in experience features that make up the Vulpy WebUI: core, welcome, side panel, env-context, env-actions, and profile switcher.
- [Missions: guided setup and daily shop ops](https://docs.vulpy.io/fox/missions.md): Missions turn store setup into a managed process. Follow the first-boot flow in the WebUI, then let Fox handle ongoing catalog, content, and analytics work.
- [Environment context and actions in the WebUI](https://docs.vulpy.io/fox/environment-context.md): The env-context banner shows live shop state; env-actions runs the approved, dev-only operations Fox proposes. Together they gate every change Fox makes.
- [Tailscale and the Fox sidecar identity](https://docs.vulpy.io/fox/tailscale.md): How Fox joins its own Tailscale identity via a sidecar, keeps SSH separate from Fox, and serves HTTPS on its MagicDNS name in the tailnet.
- [Configure AI providers for Fox](https://docs.vulpy.io/fox/ai-providers.md): Choose an LLM provider for Fox, pass API keys as explicit environment variables, and understand how the AWS IMDS lock affects Bedrock access.
- [The AWS IMDS lock and why Fox is fenced off](https://docs.vulpy.io/fox/imds-lock.md): How Vulpy blocks EC2 and Lightsail instance metadata to keep Fox off the VM IAM role, and when to opt out or provide explicit provider keys.
- [Fox sidecars: Gitea and SearXNG](https://docs.vulpy.io/fox/gitea-searxng.md): The two sidecar containers that ship alongside Fox for local git hosting and metasearch, both defined in docker-compose.hermes.yml.
- [Extending the Vulpy WebUI with iframes and pages](https://docs.vulpy.io/fox/extensions.md): Add admin surfaces to the Fox WebUI side panel via VULPY_WEBUI_IFRAMES and serve custom pages under /extensions/ with the WebUI namespace rules.
- [Manage your catalog in Vulpy Commerce](https://docs.vulpy.io/shop/catalog.md): Create and organize products, categories, and editorial content across the Medusa admin and Payload CMS in your Vulpy Commerce shop.
- [Manage orders and customers in Vulpy](https://docs.vulpy.io/shop/orders.md): View orders, fulfill shipments, resend confirmation emails, and manage customer accounts from the Medusa admin in your Vulpy Commerce shop.
- [Storefront content with Payload CMS](https://docs.vulpy.io/shop/content.md): Publish landing pages, posts, and category or product editorial with the Payload CMS that ships inside Vulpy Commerce.
- [Accept payments in your Vulpy Commerce shop](https://docs.vulpy.io/shop/payments.md): Configure payment providers in the Medusa admin, understand authorize vs. capture, and follow the Medusa payment module docs for provider setup.
- [Shipping options and tax in Vulpy Commerce](https://docs.vulpy.io/shop/shipping-tax.md): Configure shipping profiles, rate providers, and tax providers in the Medusa admin so checkout returns accurate totals for every region.
- [Transactional email in Vulpy Commerce](https://docs.vulpy.io/shop/email.md): Configure SMTP, sender identity, and templates for the @vulpy/medusa-plugin-email plugin that sends order, shipping, and password reset emails.
- [Storefront search in Vulpy Commerce](https://docs.vulpy.io/shop/search.md): The Starter Pack adds advanced storefront search on top of Vulpy Commerce, with facets and typo-tolerant queries served from the storefront app.
- [Customer accounts on the Vulpy storefront](https://docs.vulpy.io/shop/accounts.md): The Starter Pack adds a full customer account area (order history, addresses, profile) on top of Medusa's customer module.
- [Contact form and submissions in Payload](https://docs.vulpy.io/shop/contact.md): The storefront contact form uses a math captcha and stores submissions in the Payload contact-submissions collection as a read-only inbox.
- [Analytics with self-hosted Matomo in Vulpy](https://docs.vulpy.io/shop/analytics.md): Run consent-gated behavioral analytics with self-hosted Matomo in Vulpy Commerce: optional in dev, required to go live, and privacy-first by default.
- [Matomo events reference and helper API](https://docs.vulpy.io/analytics/events.md): The consent-gated Matomo event helpers shipped in apps/storefront/src/lib/analytics, plus the PII rules that gate every payload.
- [GTM and GA4 alongside Matomo in Vulpy](https://docs.vulpy.io/analytics/gtm-ga4.md): Configure NEXT_PUBLIC_GTM_ID to layer Google Tag Manager and GA4 on top of the built-in Matomo pipeline in Vulpy Commerce.
- [Environments: dev, staging, and live](https://docs.vulpy.io/deploy/environments.md): Vulpy Commerce isolates dev, staging, and live as separate Docker Compose projects with their own data, env files, and public ports.
- [Deploy Vulpy Commerce to a VPS](https://docs.vulpy.io/deploy/production.md): Install Vulpy Commerce on Ubuntu 24.04 with the interactive wizard: Docker, Caddy, Fox, and dev. Choose Tailscale, own domain, sslip.io, or both.
- [DNS records for a Vulpy Commerce live shop](https://docs.vulpy.io/deploy/dns.md): The DNS records Vulpy Commerce expects for a live environment, plus wildcard, staging label, and preview-host patterns for the golive cutover.
- [Take your Vulpy Commerce shop live](https://docs.vulpy.io/deploy/going-live.md): Add a live environment, point DNS, verify Matomo, and cut over from a noindex preview host to your apex domain with pnpm vulpy env golive.
- [Backup and restore your Vulpy Commerce shop](https://docs.vulpy.io/deploy/backup-restore.md): Snapshot environments with pnpm vulpy env backup, migrate data from a local dev machine to a VPS, and restore on demand from a bundle archive.
- [The Vulpy edge: Caddy, TLS, and sslip.io](https://docs.vulpy.io/deploy/edge.md): The Vulpy edge is a Caddy reverse proxy that terminates TLS, routes hostnames to services, and falls back to sslip.io when no domain is configured.
- [Security hardening for a Vulpy Commerce VPS](https://docs.vulpy.io/deploy/security.md): Deploy user, IMDS lock, host egress lock, split Tailscale identities, and the agent-risk disclaimer that make a Vulpy VPS safe by default.
- [Upgrade a Vulpy Commerce shop safely](https://docs.vulpy.io/deploy/upgrades.md): Pull new Vulpy Commerce releases, rebuild containers, run migrations, and roll back with backups if a release breaks staging.
- [Logs and health checks for Vulpy Commerce](https://docs.vulpy.io/deploy/logs-health.md): Tail environment logs, run health checks, and diagnose Fox from the host with pnpm vulpy env logs, verify, and hermes doctor.
- [Storefront blocks and the block registry](https://docs.vulpy.io/customize/blocks.md): Add or customize Payload blocks in the Vulpy storefront by registering them with the block registry and mapping fields to React components.
- [Payload collections and globals in Vulpy](https://docs.vulpy.io/customize/payload-schema.md): Reference for the Payload CMS collections and globals shipped with Vulpy Commerce, including the sync rules that keep Medusa the source of truth.
- [Customize the Vulpy Medusa v2 backend](https://docs.vulpy.io/customize/medusa.md): Add Medusa v2 modules, subscribers, and admin widgets in apps/medusa-backend, and follow the upstream Medusa module docs for provider integrations.
- [Build features for the Vulpy WebUI](https://docs.vulpy.io/customize/webui-extensions.md): Extend the Fox WebUI with new features, side-panel iframes, and custom pages under /extensions/, using the vulpy-commerce namespace rules.
- [pnpm vulpy CLI reference](https://docs.vulpy.io/reference/cli.md): Reference for the pnpm vulpy command line and top-level pnpm scripts used to install, manage environments, run Fox, and operate a Vulpy Commerce shop.
- [Editions: Core, Pro, and packs](https://docs.vulpy.io/reference/editions.md): Vulpy Commerce editions and add-on packs: Core (free), Starter Pack, Multi-Agent Pack, and Pro. Choose the right level for your shop.
- [Environment variables reference for Vulpy Commerce](https://docs.vulpy.io/reference/env-vars.md): A catalog of the environment variables that configure Vulpy Commerce: install, Fox, data directories, storefront, analytics, and build-time flags.
- [Troubleshooting common Vulpy issues](https://docs.vulpy.io/reference/troubleshooting.md): Fix common problems when running Vulpy Commerce: ownership drift, AWS IMDS, data directories, multiple shops, going live, and credentials resets.
- [Multi-Agent Pack: agent profiles for Fox](https://docs.vulpy.io/reference/multi-agent-pack.md): The Multi-Agent Pack adds multiple Fox agent profiles for different roles and workflows, layered on top of Core or Pro editions.