Rillence
Login

License

Effective Date: June 6, 2026

This License explains how Rillence content, labs, scenarios, software, code examples, documentation, and subscription materials may be used. It applies together with our Terms of Service.

1. Materials Covered by This License

Rillence includes several categories of materials:

  • Editorial content, documentation, articles, explanations, diagrams, and written lessons
  • Labs, scenarios, tracks, exercises, checks, scoring logic, and reports
  • CLI tools, scripts, templates, local workflow tools, and related software
  • Code examples, sample applications, broken systems, solutions, tests, and repositories
  • Paid subscription materials, premium labs, private training materials, and enterprise materials
  • Branding, design, product names, trademarks, and website assets

Unless a specific material states otherwise, these materials are owned by RillRate DOO or its licensors.

2. General Learning License

Subject to the Terms of Service, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use Rillence materials for your own learning, internal training, evaluation, and authorized business use.

You may:

  • Read and use the materials through the Service
  • Run labs and scenarios in authorized learning environments
  • Use examples to understand concepts, patterns, and techniques
  • Download materials only where the Service provides a download option
  • Share links to public Rillence pages
  • Quote short excerpts with attribution

3. Restrictions

Unless we give written permission, you may not:

  • Republish full lessons, labs, scenarios, tracks, or substantial portions of Rillence materials
  • Repackage Rillence materials into another course, training program, product, platform, marketplace, or repository
  • Sell, sublicense, rent, lease, or commercially exploit access to Rillence materials
  • Share paid materials with unauthorized users
  • Publish answer keys, complete solutions, scoring bypasses, or internal scenario logic
  • Remove attribution, copyright notices, access controls, or license notices
  • Mirror, scrape, archive, or copy the Service at scale
  • Use Rillence materials to create a substantially similar or competing product
  • Use protected Rillence materials to train, fine-tune, evaluate, or improve commercial AI systems without written permission

4. Code Examples and Sample Projects

Rillence may provide code examples, sample services, broken applications, smart contracts, configuration files, tests, scripts, and repositories.

Unless a repository or file includes a separate open-source license, you may:

  • Read, run, and modify the code for learning
  • Use the code inside Rillence labs and scenarios
  • Reuse general ideas, techniques, and patterns in your own work
  • Build your own implementation based on what you learned

You may not:

  • Republish complete sample projects as your own
  • Sell or redistribute Rillence code collections as a product
  • Misrepresent example code as production-ready software
  • Remove attribution or notices where provided
  • Use scenario code, tests, fixtures, or scoring logic to clone or compete with Rillence

You are responsible for reviewing, testing, securing, auditing, and adapting any code before using it outside a learning environment.

5. CLI and Software Tools

Rillence CLI tools and related software are licensed, not sold.

Subject to your subscription status and the Terms of Service, you may use the CLI and software tools only for authorized access to Rillence labs, scenarios, workflows, and related features.

You may not:

  • Reverse engineer, decompile, or attempt to extract source code except where allowed by law
  • Bypass licensing, authentication, entitlement, or usage controls
  • Modify the CLI to access paid features without authorization
  • Redistribute the CLI or related software except through official distribution channels
  • Use the software to attack, disrupt, or test systems you do not own or have permission to test

Open-source components included in or used by Rillence remain subject to their own licenses.

6. Paid Subscription Materials

Paid plans may include access to premium labs, private scenarios, advanced tracks, reports, CLI features, training materials, recordings, templates, or other subscription-only materials.

Paid materials are licensed only to authorized users during the period in which they have valid access.

Unless we agree otherwise in writing, you may not:

  • Share paid materials outside your account, team, or organization
  • Record, repost, redistribute, or resell paid training materials
  • Use paid scenarios to provide commercial training to third parties
  • Transfer subscription access to unauthorized users

When your subscription ends, your right to access paid materials ends, except for materials we explicitly allow you to keep.

7. Team and Enterprise Use

If your organization purchases a team, business, or enterprise plan, authorized users may use Rillence materials internally for learning, training, and operational readiness.

Unless separately agreed in writing, team or enterprise access does not allow you to:

  • Provide external commercial training using Rillence materials
  • Share private labs or paid materials with customers, contractors, or third parties who are not authorized users
  • Repackage Rillence materials as your organization’s own product or curriculum
  • Remove Rillence branding or attribution from materials

8. User Content

You retain ownership of content you submit to Rillence, such as answers, notes, files, comments, feedback, code submissions, and lab outputs.

By submitting content, you grant Rillence the rights described in the Terms of Service so we can operate, support, secure, and improve the Service.

Do not submit content that you do not have permission to use.

9. Third-Party Materials

Some parts of the Service may include third-party software, libraries, fonts, documentation, data, examples, or linked resources. Those materials remain subject to their own licenses and terms.

If a specific file, repository, package, or third-party component includes its own license, that license controls for that component.

10. Trademarks and Branding

Rillence names, logos, branding, product names, design elements, and marks are owned by RillRate DOO or its licensors.

You may not use Rillence branding in a way that suggests endorsement, partnership, sponsorship, or affiliation without written permission.

11. No Production Warranty

Rillence materials are provided for educational and informational purposes.

We do not guarantee that any code, configuration, contract, database setting, infrastructure pattern, security practice, performance optimization, scenario result, or recommendation is accurate, complete, secure, compliant, or suitable for production use.

You are responsible for testing, reviewing, auditing, and validating anything you use outside the Service.

12. Permission Requests

For permissions, licensing, partnership, enterprise reuse, or commercial training requests, contact:

legal@rillence.com

Last updated: June 6, 2026