License

While not fully open source, Quiet's source-available license is actually more permissive than most viral open source licenses. You can use Quiet, learn from it, and change it just like open source software.

Unfortunately, there's no fair way for open source authors to build something valuable and sustainable while giving it away completely free to everyone. Traditional open source means any company can take years of your work, build profitable products with it, and contribute nothing back to development.

Copyleft licenses try to solve this problem by requiring everyone who uses the code to open source their entire application. But this creates an unfair burden on noncommercial users — individuals, students, and hobbyists who just want to keep their code private without having to navigate complex licensing requirements.

Quiet's dual-license approach lets individuals, students, and non-profits use, learn from, and adapt the software freely while ensuring that businesses who profit from it help fund continued development.

Yes. You can purchase a commercial license to unlock access to the private Discord where you can get help directly from me, the maintainer, and chat with other patrons of the project. My response times are usually within 24 hours.

I will always do my best to help you and I usually reply within 24 hours. However, that doesn't guarantee I'll be able to fix your problem every time.

Bugs should be reported on GitHub . For best results, please include a minimal reproduction with your report.

I prioritize bug fixes that affect paying customers. I try to submit fixes quickly, but some bugs are tricky and require more time, research, etc. I will communicate my progress so you're always aware of what's happening.

Features can be requested on GitHub . Please search before posting to prevent duplicate requests and use the 👍 reaction to vote.

I generally don't accept sponsorships for specific features. This lets me focus on what's best for the project. Quiet is the result of many years of experience and my commitment to painstakingly curating the project. I want people to sponsor it because they see the vision, not because they want to change it.

You can fork and modify the software for your own use, but creating a competing product and/or changing the license is prohibited.

It's best to not ship Quiet with open source projects, as that creates a complicated downstream licensing requirement for end users.

Framework SSR was created to solve problems introduced by client-side frameworks. When we moved to rendering everything with JavaScript, we broke SEO, social media previews, and page load performance. While framework SSR can be helpful in some scenarios, it's often misused to justify shipping massive JavaScript bundles that leave pages looking ready but completely unresponsive until everything loads and hydration completes.

The idea behind framework SSR is that fetching and hydrating can be done in the background before the user is likely to interact with the page. As such, it first sends the user a "fully painted" picture they can't actually do anything with while waiting for the browser to download and process a multi-megabyte bundle. However, it's become common to see 5+ seconds until TTI in the wild, leaving many users confused and frustrated.

Quiet isn't interested in supporting the framework SSR fallacy. As part of the platform, web components can be server-side rendered like all other HTML elements have since the early days of the Web. Just generate the appropriate HTML tags, import the components, and you're good to go.

If you're using Quiet's autoloader, it will efficiently fetch only the components you're using on the page. And to eliminate FOUCE , the most common reason people reach for SSR when using web components, Quiet provides some simple and effective tools.

The key to a great experience on the web isn't SSR, it's less JavaScript. If you're of the belief that you need framework SSR and all the needless complexity it brings to a project, this library isn't for you.

Component tag names, e.g. <quiet-button>, cannot be changed without modifying the source code due to the way tags are referenced in code and styles. Attempting to change tag names, e.g. by extending the associated classes, will cause unexpected breakages and isn't a supported feature of the library.

While components are written as classes, they aren't designed to be subclassed. This is neither supported nor an objective of the library and doing so will cause things to break. Instead, use composition when possible.

Because custom elements are registered globally, I don't recommend using Quiet in a micro frontend architecture unless you move it to the top of the stack. Avoid loading the library multiple times, as this will cause version conflicts and load more code than is necessary.