What Licensing Options Does Slint Offer for Commercial Products?

Slint is a declarative GUI toolkit for Rust, C++, JavaScript, and Python, and its own site shows it being used in commercial products — including OTIV autonomous rail vehicles, a WesAudio digital audio workstation plugin, an SK Signet EV charger HMI, and the Aava convolution plugin. Each of those customer entries on slint.dev carries a "Proprietary License" label, which tells you that shipping a closed-source commercial product on Slint is an accepted, documented use. What the site does not publish is a price list or a self-service checkout, so the practical answer for a commercial team is: commercial use is supported, but the exact terms depend on your product, and you confirm them with the Slint team rather than from a public pricing page.

What the "Proprietary License" label means

On slint.dev, the "Proprietary License" tag appears next to customer product pages, not as a general statement about the toolkit. Read it as a signal about how that customer ships Slint, not as the only license available to you:

• It indicates the customer distributes a closed-source product built with Slint.
• It implies a commercial arrangement exists between that customer and Slint, separate from any open-source license.
• It does not tell you the price, the seat count, the royalty structure, or whether support is bundled.

Because the label is attached per customer, you cannot infer your own terms from it. Treat it as evidence that the commercial path is real and in production, then get your own terms in writing.

The two-track model you should assume

The page evidence supports a dual-licensing pattern rather than a single license:

The important consequence: if your product can satisfy the open-source license conditions, you may not need a commercial agreement at all. If it cannot — for example, you ship a closed-source plugin, charger HMI, or vehicle UI — the commercial track is the one the customer examples point to.

What to confirm before you ship

The site gives you no pricing signals, no payment platform, and no license comparison table, so these are the questions to settle with Slint directly. Frame them around your actual product:

1. Distribution model — are you shipping a binary, a library linked into someone else's product, or a hosted service? Each can fall under different terms.
2. Closed vs. open source — will your Slint-based UI code be published, or kept proprietary?
3. Target platforms — embedded, desktop, mobile, or web. The site markets one codebase across these, but confirm your specific targets are covered.
4. Support and updates — the customer quotes emphasize responsiveness and support; check whether that is part of the commercial agreement or a separate item.
5. Volume and product count — one product or a family of products, and how many devices or seats.

How to get the right license

There is no pricing page or checkout flow on slint.dev, so the route is direct contact:

• Start from the Slint site and use its contact or sales channel to describe your product.
• Bring the answers to the five questions above; a specific description gets you a specific quote faster than a generic inquiry.
• Ask explicitly which license applies to your case and request the terms in writing before you commit engineering time.
• If you are evaluating first, the demos and the customer product pages show what the toolkit does in production — use them to judge fit, then negotiate terms.

The short version: Slint supports commercial, closed-source products, and its own site names four companies doing exactly that under a proprietary license. It does not publish prices or terms, so the licensing decision is a conversation with Slint, not a download-and-go step.