1. About This Agreement
1.1 Who this is between. This License Agreement (the "Agreement") is between Teyra LLC ("Teyra," "we," "us"), a limited liability company formed in Wyoming, United States, operator of WebberUI at webberui.com (the "Site"), and you, the individual or entity that obtains Components from WebberUI ("you" or "Licensee"). If you obtain Components on behalf of a company or other entity, you represent that you have authority to bind that entity, and "you" means that entity.
1.2 What this Agreement covers. This Agreement governs the code you obtain from WebberUI — the components, templates, sections, and kits themselves. Your use of the Site and its online services (accounts, downloads, the composer, search) is governed by the Terms of Service at /terms. Billing and refunds are covered by the Refund & Billing Policy at /refunds. How we handle personal data is covered by the Privacy Policy at /privacy, the Cookie Policy at /cookies, and the Subprocessors list at /subprocessors.
1.3 Relationship to the LICENSE file. The LICENSE file shipped in our repositories and npm packages (including @webberui/mcp) is a plain-language summary of this Agreement. This Agreement, published at /license, is the complete version. If a summary and this Agreement ever differ, this Agreement controls — except that a separate written agreement signed by both you and Teyra prevails over everything, including this Agreement.
1.4 The version in effect when you obtained the code governs. Each copy of a Component you obtain is licensed under the version of this Agreement in effect at the time you obtained it. If we later change this Agreement, the changes apply only to Components obtained after the change. No future change will reduce your rights in code you have already obtained.
1.5 Our promise of honesty. We wrote this Agreement to be read. Where we make a promise on the Site — such as "installed components never phone home" — this Agreement is written to keep that promise, not to quietly take it back.
2. Definitions
2.1 "Components" means the UI components, full-page templates, composable sections, starter kits, theme files, and the associated source code, styles, types, documentation comments, and assets that Teyra makes available through the Registry, whether Free Content or Pro Content. This definition — which expressly includes theme files and associated assets — is the authoritative definition of "Components"; the Terms of Service at /terms incorporate it by reference.
2.2 "Free Content" means Components that Teyra makes available at no charge, with no payment, no account, and no sign-in required.
2.3 "Pro Content" means Components whose download requires a Pro entitlement — a paid subscription, a valid License Key, or a qualifying promotion (see Section 10).
2.4 "Registry" means the distribution endpoints through which Teyra delivers Components, including the registry at webberui.com, the composer and kit endpoints, and installs performed via the webberui CLI or the @webberui/mcp package.
2.5 "End Product" means an application, website, or other product you create that incorporates Components in compiled, integrated, or deployed form — that is, a product whose users receive a functioning application or site, not the Components themselves as reusable source building blocks.
2.6 "Organization" means a single company, team, or other legal entity, together with its employees and the contractors working on that entity's projects. One Organization means one entity: a parent company and an unaffiliated client, community, or the general public are not the same Organization.
2.7 "Derivative Work" means any work based on or derived from the source code of the Components, including modifications, extensions, ports or translations to other frameworks or languages, and code produced by refactoring or transforming Component source — with or without AI tools, and regardless of how heavily the code was transformed.
2.8 "License Key" means a long-lived key, or an account-based credential, used to authorize downloads of Pro Content from the Registry.
2.9 "Service" has the meaning given to it in the Terms of Service at /terms, where it is authoritatively defined; as used in this Agreement, the Service includes the Site and the Registry.
3. License Grant
3.1 The grant. Subject to this Agreement, Teyra grants you a non-exclusive, worldwide, perpetual (as to each copy of a Component you have obtained), non-transferable, non-sublicensable license — except as expressly permitted in Sections 4, 6, and 16.6 — to use, reproduce, and modify the Components, to create Derivative Works, and to distribute Components and Derivative Works as integrated parts of End Products.
3.2 The core promise: your installed code is yours to run, forever. This is the heart of WebberUI's license, and every part of it is binding on us:
(a) Once a Component's code is copied into your project, you may keep using it, running it, and shipping it indefinitely. The license to that copy does not expire.
(b) Installed Components never contact our servers. They contain no telemetry, no usage reporting, no runtime license validation, no remote-disable ("kill switch") mechanism, and no expiry mechanism. We could not remotely disable your components even if we wanted to — no such mechanism exists in the code we deliver.
(c) Downtime or discontinuation of the Service never affects your deployed End Products. If webberui.com is unreachable, or WebberUI shuts down entirely, everything you have already installed and shipped keeps working exactly as before.
(d) Lapse of a subscription, the end of a promotion, and even termination of this Agreement under Section 13 do not reach End Products you have already deployed or delivered to third parties.
3.3 Free and Pro carry identical usage rights. The permitted and prohibited uses in Sections 4 and 5 are the same for Free Content and Pro Content. A Pro purchase buys more content — additional components, templates, sections, kits, and future updates — not broader usage rights over any given Component. (Organization plans additionally include the organization-level rights described in Section 6.3.)
3.4 No attribution required. You are never required to credit WebberUI or Teyra in your End Products, on either tier. Attribution is welcome; it is not a condition.
4. Permitted Uses
Subject to Section 5, you may:
4.1 Use Components in an unlimited number of your own products, websites, and applications, commercial or non-commercial.
4.2 Use Components in client work, for an unlimited number of clients and projects, and deliver the integrated result to your clients:
(a) Delivering a finished, integrated site or application to a client is not redistribution of source under Section 5.
(b) Client pass-through sublicense. Upon delivery of an End Product to a client, that client automatically receives a non-exclusive, perpetual sublicense to use, host, maintain, and modify the Components included in that End Product solely as part of that End Product — including through the client's own employees and contractors — subject to the prohibitions in Section 5. Reuse of the Components in other, unrelated projects requires the client's own entitlement.
4.3 Modify Components freely — source code, animation, styles, structure — to any extent.
4.4 Use AI coding agents and assistants to modify, extend, refactor, or build with Components. (See Section 8 for how the license applies to AI-derived code.)
4.5 Distribute Components and Derivative Works in compiled, integrated, or deployed form as part of End Products, including commercially.
4.6 Keep Components and Derivative Works in private repositories for your own products and client projects.
4.7 Delete the informational license header described in Section 9 from delivered source without affecting any of your rights.
5. Prohibited Uses
You may not, on either tier:
5.1 Redistribute the source. You may not redistribute Component source code, or any substantial Derivative Work in source form, to the public or outside your Organization — including via public repositories, gists, code archives or zip files, forum or chat pastes, or any other channel that makes the source available as source. A public GitHub repository containing WebberUI-derived components is not allowed, even heavily modified; a private repository for your own product is fine.
5.2 Repackage as a developer asset. You may not repackage Components or Derivative Works as a component library, UI kit, template pack, SDK, design-system product, or any similar reusable developer asset, whether offered for free or for payment.
5.3 Sell on marketplaces. You may not list or sell Components or Derivative Works on template marketplaces, theme stores, or other resale channels.
5.4 Offer components as a pickable asset library. If you build a site builder, SaaS platform, or similar product: it is allowed if your end users receive generated, finished sites or applications. It is not allowed if your product offers the Components themselves as a selectable, reusable asset library for your users to pick from. That use case requires a separate agreement — contact official@teyrallc.com.
5.5 Share License Keys outside your Organization. See Sections 6 and 7.
The line that runs through all of Section 5: your users and clients should receive your product, not our components.
6. Organizations and Teams
6.1 Unlimited seats within one Organization. An organization subscription or a shared License Key covers an unlimited number of people within one Organization — its employees and the contractors working on that Organization's projects. There are no per-seat counts in this Agreement.
6.2 No cross-organization sharing. License Keys and Pro account access may not be shared across organizational boundaries — not with other companies, not with a community, not with the public. One Organization, one entitlement.
6.3 Organization-plan rights. Organization plans may include rights that personal plans never include: a commercial-redistribution license (whose scope is defined by the applicable plan terms or a separately signed contract), a private registry, and priority support. Organization-only redistribution rights apply only to distribution that occurs while an organization plan is active; End Products already delivered are never retracted. A personal (individual) plan does not include any redistribution rights beyond Section 4.
6.4 Client work is not key sharing. Delivering an End Product to a client under Section 4.2 is permitted. Giving a client your License Key is sharing outside your Organization and is not.
7. License Keys and Install Credentials
7.1 Keys are used only at download time. A License Key authorizes downloads from the Registry — for example, sent as an Authorization header by the webberui CLI. Installed code contains no key, performs no key checks, and never transmits anything. Short-lived signed install links (valid for at most 15 minutes, limited to a single resource) work the same way: they authorize one download and do nothing afterward.
7.2 Keep keys confidential. You are responsible for keeping License Keys confidential within your Organization and for use of the Registry under your keys and accounts.
8. AI-Assisted Development and Machine Learning
8.1 AI-assisted modification is expressly permitted. Using AI coding agents and assistants to work with Components is a normal, supported use of WebberUI, not a gray area.
8.2 AI-derived code remains covered. A Derivative Work remains subject to this Agreement even after heavy AI-assisted refactoring, restyling, or translation to another framework or language. The degree of transformation, and whether a human or an AI performed it, does not remove code derived from Component source from the scope of this Agreement. We acknowledge genuine gray areas exist at the far end of transformation; if you are unsure whether something you have built is still a Derivative Work, email official@teyrallc.com and ask — we answer.
8.3 Machine-learning training restriction. You may not use Component source code (Free or Pro) to train, fine-tune, or otherwise develop a machine-learning model whose purpose or foreseeable effect is to generate competing component libraries, UI kits, or template collections. To be unambiguous: this Section restricts training whose purpose or effect is to produce a competing component library, UI kit, or template collection. It does not prohibit you from using AI coding assistants on Components in the ordinary course of building your own products — that use is expressly permitted by Section 4.4.
8.4 Building with AI is not training. Using Components as context for an AI tool while building your End Products (for example, letting a coding agent read installed component source in your repository) is ordinary permitted use under Section 4, not training under Section 8.3.
9. License Header Comments
Pro source delivered from the Registry carries a visible license comment at the top of each file, identifying the component name, target path, retrieval date, and the license URL. This header:
9.1 is informational only — it identifies the code's origin and license;
9.2 contains no licensee identity and performs no tracking of any kind;
9.3 executes nothing — it is a comment; and
9.4 may be deleted without affecting the code's behavior or any of your rights under this Agreement.
Free Content files may also include an informational license-pointer header. Like the Pro header, it is informational only, executes nothing, and may be deleted without affecting the code's behavior or any of your rights under this Agreement.
10. Subscriptions, Lapse, and Promotions
10.1 What a Pro subscription buys. An active Pro entitlement gives you the ongoing right to download Pro Content from the Registry and to receive newly added Pro items and updates while the entitlement is active. Billing terms are in the Refund & Billing Policy at /refunds.
10.2 What happens when a subscription lapses. If your subscription is canceled or expires, you lose the right to download new Components and updates. That is all you lose. Every Component you obtained while entitled remains licensed under Section 3 — perpetually, with nothing disabled, because nothing can be disabled (Section 3.2(b)).
10.3 Promotions. From time to time we may run promotions that grant Pro access without payment — for example, a launch promotion granting all Pro Content free upon sign-in. Components obtained during a promotion are licensed on exactly the same perpetual terms as purchased Pro Content. When a promotion ends, only future free downloads stop; Components you installed during the promotion are yours under Section 3.2 and are never retroactively revoked.
10.4 No retroactive changes. As stated in Section 1.4, later changes to pricing, plans, or this Agreement never reduce your rights in Components you have already obtained.
11. Third-Party Open-Source Software
11.1 Components are designed to be used with, and depend on, third-party open-source software — including React, Tailwind CSS, and the other packages listed in THIRD_PARTY_NOTICES.md — each of which is licensed under its own terms. Nothing in this Agreement limits any rights you have under those licenses. This Agreement covers only Teyra's own code.
11.2 The Components are original implementations by Teyra. Generic pattern names used in the catalog (such as bento grid, marquee, or carousel) are industry-standard descriptive terms, not any vendor's property, and their use implies no affiliation with or endorsement by any third party.
12. Ownership
12.1 Teyra retains all right, title, and interest in and to the Components, including all copies and the copyrights in them. This Agreement is a license, not a sale.
12.2 You own your End Products and your original contributions to Derivative Works, subject to Teyra's continuing ownership of the underlying Components.
12.3 No trademark license. This Agreement grants no rights in the "WebberUI" or "Teyra" names or any associated branding.
13. Term and Termination
13.1 Term. This Agreement takes effect for you when you first obtain a Component and, as to each obtained copy, continues perpetually as described in Section 3.2.
13.2 Termination for material breach. We may terminate this Agreement as to you if you materially breach it — in particular Sections 5, 6.2, 7.2, or 8.3 — and, where the breach is curable, fail to cure it within thirty (30) days after we notify you at an address associated with your account or purchase. We will not terminate for convenience, and we will never terminate to claw back the core promise in Section 3.2.
13.3 Effect of termination. Upon termination: (a) your right to obtain new Components from the Registry ends; (b) you must stop the breaching conduct and cease making new uses of the Components going forward; but (c) End Products already deployed, or already distributed or delivered to third parties, are not affected — your clients and users keep what they have, your live sites keep running, and, as a technical matter, nothing we deliver contains any mechanism to interfere with them (Section 3.2(b)). Termination operates as a legal remedy against continued breach, never as a switch on shipped products.
13.4 Survival. Sections 3.2 (as to deployed and delivered End Products), 9, 11, 12, 13.3, 14, 15, and 16 survive termination.
14. Warranty Disclaimer
14.1 THE COMPONENTS ARE PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY LAW, TEYRA DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT, AND ANY WARRANTY THAT THE COMPONENTS WILL BE ERROR-FREE OR MEET YOUR REQUIREMENTS.
14.2 In plain language: we work hard on this code, but you are responsible for reviewing, testing, and validating Components in your own product before you ship them. Free Content in particular is provided at no charge and on that basis.
14.3 This section is intended to be consistent with the warranty terms in the Terms of Service at /terms; if they conflict as to the Components, this Agreement controls (Section 1.3).
15. Limitation of Liability
15.1 TO THE MAXIMUM EXTENT PERMITTED BY LAW, TEYRA WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST DATA, OR BUSINESS INTERRUPTION, ARISING OUT OF OR RELATING TO THE COMPONENTS OR THIS AGREEMENT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
15.2 TO THE MAXIMUM EXTENT PERMITTED BY LAW, TEYRA'S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THE COMPONENTS OR THIS AGREEMENT IS LIMITED TO THE AMOUNTS YOU PAID TEYRA FOR THE ENTITLEMENT GIVING RISE TO THE CLAIM IN THE TWELVE (12) MONTHS BEFORE THE EVENT GIVING RISE TO LIABILITY. FOR FREE CONTENT AND PROMOTIONAL ACCESS OBTAINED AT NO CHARGE, THAT AMOUNT IS ZERO. This entitlement-based cap governs claims relating to the Components. Claims relating to the Service are governed instead by the liability cap in the Terms of Service at /terms — the greater of the fees you paid in the twelve (12) months before the event or USD 100. The split is explicit: the Terms' cap governs Service claims, except claims relating to the Components, which are governed by this Section 15.2; as to the Components, this Agreement controls (Sections 1.3 and 16.3).
15.3 Some jurisdictions do not allow certain warranty disclaimers or liability limitations. Nothing in Sections 14 or 15 excludes or limits any liability that cannot be excluded or limited under applicable law, or any consumer right you hold under mandatory law that cannot be waived by contract.
16. General
16.1 Governing law and disputes. The governing-law and dispute-resolution section of the Terms of Service at /terms is incorporated into this Agreement by reference and governs this Agreement: the same governing law of the State of Wyoming, the same exclusive venue in the state courts of Sheridan County, Wyoming or the United States District Court for the District of Wyoming, the same exclusion of the United Nations Convention on Contracts for the International Sale of Goods (CISG), and the same consumer carve-out. There is one dispute regime for WebberUI, defined once in the Terms of Service. Nothing in this Agreement waives any mandatory consumer venue or other consumer rights you hold under applicable law.
16.2 Notices and contact. Legal notices to Teyra should be sent to official@teyrallc.com, and by post to Teyra LLC, 30 N Gould St Ste N, Sheridan, WY 82801, United States. We may send notices to you at an email address associated with your account or purchase.
16.3 Entire agreement; order of precedence. The order of precedence is: (1) a written agreement signed by both parties; (2) this Agreement; (3) the plain-language summaries at /license and in the LICENSE file. This Agreement, together with the documents it references, is the entire agreement between you and Teyra regarding the Components.
16.4 Severability. If any provision of this Agreement is held unenforceable, it will be enforced to the maximum extent permissible and the remaining provisions remain in full effect.
16.5 No waiver. Our not enforcing a provision is not a waiver of it.
16.6 Assignment. You may not assign this Agreement without our prior written consent, except to a successor in a merger, acquisition, or sale of substantially all of the assets to which it relates, with notice to us. We may assign this Agreement to a successor of the WebberUI business that assumes our obligations under it — including the promises in Section 3.2.
16.7 Changes. We may update this Agreement prospectively. Changes apply only to Components obtained after the change takes effect (Section 1.4). Material changes will be reflected in the "Last updated" date above.
16.8 Language. This Agreement is provided in English only. Any translation is offered for convenience only, and the English version controls in case of conflict.
16.9 Questions. Custom licensing, enterprise terms, or anything unclear: official@teyrallc.com. Operator: Teyra LLC.