PY-IDP DUAL LICENSE

Copyright (c) 2026 Royce

This software is dual-licensed under the following terms:

  (A) GNU Affero General Public License v3.0 (AGPL-3.0)
      ── For open-source use: see LICENSE-AGPL.
      Use, modification, and hosting permitted provided that any
      modified version you run as a network-accessible service must
      also be made available under AGPL-3.0 (including your full
      corresponding source). This is the standard copyleft clause
      that prevents "wrap our work in a SaaS and ship" without
      contributing back.

  (B) Commercial License
      ── For proprietary/SaaS embedding WITHOUT AGPL obligations.
      See LICENSE-COMMERCIAL (summary below) or contact the author
      for a paid licence.

    Summary of the Commercial License terms (non-binding preview;
    the signed agreement is the authoritative document):

    Grant. Subject to payment of the applicable license fee, the
      Licensor grants you a non-exclusive, non-transferable,
      worldwide right to use, modify, embed, and distribute py-idp
      in your proprietary products and hosted services, without the
      copyleft obligations of AGPL-3.0.

    Restrictions. You may NOT:
      - redistribute py-idp itself under the commercial terms
        (only your own application code that consumes it);
      - remove copyright or license notices;
      - use the Licensor's name, trademarks, or logos to endorse
        derived products without written permission.

    Disclaimer. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY
      OF ANY KIND. See the full agreement for liability limits.

  Pricing tiers (indicative, not binding):
    Solo          $300 / year   — single developer, single company
    Team          $1,500 / year — up to 10 developers, single company
    Enterprise    contact        — unlimited developers, SLA, support
    SaaS-OEM      per-seat       — embed in hosted SaaS, paid per active user

  To buy a Commercial License, contact:  <royce-license-placeholder>

This file itself is informational. The binding license for your use
case is whichever of LICENSE-AGPL or a signed LICENSE-COMMERCIAL you
choose; the other does not apply to your use.
