RS-TECH-HUB SOFTWARE LICENSE AGREEMENT

Effective Date: February 1, 2026

Last Updated: February 1, 2026

Version: 2.0

EXECUTIVE SUMMARY

This agreement governs the RS-Tech-Hub License, offering production-ready NestJS infrastructure modules with professional support from the software architect.

License Grant:

  • Production licenses for server infrastructure modules
  • Obfuscated code distribution with complete TypeScript definitions
  • Direct technical support via email
  • Security updates and maintenance during license term
  • Unlimited development mode access without licensing requirements
  • Select modules available under MIT open source license

License Tier Structure:

  • Professional tier with competitive annual licensing (see purchasing page for exact pricing)
  • One production instance per license (self-hosted)
  • Email support

Key Limitations:

  • Email support (best effort, no formal Service Level Agreement)
  • No legal indemnification for intellectual property claims
  • No enterprise-grade warranties beyond software conformance
  • Limited liability capped at annual license fee

The Professional License targets technical decision-makers and teams who prioritize quality implementation and cost-effective solutions.

1. DEFINITIONS

Software means the RS-Tech-Hub NestJS backend infrastructure packages distributed via the @rs-tech-hub organization, including authentication, user management, and related or additional modules.

License means the right to use the Software as granted under this Agreement.

License Key means the unique alphanumeric code provided via Gumroad that activates production and staging environments.

Development Environment means local development or internal testing infrastructure not accessible to end users or generating revenue.

Staging Environment means pre-production quality assurance infrastructure accessible to internal teams and authorized test users, but not used for revenue-generating operations.

Production Environment means infrastructure where the Software serves end users, processes customer data, or generates revenue.

Licensee means the individual or legal entity that has purchased a License.

Licensor means RS-Tech-Hub, operated by Raphael Schwirtlich.

2. LICENSE GRANT

2.1 Scope of License

Subject to the terms herein and payment of applicable fees, Licensor grants Licensee a limited, non-exclusive, non-transferable, non-sublicensable license to:

  • (a) Install and operate the Software in accordance with documentation;
  • (b) Integrate the Software into Licensee's applications;
  • (c) Modify open source (MIT licensed) modules;
  • (d) Extend licensed modules via documented APIs and interfaces;
  • (e) Deploy commercial applications utilizing the Software.

2.2 License Types

Single Instance License: One production deployment per license key

Development License: Unlimited development instances (no license key required)

Staging License: Unlimited staging instances (license key required)

2.3 Instance Limitations

Each License Key permits operation on ONE (1) production instance. Multiple production instances require multiple licenses or upgrade to Enterprise tier upon availability.

Instance migration is supported through production instance deactivation in staging mode with subsequent reactivation via production instance startup.

2.4 Code Distribution Model

Dual Licensing Structure:

RS-Tech-Hub employs a dual distribution model:

Open Source Components (MIT License):

  • Foundation modules distributed with full source code
  • Standard MIT License terms apply
  • Clearly identified in package documentation
  • Full modification and derivative rights granted

Licensed Components (Proprietary):

  • Premium modules distributed as obfuscated JavaScript
  • Complete TypeScript definitions provided for integration
  • Documentation and API specifications included
  • Source code protection via obfuscation

Technical Integration:

  • TypeScript definitions ensure type safety and IDE support
  • Comprehensive API documentation enables extension without source access
  • Obfuscation protects intellectual property while maintaining functionality

Prohibited Activities:

  • Deobfuscation or reverse engineering of licensed modules
  • Redistribution of proprietary code
  • Circumvention of license validation mechanisms
  • Publication of internal implementations

3. LICENSE VALIDATION

3.1 Validation Mechanism

The Software employs API-based license validation through Gumroad's licensing infrastructure:

  • Validation occurs at application startup and every 24 hours thereafter
  • Internet connectivity required for production and staging environments
  • Development environments operate without validation requirements
  • Failed validation triggers license removal. RS-Tech-Hub modules seize operation.

3.2 License Duration and Renewal

Initial Term: 12 months from purchase date

Grace Period: 30 days post-expiration with full functionality

Renewal: Manual purchase at current rates via Gumroad

Post-grace-period expiration results in production and staging deactivation while development mode remains operational.

3.3 Environment-Specific Behavior

Development Mode:

  • No license key required
  • Usage limitations as documented on application startup
  • Permanent availability for development purposes

Staging/Production Modes:

  • Valid license key required
  • Full feature access with higher limitations as documented on application startup
  • Automatic license removal upon license expiration with no grace period for staging environements.

5. SUPPORT SERVICES

5.1 Support Channels

Primary Channel: Email support

Support Scope: Installation, configuration, integration guidance, bug resolution

5.2 Included Support

  • Technical implementation assistance
  • Bug identification and resolution
  • Documentation clarification
  • Integration architecture guidance
  • License activation support

5.3 Excluded from Support

  • Custom feature development
  • Application architecture consulting (except integration-specific)
  • Third-party service integration debugging
  • Code review of Licensee applications
  • Emergency after-hours support

5.4 Support Model

Support is provided via email on a best-effort basis without formal Service Level Agreement.

Best Effort Support:

  • No formal Service Level Agreement
  • Response times depend on availability
  • Priority given to critical issues

5.5 Bug Resolution Priority

Critical: Production failure (best effort resolution)

High: Feature malfunction (included in regular updates)

Low: Enhancement requests (roadmap consideration)

6. USAGE RESTRICTIONS

6.1 Permitted Use Cases

Licensee may:

  • (a) Deploy the Software in commercial applications;
  • (b) Modify MIT licensed modules;
  • (c) Extend licensed modules via documented interfaces;
  • (d) Integrate with Licensee's proprietary systems;
  • (e) Build customer-facing applications utilizing the Software.

6.2 Prohibited Activities

Licensee may not:

  • (a) Sublicense, resell, or redistribute the Software or License Keys;
  • (b) Share License Keys across unrelated organizations or projects;
  • (c) Remove or modify copyright or license notices;
  • (d) Develop competing products utilizing the Software;
  • (e) Publish or distribute proprietary source code;
  • (f) Reverse engineer, deobfuscate, or reconstruct obfuscated modules;
  • (g) Circumvent license validation systems;
  • (h) Violate applicable laws or regulations.

7. INTELLECTUAL PROPERTY

7.1 Software Ownership

All intellectual property rights in the Software, including source code, documentation, and related materials, remain the exclusive property of Licensor.

This Agreement grants usage rights only; no ownership transfer occurs.

7.2 Licensee Applications

Licensee retains all rights to applications developed using the Software. Licensor claims no ownership of Licensee's code, business logic, or customer data.

7.3 Trademark Usage

Licensee may reference "Built with RS-Tech-Hub" or "Powered by RS-Tech-Hub" for factual purposes. Misleading use of Licensor's name, logo, or trademarks is prohibited.

8. REFUND POLICY

8.1 Integration Guarantee

Licensees receive a 30-day integration guarantee. If Licensee cannot successfully integrate the Software within 30 days despite good-faith effort following documentation, full refund is available upon request with:

  • Description of integration attempts
  • Specific technical obstacles encountered
  • Error messages or configuration details

Licensor will attempt resolution before processing refund.

8.2 Post-Integration Policy

Following successful production or staging deployment, licenses become non-refundable. Successful deployment validates compatibility with Licensee's technical requirements.

8.3 Exceptional Circumstances

Refunds are provided for:

  • Software discontinuation (pro-rata refund of unused term)
  • License validation system failure exceeding 30 days (full refund)
  • Critical support request abandonment exceeding 90 days (full refund)

Refunds are not provided for:

  • Change of business direction
  • Internal architectural decisions
  • Dissatisfaction with response times within stated SLA
  • Decision to develop in-house alternative

8.4 Refund Processing

Requests submitted to insights@rs-tech-hub.com are processed within 14 business days via Gumroad. Processing fees are non-refundable.

9. DATA PROTECTION AND PRIVACY

9.1 Data Collection

License Validation Data:

  • License key (encrypted)
  • Instance identifier (hashed)
  • Validation timestamps
  • Environment classification

Purchase Information (via Gumroad):

  • Email address
  • Transaction date and amount

9.2 Data Not Collected

The Software does not collect, transmit, or store:

  • End user data or personally identifiable information
  • Customer business data or analytics
  • Application usage metrics beyond license validation

9.3 Data Retention and Compliance

License validation data: 24 months maximum

Purchase records: 10 years (Swiss tax law requirement)

All data handling complies with Swiss data protection law and GDPR requirements.

9.4 Licensee Responsibilities

Licensee is responsible for:

  • GDPR, CCPA, HIPAA, and applicable regulatory compliance
  • End user data protection and privacy
  • Secure storage of License Keys
  • Implementation of appropriate security measures

The Software may provide tools (encryption, audit logging, access controls) to assist compliance efforts. Achieving certification remains Licensee's responsibility.

10. WARRANTIES AND DISCLAIMERS

10.1 Limited Warranty

Licensor warrants that the Software substantially conforms to its documentation. The sole remedy for non-conformance is commercially reasonable efforts to correct reproducible issues.

10.2 Disclaimer of Warranties

EXCEPT FOR THE LIMITED WARRANTY ABOVE, THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LICENSOR DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO:

  • MERCHANTABILITY
  • FITNESS FOR A PARTICULAR PURPOSE
  • NON-INFRINGEMENT
  • UNINTERRUPTED OR ERROR-FREE OPERATION
  • COMPLETE ACCURACY OF RESULTS

No software is error-free. This disclaimer reflects standard industry practice for commercial software licensing.

11. LIMITATION OF LIABILITY

11.1 Liability Cap

Licensor's total aggregate liability arising from or related to this Agreement shall not exceed the amount paid by Licensee for the License in the twelve (12) months preceding the claim.

11.2 Excluded Damages

TO THE MAXIMUM EXTENT PERMITTED BY LAW, LICENSOR SHALL NOT BE LIABLE FOR:

  • Indirect, incidental, special, consequential, or punitive damages
  • Lost profits or revenue
  • Data loss (Licensee must maintain backups)
  • Business interruption
  • Cost of substitute goods or services
  • Third-party claims

11.3 Liability Exceptions

Liability limitations do not apply to:

  • Intentional misconduct or gross negligence
  • Violations of intellectual property rights
  • Liabilities that cannot be limited under applicable law

11.4 Rationale

These limitations enable competitive pricing while maintaining sustainable business operations. Enterprise-grade liability coverage requires enterprise pricing structure and insurance arrangements not currently in place.

12. INDEMNIFICATION

12.1 No Indemnification Provided

Licensor does not indemnify Licensee against intellectual property claims, litigation, or other legal actions related to Software use.

12.2 Rationale

Indemnification requires significant insurance infrastructure not economically viable at current pricing. The Software utilizes standard open-source components (NestJS, etc.) with proper licensing, minimizing IP risk.

12.3 Alternative Protections

In the event of legitimate IP claims:

  • Licensor will collaborate on resolution approaches
  • Code modifications or replacements provided if feasible
  • Refunds available if resolution impossible

Legal defense costs and damages remain Licensee's responsibility.

13. TERM AND TERMINATION

13.1 Voluntary Termination

Licensee may terminate by ceasing Software use and deactivating License Keys. No refund provided for unused license term except as specified in Section 8.

13.2 Termination for Cause

Licensor may terminate immediately for:

  • Material breach of Agreement terms
  • Failure to renew expired license after grace period
  • Illegal use of Software
  • Circumvention of license validation mechanisms

13.3 Effects of Termination

Upon termination:

  • All license rights cease immediately
  • Production and staging instances must be deactivated
  • Development mode remains available
  • Licensee retains ownership of developed applications
  • Sections 7, 10, 11, 12, and 14 survive termination

14. GENERAL PROVISIONS

14.1 Entire Agreement

This Agreement constitutes the complete understanding between parties and supersedes all prior agreements, communications, and understandings regarding the Software.

14.2 Modifications

Licensor may modify this Agreement by:

  • Publishing updated version on website
  • Email notification to license holders
  • 30-day advance notice for material changes

Continued Software use constitutes acceptance of modifications.

14.3 Governing Law and Jurisdiction

This Agreement is governed by Swiss law without regard to conflict of law principles.

Exclusive jurisdiction: Courts of Zürich, Switzerland.

14.4 Assignment

Licensee may not assign or transfer this Agreement without written consent. Licensor may assign without restriction. Attempted unauthorized assignment is void.

14.5 Severability

If any provision is deemed unenforceable, remaining provisions remain in full effect. Unenforceable provisions shall be reformed to the extent possible while preserving intent.

14.6 No Waiver

Failure to enforce any provision does not constitute waiver of that or any other provision. Waivers must be in writing.

14.7 Force Majeure

Neither party is liable for delays or failures resulting from circumstances beyond reasonable control, including natural disasters, pandemics, government actions, or infrastructure failures.

14.8 Export Compliance

Licensee agrees to comply with all applicable export laws and regulations.

14.9 Third-Party Components

The Software may incorporate third-party open source components. Use of such components is governed by their respective licenses as documented in Software documentation.

15. CONTACT INFORMATION

For support, licensing, or general inquiries:

Raphael Schwirtlich
RS-Tech-Hub
Trottenstrasse 23
8180 Bülach
Switzerland

Email: insights@rs-tech-hub.com
Website: https://rs-tech-hub.com
Documentation: https://rs-tech-hub.com/docs

16. ACCEPTANCE

BY INSTALLING, ACCESSING, OR USING THE SOFTWARE, LICENSEE ACKNOWLEDGES HAVING READ THIS AGREEMENT, UNDERSTANDS ITS TERMS, AND AGREES TO BE BOUND BY ITS CONDITIONS.

IF LICENSEE DOES NOT AGREE TO THESE TERMS, LICENSEE MUST NOT INSTALL, ACCESS, OR USE THE SOFTWARE.

RS-Tech-Hub Software License Agreement

Version 2.0

Effective Date: February 1, 2026