SHKeeper

Open-source cryptocurrency payment processing, honestly reviewed. No marketing fluff, just what you get when you run it on your own server.

TL;DR

• What it is: Open-source (GPL-3.0) self-hosted cryptocurrency payment gateway and merchant processor — accept crypto directly to your wallet, no intermediaries, no per-transaction fees [1].
• Who it’s for: E-commerce operators, SaaS founders, and hosting businesses that want to accept BTC, ETH, USDT, and a dozen other coins without routing payments through Coinbase Commerce, CoinGate, or similar services that take 0.5–1% per transaction and hold your funds.
• Cost savings: Coinbase Commerce and CoinGate take a cut of every transaction. SHKeeper self-hosted costs $0 in software fees — your only overhead is the VPS. For a business processing $50K/month in crypto, eliminating a 1% gateway fee saves $500/month, or $6,000/year [2].
• Key strength: Genuinely non-custodial — private keys stay on your server, not on a third-party platform. Supports 14+ cryptocurrencies including privacy coins (Monero) and stablecoins across multiple chains [1].
• Key strength: No KYC or AML requirements. You run the software; you set the rules [1].
• Key weakness: Installation requires Kubernetes (k3s) and Helm. This is not a Docker Compose one-liner. For non-technical founders, the setup complexity is a real barrier [1].
• Key weakness: At 538 GitHub stars, this is a small project from a hosting company (VSYS Host). The community and ecosystem are thin compared to BTCPay Server [1].

---

What is SHKeeper

SHKeeper is a self-hosted, open-source cryptocurrency payment processor built by VSYS Host, a Ukrainian VPS provider. It positions itself as both a gateway and a merchant — meaning it handles both the payment UI your customers see (choose crypto, get address, scan QR code, confirm payment) and the backend settlement (funds go directly to your wallet, no intermediary custodian) [1][2].

The core value proposition is simple: every other crypto payment gateway you’ve heard of — Coinbase Commerce, CoinGate, NOWPayments, BitPay — holds your funds in custody for some period, takes a transaction fee, and requires varying degrees of KYC on both sides. SHKeeper eliminates all three. Payments go peer-to-peer from your customer’s wallet to yours, the software is free, and nobody is checking IDs [1][2].

The project is backed by VSYS Host, which also sells dedicated servers optimized for running SHKeeper’s full-node requirements. That’s worth understanding upfront: the open-source version is free, but the company’s revenue model involves selling you managed setup ($2,000/year “Advanced” plan) and server hosting. This creates an incentive to keep the self-hosted path technically demanding enough that non-technical users consider paying for managed setup [2].

As of this review, SHKeeper sits at 538 GitHub stars. For context, BTCPay Server — the dominant open-source crypto payment processor — has over 7,000 stars and a substantially larger contributor base.

---

Why People Choose It

No independent third-party reviews were available for synthesis at the time of writing. The following is based on primary sources: the GitHub README, official website, and documentation.

The case for SHKeeper over managed crypto gateways comes down to three things.

Transaction fee elimination. Most crypto payment gateways charge 0.5% to 1% per transaction. For a business doing $10,000/month in crypto revenue, that’s $600–$1,200/year in fees, pure overhead. SHKeeper charges zero per-transaction fees — you pay only for your VPS [1][2].

Non-custodial operation. When you use Coinbase Commerce or CoinGate, you’re trusting a third party with access to your payment flows, customer data, and sometimes the funds themselves during settlement windows. SHKeeper sends payments directly to your wallet address. The only party who can access the funds is you [1].

Privacy and no KYC. This matters for two different categories of user: legitimate businesses operating in jurisdictions where KYC compliance is burdensome, and privacy-focused operators who simply don’t want to hand customer payment data to a US company subject to subpoena [1].

The case against SHKeeper relative to BTCPay Server is community size and ecosystem maturity. BTCPay has been around since 2017, has thousands of deployments, extensive documentation, a large plugin ecosystem, and supports Lightning Network natively. SHKeeper is newer, smaller, and still building out its ecosystem.

---

Features

Supported cryptocurrencies [1]:

• Bitcoin (BTC), Litecoin (LTC), Dogecoin (DOGE)
• Ethereum (ETH), Binance Smart Chain (BNB), Tron (TRX), Solana (SOL)
• Ripple (XRP), Monero (XMR), Avalanche (AVAX), Polygon (MATIC), Firo (FIRO)
• USDT (ERC20, TRC20, BEP-20, Polygon, Avalanche)
• USDC (ERC20, TRC20, BEP-20, Polygon, Avalanche)

That’s 14+ distinct coins and 20+ chain/token combinations. Monero support is notable — XMR is a privacy coin that most managed gateways refuse to touch.

Payment handling [1][2]:

• Customer-facing payment UI with QR code and wallet address display
• Countdown timer, payment status polling
• Partial payment support — accept underpayments, credit the rest to a balance
• Overpayment crediting — if a customer sends too much, it goes to your balance rather than being lost
• Customizable exchange rates and commission structure
• Embeddable payment buttons for any website

Settlement and wallet management [1]:

• Non-custodial — private keys remain on your server
• Auto-withdrawal to cold wallet (by schedule or accumulated balance threshold)
• Multipayout — send crypto to multiple addresses in a single operation
• Wallet encryption with API-accessible decryption key entry

CMS integrations (ready-made modules) [1]:

• WooCommerce / WordPress
• WHMCS (web hosting billing)
• OpenCart 3
• PrestaShop 8

API [1]:

• REST API with API key authentication
• Invoice creation, address retrieval, transaction lookups
• Webhook callbacks on payment events
• Prometheus metrics endpoint
• Payout and multipayout endpoints

Infrastructure [1]:

• Kubernetes-native (Helm chart)
• Runs on k3s for single-server installs
• Optional full-node operation for BTC, LTC, DOGE, XMR (instead of relying on shared nodes)

---

Pricing: SaaS vs Self-Hosted Math

SHKeeper’s own pricing tiers [2]:

Tier	Cost	What you get
Open-Source	Free	Software license, community support, self-setup
Advanced	$2,000/year	Integration and setup by VSYS Host, extended tech support, faster updates, dedicated account manager
Custom	On request	Customization of SHKeeper, full integration and setup

The “Advanced” plan at $2,000/year is essentially a managed deployment and support contract. You’re paying for VSYS Host’s engineers to set up and maintain your instance, not for the software itself. Whether that’s worthwhile depends entirely on your team’s technical capacity.

Managed crypto gateway alternatives for comparison:

• CoinGate: 1% per transaction, plus fixed fees on some coins. No setup cost, but fees compound at volume.
• Coinbase Commerce: No transaction fees, but funds custodied by Coinbase; requires Coinbase account and their KYC.
• NOWPayments: 0.5% per transaction standard, 0.4% at higher volume.
• BitPay: 1% per transaction, minimum $5/month for merchant accounts.

Concrete math for a business processing $20,000/month in crypto:

• CoinGate at 1%: $200/month in fees, $2,400/year
• NOWPayments at 0.5%: $100/month, $1,200/year
• SHKeeper self-hosted on a $20/month VPS: $240/year, zero transaction fees
• SHKeeper Advanced plan: $2,000/year flat — only makes sense if your internal setup cost exceeds $1,760

For high-volume merchants ($50K+/month), self-hosted SHKeeper pays for the Advanced plan in under two months of fee savings compared to a 1% gateway.

---

Deployment Reality Check

Here’s where SHKeeper diverges sharply from more accessible self-hosted tools. The installation path requires Kubernetes [1]:

# Install k3s
curl -sfL https://get.k3s.io | sh -

# Install Helm
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash

# Add chart repos and install
helm repo add vsys-host https://vsys-host.github.io/helm-charts
helm install -f values.yaml shkeeper vsys-host/shkeeper

This isn’t inherently hard for someone comfortable with Linux and containers, but it’s a real jump from “run docker-compose up” tooling. If you’ve never touched Kubernetes, budget a full day to understand the toolchain before you even start configuring SHKeeper itself.

What you actually need [1][2]:

Setup	CPU	RAM	Disk
SHKeeper core only	4 cores	4GB	20GB SSD
+ BTC, LTC, DOGE, XMR full nodes	8 cores	8GB	100GB SSD

Full-node operation for BTC alone requires ~600GB of disk for the full blockchain. The Helm chart lets you enable full nodes per-coin, or you can rely on shared nodes (which introduces some trust assumptions and availability dependency).

SSL setup requires cert-manager installed separately via Helm — an additional step that isn’t automated in the base install [1].

What can go sideways:

• Running BTC and XMR full nodes is resource-intensive. A cheap 4-core VPS won’t cut it if you enable multiple full nodes.
• Blockchain sync time for BTC can take days on first setup.
• The project documentation is primarily in the README and a knowledge base on the official site — not the deep community documentation you’d find with BTCPay Server.
• At 538 stars, community support is thin. If you hit an edge case, GitHub issues and the VSYS Host team are your main options.
• The website advertises that VSYS Host server plans are the recommended hosting — which is fine, but creates a vendor dependency in practice for users who buy in.

Realistic time estimate for a Linux-comfortable engineer: 2–4 hours to a running instance with a couple of coins enabled, not counting blockchain sync time. For a non-technical founder: either budget a full weekend with documentation in hand, or pay for the Advanced plan.

---

Pros and Cons

Pros

• Zero transaction fees. No per-payment cuts. What your customer sends is what you receive, minus blockchain network fees that SHKeeper doesn’t control [1][2].
• Genuinely non-custodial. Private keys live on your server. No third party can freeze, seize, or delay your funds [1].
• No KYC. You don’t need to verify your identity or your customers’ identities to use the software [1].
• Strong stablecoin coverage. USDT and USDC across ERC20, TRC20, BEP-20, Polygon, and Avalanche — useful for merchants who want crypto payments but need USD-pegged settlement to avoid volatility [1].
• Monero support. One of the few payment processors that handles XMR without routing through a managed service [1].
• Partial payments and overpayment handling. These edge cases matter in practice and are often poorly handled by simpler solutions [1].
• Ready-made WooCommerce and WHMCS modules. Reduces integration work for the two most common use cases [1].
• Multipayout API. Useful for marketplaces or platforms that need to distribute crypto to multiple recipients [1].

Cons

• Kubernetes-only install. This is the single biggest barrier for non-technical founders. There’s no Docker Compose path documented in the README [1].
• 538 GitHub stars. Small project, small community. Compare to BTCPay Server’s 7,000+. If you hit a production bug, your support options are limited.
• GPL-3.0 license. More restrictive than MIT. If you want to embed SHKeeper in a commercial product or SaaS, you need to review GPL-3.0 obligations carefully. You may be required to open-source your integration code [1].
• VSYS Host conflict of interest. The project is built and maintained by a hosting company that profits from selling you servers and managed setup. This isn’t a disqualifier, but it’s a structural incentive worth understanding.
• No Lightning Network support. BTCPay Server supports Lightning for instant, low-fee BTC payments. SHKeeper appears to be on-chain only — data not available in official docs.
• Thin third-party review ecosystem. No independent deployment guides, community blogs, or review aggregators at time of writing. You’re largely relying on official documentation.
• Full-node resource requirements are heavy. Running BTC + XMR full nodes requires serious server specs and significant disk over time [1][2].

---

Who Should Use This / Who Shouldn’t

Use SHKeeper if:

• You’re a hosting company, SaaS provider, or e-commerce operator already processing meaningful crypto volume (say, $5K+/month) and paying 0.5–1% in gateway fees.
• You have a Linux engineer on staff or can hire one for initial setup.
• You’re specifically in the WHMCS or WooCommerce ecosystem — the ready-made modules make integration straightforward once the server is up.
• Privacy and non-custodial operation are requirements, not preferences. You need XMR support, no KYC exposure, or jurisdiction flexibility.
• You’re comfortable with Kubernetes or willing to learn.

Skip it (look at BTCPay Server instead) if:

• You need Lightning Network support for fast, low-fee BTC transactions.
• You want a large community, extensive documentation, and years of production deployments to draw on.
• You’re a non-technical founder and the $2,000/year Advanced plan budget isn’t justified.
• You only need BTC or a limited subset of coins — BTCPay Server is more mature for pure Bitcoin merchants.

Skip it (use a managed gateway) if:

• You’re just starting out with crypto payments and processing under $2,000/month. The transaction fees you’d save don’t justify the operational overhead.
• You need immediate setup — a managed gateway takes 30 minutes, SHKeeper takes a day minimum.
• Your compliance team requires an audited, SOC 2 certified provider.
• You’ve never managed a Linux server and have no intention of learning.

---

Alternatives Worth Considering

• BTCPay Server — the obvious comparison. Older, larger community, far more documentation, Lightning Network support, more integrations. Also open-source (MIT license). If you’re primarily Bitcoin-focused or want the most mature self-hosted option, BTCPay Server wins on ecosystem. SHKeeper’s edge is multi-coin coverage and stablecoin breadth.
• Coinbase Commerce — zero transaction fees, beginner-friendly, but custodial and requires Coinbase KYC. No Monero, no privacy coins.
• CoinGate — managed, easy setup, supports 70+ coins, but 1% transaction fee. Good for businesses that don’t want to manage infrastructure.
• NOWPayments — 0.5% fee, managed, broad coin support. Similar trade-off to CoinGate.
• BitPay — legacy brand, 1% fee, strong e-commerce integrations. Increasingly irrelevant as alternatives have caught up.
• OpenNode — Bitcoin and Lightning only, 1% fee, very clean integration. Better choice than SHKeeper if you only need BTC.

For a non-technical founder choosing between SHKeeper and BTCPay Server for self-hosting: BTCPay Server has dramatically more community support and a simpler onboarding path via Lunos or BTCPay Server’s own hosted option. For a technical team that specifically needs multi-coin support including stablecoins and XMR, SHKeeper is the stronger option.

---

Bottom Line

SHKeeper solves a real problem: merchant crypto payment processing is dominated by custodial services that take a cut and require KYC, and BTCPay Server doesn’t cover stablecoins and privacy coins as comprehensively. For a technical team running WooCommerce or WHMCS with meaningful crypto volume, SHKeeper’s zero-fee, non-custodial model makes strong economic sense. The math isn’t subtle — at $20K/month in volume, you recover a $20/month VPS cost in saved gateway fees inside the first 24 hours of the month.

The honest caveats: this is a small project maintained by a hosting vendor, Kubernetes-based installation is a real barrier for non-technical founders, and the community is thin enough that you’ll be reading source code when something breaks. If you have the technical depth to deploy it, the ongoing economics are compelling. If you don’t, the $2,000/year managed plan is expensive relative to just paying gateway fees until your volume justifies the switch.

If the deployment work is the blocker, that’s exactly what upready.dev handles for clients — one-time setup, you own the infrastructure, no recurring software fees.

---

Sources

Primary sources (all third-party review URLs provided returned unrelated content and could not be cited):

1. SHKeeper GitHub Repository and README — vsys-host/shkeeper.io, GPL-3.0, 538 stars. https://github.com/vsys-host/shkeeper.io
2. SHKeeper Official Website — homepage, pricing page, feature list, server requirements. https://shkeeper.io/
3. SHKeeper API Documentation — full REST API endpoint reference. https://shkeeper.io/api/
4. SHKeeper Knowledge Base — installation guides, coin-specific setup requirements. https://shkeeper.io/kb/launch/what-is-shkeeper