LicenseManager

Blog

How to sell a Tauri app

7 min read

The Tauri logo, an arrow and a price tag

You built a desktop app with Tauri: a Rust core, a web frontend, and installers a few megabytes big for macOS, Windows and Linux. People like it. Now you want them to pay for it, and Tauri’s documentation covers how to build and distribute the app, not how to charge for it.

Selling a Tauri app comes down to five decisions: where you sell (app stores or your website), how you price it, who takes the payment, how the app checks that the person running it paid, and how you sign and update it so customers trust it. This guide goes through each one, in the order you’ll meet them, with what’s specific to Tauri.

Decide where you sell: app stores or direct

Most paid Tauri apps are sold from their own website. App stores are an option too, and some apps do both.

Through app stores

Tauri can build for the Mac App Store and the Microsoft Store, and Linux users can get your app from Flathub or the Snap Store. Stores handle payments, taxes and discovery, and customers trust them. In exchange:

  • A commission of 15% to 30% on every sale. Apple charges 15% under its Small Business Program, for developers who make less than $1 million a year from it, and 30% otherwise.
  • Sandboxing. Mac App Store apps run in the App Sandbox. Commands that read arbitrary files, spawn processes or talk to other apps need entitlements, or don’t work at all.
  • Review of every update, which delays bug fixes.
  • No paid Linux store at scale. Flathub and the Snap Store distribute free apps well; selling there is rare.
  • No customer relationship. The store knows your customers, you often don’t get their email.

Directly from your website

Selling directly means a checkout on your website, a download link per platform, and a way for the app to know the customer paid. You keep most of the revenue and the customer’s email, you ship updates when you want, and you can sell to Linux users too.

You also take over what the store did: payments, taxes, licensing, code signing and updates. The rest of this guide covers those.

App stores and direct sales of a Tauri app compared on commission, sandboxing, review delays, customer relationship and Linux

Selling both ways is common on the Mac: a store version for people who search the Mac App Store, and a direct version, often with team licenses or a trial, for everyone else. See Mac App Store vs selling direct for the trade-offs.

Pick a pricing model

A Tauri app runs on the customer’s computer and doesn’t need your server to work. That opens more pricing models than a web app has:

  • Perpetual license: pay once, use forever. Customers like it, but revenue stops when sales do.
  • Perpetual with a year of updates: the customer keeps the version they bought forever, and pays again for updates after a year. A good middle ground, and common for developer tools.
  • Yearly or monthly subscription: recurring revenue, but desktop users push back on subscriptions more than web users, especially for apps that work offline.
  • Free with a paid tier: the free version spreads the app, the paid one unlocks features.

Add a free trial to any of these: few people pay for a desktop app they haven’t tried. See how to add a free trial to a Tauri app.

Price per person, not per installation. “One person, up to 3 computers” matches how people work: a desktop, a laptop, and a new computer every few years.

Choose how you take payments

Stripe, or another payment processor

Stripe takes the payment and pays you, for a fee per transaction. Payment Links and Checkout give you a hosted payment page without writing a backend.

You’re the seller, so sales taxes are yours: VAT in the EU and UK, GST in Australia, sales tax in some US states. Stripe Tax calculates and collects them, but registering and filing in each country where you pass the threshold is still on you.

A merchant of record

A merchant of record, like Paddle, Stripe Managed Payments or FastSpring, sells your app on your behalf. It’s the seller for tax authorities, so it collects and pays sales taxes worldwide, for a higher fee than Stripe, often around 5% plus a fixed amount per sale.

A solo developer selling worldwide saves a lot of paperwork with a merchant of record. A company that already handles taxes pays less with Stripe. Paddle vs Stripe compares the two, and Paddle alternatives for Mac apps the other options; most of it applies to any desktop app. If you pick Paddle, the checkout flow is in Paddle Checkout in a Tauri app.

Open the checkout in the browser

Whatever you pick, open the payment page in the customer’s browser, with the opener plugin, rather than in a Tauri window: their saved cards, Apple Pay and password manager are there, and the address bar shows a domain they trust. Stripe Checkout in a Tauri app builds the whole flow, with a deep link that brings the customer back to the app after paying.

Add license keys

Once you sell directly, your app needs to know whether the person running it paid. A license key is the standard answer:

  1. The customer pays.
  2. A key is created and emailed to them.
  3. They paste it in your app, which checks it with a server and unlocks.

The server is what makes keys worth having: it limits the number of computers, expires keys when a subscription ends, and revokes them after a refund. The app has to keep working offline, and keep the key across updates.

Tauri has one advantage over Electron here: a Rust core. Your frontend’s JavaScript ships as text and can be edited; your Rust commands are compiled into the binary. Check the license in Rust, and gate paid commands there, so editing the webview unlocks nothing.

A sale of a Tauri app in four steps: payment, license key email, activation in the app, validation in the Rust core

The full integration, from the plugin to offline tokens, is in how to add license keys to a Tauri app. To limit how many computers a key unlocks, the app needs a stable identifier for each computer: see how to get a unique machine id in Tauri.

Sign your app

An unsigned app is a hard sell:

  • On macOS, Gatekeeper won’t open an app that isn’t signed with a Developer ID and notarized by Apple. Customers have to find the override in System Settings, and most give up.
  • On Windows, SmartScreen shows “Windows protected your PC” on unsigned downloads, with the Run button hidden behind “More info”.

Signing costs an Apple Developer Program membership ($99 a year) and a Windows certificate or signing service, plus some setup in tauri.conf.json and your CI. For a paid app, it’s not optional. See how to code sign and notarize a Tauri app.

Ship updates automatically

Customers who paid expect fixes without downloading a new installer. Tauri’s updater plugin checks a JSON file or an endpoint you host, downloads the new version, verifies its signature, and installs it. See Tauri auto updates.

If you sell a year of updates, the updater and the license must agree: a customer whose year of updates ended shouldn’t install a version their license doesn’t include, or should at least be told why it won’t unlock.

Build the website

Your website does the selling. It needs at least:

  • A page that explains the app, with screenshots or a short video. Tauri’s small download size is worth saying out loud.
  • A download button per platform, or one that detects it.
  • A pricing page with a buy button for each plan.
  • A way to find a lost key, ideally self-service: it’s the most common support request of any app sold with keys.

What to build, and what to use

Each piece above exists as a service: Stripe or a merchant of record for payments, the Tauri updater with a static file host for updates, and Apple and Microsoft’s tools for signing. The piece most developers end up building themselves is the license server: a database of keys, a webhook that creates them on payment, signed tokens for offline use, machine limits, and a page where customers find their key.

LicenseManager is that piece. Connect your Stripe or Paddle account, and each purchase creates a license key and emails it, with no backend of your own. The Tauri SDK is a Rust plugin with typed JavaScript bindings: it validates keys, limits machines, works offline with signed tokens, and detects a clock set back. Customers find their key and free old computers in the customer portal, and trial licenses use the same code as paid ones.

Wrapping up

Selling a Tauri app takes a pricing model, a payment provider, license keys checked in Rust, code signing, and auto updates. None of them is hard on its own, and most of them you don’t build yourself.

Start with the checkout and the license key: they turn a free download into a paid app. Adding license keys to a Tauri app walks through the integration, and the Tauri licensing page shows how it fits with Stripe. If you also have an Electron version, how to sell an Electron app covers what differs.

More articles