Zoneless: Open-source Stripe Connect alternative for marketplace payments.

What it does

Zoneless is an open-source payment platform designed as an alternative to Stripe Connect for marketplace operators. It handles seller onboarding, payouts, and cross-border payments. The platform uses stablecoins (USDC) to move money between parties. It offers the same API as Stripe, so existing integrations can be adapted with minimal code changes. The source code is published under the Apache 2.0 license and can be self-hosted.

Who it is for

Marketplace operators and platform companies that process payouts to many sellers across different countries. The builder positions it as an alternative for those frustrated with Stripe Connect's fees and country limitations. It targets founders who want control over their payment infrastructure and may operate in markets Stripe supports less comprehensively. Companies already using Stripe can add Zoneless as a secondary payment option without replacing their existing setup.

Pricing

Zoneless charges approximately $0.002 per payout plus a $0.25 cross-border fee, with payout settlement in seconds. No monthly account fees. A comparison table on the site shows estimated annual costs: Stripe Connect at $40,500 per year for 12,000 payouts, PayPal Payouts at $19,500 per year, and Zoneless at approximately $26 per year under the same scenario (1,000 monthly payouts at $50 average, 50% international).

How it stands out

The open-source model and self-hosting capability are distinct from Stripe and PayPal. Global coverage extends to 220+ countries and regions. Settlement happens in seconds rather than days. The stablecoin approach eliminates many traditional cross-border and currency conversion fees. Stripe API compatibility allows easier migration. The builder reports 74% of new sellers on the operator's own marketplace selected Zoneless over Stripe Connect, suggesting real competitive adoption within a production environment.

What a founder should check

First, verify the long-term stability and security implications of running an open-source, self-hosted payment system versus relying on Stripe's institutional support and compliance infrastructure. Second, investigate the liquidity and counterparty risk inherent in stablecoin-based payments, especially during market stress. Third, examine the actual switching costs—while the API is similar, full migration requires testing, seller education, and potentially supporting both systems during transition, which may offset the fee savings for some operators.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.