For module developers and publishers
Wayseer marketplace publisher agreement
Version: 2026-10-04
This agreement is between you and Wayseer LLC, a Utah limited liability company ("Wayseer", "we", "us"). It covers the developer certificates we issue you and the modules you submit to the Wayseer marketplace, where we build them from your public source, sign them and offer them to users of the Wayseer desktop app ("the Wayseer app"), our licensed product. If your license is a business license, you accept this agreement for your organization, and "you" means the organization as well as you.
You accept this agreement when you request a developer certificate, by ticking the box on the request form. We issue no certificate before you do. For a business license, a person who may bind your organization must also sign this agreement before we issue the certificate. It applies to every certificate we issue you and every version you submit. You must be 18, or the age of majority where you live.
The Wayseer end-user license still governs your own use of the Wayseer app, your license key and your developer certificate. Where it and this agreement conflict about your marketplace modules, this agreement governs.
1. Who may publish
To publish, you need:
- a paid Wayseer license key, personal or business, that covers the current release of the Wayseer app, and a developer certificate we issued under it; and
- a public repository holding the module's source.
Each module's ID starts with your license's namespace (acme/snowflake). The kinds a module reports use a namespace we allocate to that module (section 7).
2. What you submit
For each version you send us the repository URL and a tag. We record the full commit the tag points to and build only that commit; moving the tag later changes nothing we built. You also send the module's manifest, which declares its entity kinds, its actions and what each changes, the network endpoints it reaches, whether it reads the keyring, and the source license.
The manifest must be complete and true. The Wayseer app refuses actions and kinds a module's manifest doesn't declare, but it does not enforce the network endpoints or keyring use; for those, users rely on your word.
3. What you let us do
You give us a worldwide, non-exclusive, royalty-free license, for as long as this agreement lasts and as section 11 says after, to:
- copy and keep your source at each submitted commit, for building, review and audit;
- build it, run it and its tests, and sign the result with our marketplace key;
- copy and distribute the built binaries, the manifest, the build recipe and a link to your source, to anyone, from the marketplace and its mirrors;
- show your module's name, description, homepage, publisher name and manifest on the marketplace and in the Wayseer app; and
- withdraw any of them, as section 8 says.
You also give each user who gets one of those binaries the right to install and run it with the Wayseer app, at no charge, whatever your source license says about binaries. Your source license governs everything else about your source.
4. Your source stays public
The source at every commit we published must stay publicly available, under the license the manifest names, for as long as that version is in the marketplace. If it stops being available, we may withdraw the version. The source license may be open source or source-available, as long as it lets anyone read the code and lets us do what section 3 says.
5. No charge
Every marketplace module is free to every licensed user of the Wayseer app. You may not:
- charge for the module, a version of it, or any feature in it, or ask a user for a key, account or payment to unlock any part of it;
- show advertising in what the module reports or does; or
- expect any payment from us. There is no revenue share, fee or other pay for anything under this agreement.
The marketplace links only to your module's homepage. It shows no donation, sponsor or other payment links.
6. Your promises
You promise that:
- you wrote the module, or have the right to publish all of it under this agreement, and its dependencies' licenses allow what section 3 says; you keep their notices with the source;
- the module does nothing its manifest doesn't declare, and nothing harmful: no malware, no hidden access, nothing that harms a user's systems or data beyond the actions they confirm, nothing that gets around the Wayseer app's license checks, and nothing that tries to reach other modules' data or kinds outside the module's own namespace;
- the module connects only to what the user configures it to connect to, and sends nothing about the user, their systems or their use of the module to you or anyone else unless the user turns that on;
- the source is readable: no obfuscated or minified code, and no code fetched at build or run time that isn't in the submitted commit or its pinned dependencies; and
- you are not on a US restricted-party list, and publishing the module does not break US export control or sanctions law.
You are responsible for the licenses of everything your module contains, whether you knew of it or not, including its dependencies.
7. Namespaces
A module's namespace is allocated by us, belongs to the marketplace and not to you, and is not transferable. It stays with the module even after the module is withdrawn, and we never give it to anyone else. You may not use a namespace you weren't allocated, or our reserved ones.
8. Review and withdrawal
We decide whether to publish a version, after reviewing its source and building it, and we may decline without giving a reason. We have no duty to review within any time.
We may withdraw a version, a module or your developer certificate, at any time and without notice, for any reason we judge protects users, including:
- a security problem, or a breach of section 6;
- a module that is unmaintained, or that destabilizes the Wayseer app;
- a problem with you as publisher, such as an exposed developer key or a breach of this agreement;
- a substantiated complaint that the module infringes someone's rights; or
- a finding that the module breaks the license of anything it contains, whether you knew of it or not.
A withdrawn version or module is no longer offered for download, and the Wayseer app stops it on every install when it next fetches our list of withdrawals, or in a later release that includes it. We publish what we withdraw, and the reason users see. Where we can, we tell you first and give you a chance to fix it.
9. Vulnerabilities and keys
- If you learn of a vulnerability in a published version, tell us at [email protected] within 3 days, and before you disclose it publicly. Fix it or ask us to withdraw the version, and work with us on what users are told.
- If your developer key is lost or may be exposed, tell us at once so we can withdraw its certificate. Withdrawing it withdraws every marketplace module you submitted under it.
- After we withdraw a certificate because its key was lost or exposed, you may request a new certificate for a new key, under this agreement, and submit your modules again under it.
10. Names and support
- You may say your module is "available in the Wayseer marketplace". You may not name a module or project with "Wayseer", use our logo, or suggest we made or endorse it.
- You support your module's users, as you choose. We forward users to your homepage, and we have no duty to support your module.
11. Ending
You may end this agreement at any time by telling us. We may end it at any time by telling you, and at once if you breach it. Either way:
- we stop listing your modules, and they can no longer be downloaded from the marketplace;
- copies users already installed keep running unless we withdraw them, and section 3's rights continue for those copies, for the build records we keep, and for our list of withdrawals;
- we issue you no further developer certificates; and
- sections 3 (as above), 6, 7, 11 to 15 still apply.
If your Wayseer license ends or is not renewed, your published versions stay, but we accept no new versions until a license covers the current release again. Ending your license for a breach may end this agreement too.
12. No warranty, both ways
YOU PROVIDE YOUR MODULES AND WE PROVIDE THE MARKETPLACE "AS IS". TO THE FULLEST EXTENT THE LAW ALLOWS, EACH OF US DISCLAIMS ALL WARRANTIES TO THE OTHER, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. Signing a module means we checked where it came from, not that we vouch for what it does.
13. Limit of liability
TO THE FULLEST EXTENT THE LAW ALLOWS, WE ARE NOT LIABLE TO YOU FOR INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL LOSS, OR LOST PROFITS, DATA OR BUSINESS, INCLUDING FROM DECLINING OR WITHDRAWING A MODULE. OUR TOTAL LIABILITY TO YOU UNDER THIS AGREEMENT IS LIMITED TO US$50.
14. Claims about your module
You will defend us against, and pay what we must pay because of, any claim by someone else that your module infringes their rights, or that arises from your breach of section 6. We will tell you about the claim promptly, let you control its defense, and help at your cost. You may not settle it in a way that binds us without our consent.
15. General
- Changes. We may publish a new version of this agreement, dated at the top, and ask you to accept it online before your next certificate or submission. Versions you already submitted stay under the version you accepted for them, except that section 8 always applies.
- Whole agreement. This agreement and the Wayseer end-user license are the whole agreement about developer certificates and the marketplace.
- Severability. If a court finds part of this agreement unenforceable, the rest stands, and that part is enforced as far as it can be.
- Assignment. You may not transfer this agreement, or a module's listing, without our written consent. We may transfer it to a successor to our business.
- Notices. We write to the email address on your license. You write to [email protected], or [email protected] for section 9.
- Your details. We keep your name, email, license ID and certificate ID to run the marketplace. We publish your publisher name, namespace and certificate ID with your modules, never your license ID or email.
- Law. This agreement is governed by the law of the State of Utah, without regard to its conflict-of-law rules, and disputes go to the state and federal courts in Utah.
Questions about this agreement: [email protected].
To accept it, request a developer certificate: the request form asks you to.