Platform map, service boundaries, domains, deployment roles, and roadmap.
Sprey Docs
Canonical technical documentation for Sprey products, deployable stacks, integrations, architecture, and operations.
Always up to dateOpen sourceGitHub-firstSelf-hostedNon-custodialAutomation-first
Your own non-custodial payment infrastructureYour own non-custodial payment infrastructure — hosted and managed by Sprey. Payments go directly to merchant-controlled wallets or payment destinations. Sprey provides software hosting, payment-state observation, and integration infrastructure without receiving, holding, exchanging, transferring, or otherwise controlling merchant funds.See Sprey Processing →
One portal for the whole Sprey platform
Section titled “One portal for the whole Sprey platform”Sprey Processing, Sprey RPC, Sprey Wallet, and future customer-facing services.
Reproducible infrastructure such as Sprey WP Stack and future BTCPay and RPC stacks.
Security, backups, updates, monitoring, recovery, and production procedures.
BTCPay + WooCommerce, Cloudflare, webhooks, and cross-service integration guides.
Planned capabilities, dependencies, milestones, and long-term platform direction.
Sprey WP Stack v1.1.0Production-ready WordPress and WooCommerce Docker stack with Caddy, MariaDB, optional phpMyAdmin, and BTCPay integration for small VPS deployments.Read the WP Stack documentation →Open the WP Stack product page ↗
Documentation principles
Section titled “Documentation principles”CanonicalEnglish is the canonical source language, with multilingual access layered on top.
TransparentPlanned capabilities are clearly marked so documentation reflects what exists today.
ReproducibleProduct documentation stays separate from implementation repositories so each stack can evolve independently.