Moatless is a marketplace for source code, and this is the code that runs moatless.store. Developers list codebases from their GitHub repositories or any git URL and set a price. Buyers pay once, or subscribe to updates, and clone the code with git. Coding agents can do all of it through an MCP server.

Features

• Listings. Sellers connect a GitHub repository with a GitHub App, or use any HTTPS git URL with credentials stored encrypted. Each listing has a description, screenshots for desktop, tablet and phone, categories, a tech stack, the services the code needs to run, a demo link, and share cards drawn from the listing for posting it.
• Releases. Each release is built from a branch, tag or commit into a single commit on top of the last one, without the seller's history and without anything in .moatlessignore. Publishing a GitHub release or pushing a tag can publish one automatically, and the files attached to a GitHub release can be copied for buyers to download.
• Delivery over git. Buyers clone and pull from a git URL with an API key as the password, and each buyer is served the newest release they're entitled to. Downloads are recorded as proof of delivery for disputes.
• Payments. Stripe Checkout with the platform as the merchant of record, and sellers paid through Stripe Connect Express accounts every Friday, after a 10-day hold for refunds and fraud. A platform fee, founder codes for lower rates, refunds and disputes, and optional Stripe Tax.
• Subscriptions to updates, charged only for the months or years in which the seller publishes a release (Stripe Billing meters), with adding updates after buying, and the confirmation and yearly reminder emails California's automatic renewal law requires.
• For buyers. A library with clone instructions and downloads, wishlists, reviews rated on code quality, documentation, design, performance and updates, seller replies, emails when new releases come out, and review reminders with one-click unsubscribe.
• For sellers. Seller pages and a sellers directory, an earnings dashboard, payouts, and a selling page that updates live as sales and builds happen.
• Coding agents. An MCP server that agents sign in to with OAuth, with tools for selling and buying, a setup page and guide written for agents, a Claude Code plugin, and an entry in the official MCP Registry.
• Search engines. Public pages are rendered on the server, with a sitemap, structured data, and IndexNow, so Bing and others hear about changes.
• Admin. Stats, release builds, error tracking, Oban Web, and founder codes.
• Analytics. PostHog, with first-touch attribution from UTM tags, and a cookie banner.

Built with

Elixir and Ash (AshPostgres, AshAuthentication with its OAuth 2 server, AshOban, AshAi, AshTypescript, AshStorage, AshPhoenix), Phoenix, PostgreSQL and Oban Pro; a React front end (TanStack Router and Query) over AshTypescript's RPC and typed channels, rendered on the server with Node, with Tailwind CSS and Vite.

What you need

Elixir 1.17 or later, PostgreSQL, Node and git, plus an Oban Pro license, since background jobs use Oban Pro. In production, you'll also need a Stripe account with Connect, a GitHub App, S3-compatible storage, and Resend for email. PostHog is optional. It's set up to deploy to Fly.io with a Tigris bucket. The README covers configuration, setting up Stripe and the GitHub App, and deploying, and AGENTS.md describes how it all fits together.

What the license allows

You can use and change the code for yourself or your organization, including running it to sell your own products, such as a store for your own codebases, templates or apps. You can also copy parts of it into your own products, as long as they aren't a competing product: a public marketplace, store or directory where other people sell or distribute code or software.

What you can't do

• Run Moatless, or anything built from it, as a marketplace for other people's code, whether it's hosted, downloadable, or offered as a service or an API.
• Share, resell, sublicense or re-list the source code, or push it to a public repository.
• Use the Moatless name, logo, brand or domain, its MCP Registry listing or Claude Code plugin, or suggest that WeBuilt LLC, which operates Moatless, endorses your product.
• Use the original deployment's servers, GitHub App, Stripe account or credentials.

The full terms are in LICENSE.md, which ships with every release.

Included, and not

Included: the full source of the server and the web app, with tests, a README, AGENTS.md, and skills for coding agents.

Not included: the Moatless name, logo and brand (the README lists what to replace before you deploy it), a hosted instance, credentials for any service, or an Oban Pro license.