Effective date: Oct 13, 2026
These Self-hosted Subscription Terms ("Terms" or "Agreement") govern the purchase and use of paid self-hosted plans for Logto ("Self-hosted Plans") provided by Silverhand Inc., a Delaware corporation located at 2810 North Church Street, Wilmington, Delaware, 19802, United States ("Silverhand", "Logto", "we", "us").
By purchasing a Self-hosted Plan, activating a License File, or using any Commercial Feature, the Customer agrees to be bound by these Terms.
These Terms apply only to Self-hosted Plans. Logto Cloud, the managed service operated by Logto, is governed by the separate Terms of Service for Logto Cloud.
The legal entity or individual entering into this Agreement and responsible for all Deployments activated under its License Files.
The publicly released Logto software, including its source code, container images, and Documentation, as made available by Logto.
The portions of the Software that Logto makes available under the Mozilla Public License 2.0 ("MPL-2.0") or another open source license. Open Source Components are licensed to the Customer under their respective open source licenses, not under this Agreement.
Capabilities of the Software that are included in the public release but remain disabled until a valid License File is applied. The Commercial Features included in each Self-hosted Plan are described on the Self-hosted plans page and in the Documentation.
A cryptographically signed file issued by Logto that identifies the Customer, the Self-hosted Plan, the Subscription Term, and any applicable usage limits, and that unlocks the corresponding Commercial Features in a Deployment.
A running instance of the Software operated by or for the Customer on infrastructure the Customer controls, together with the database and other backing services attached to it.
The Customer's purchase of a Self-hosted Plan for a defined Subscription Term.
The period during which a Subscription is active, as stated at purchase or in an Order Form.
A written ordering document or contract, including a Master Services Agreement, signed by both parties that references these Terms.
The technical support, upgrade guidance, and security advisory services included in a Self-hosted Plan, as described in Section 6.
The number of unique end users who authenticate through a Deployment at least once during a calendar month, across all tenants of that Deployment.
Any data, including personal data of the Customer's end users, that is stored in or processed by a Deployment.
Personal data Logto processes as a controller in connection with the Customer's Subscription, such as administrator and support contact details, billing information, support communications, and License File issuance records. Account Data is governed by the Privacy Policy.
Logto's published documentation for the Software, currently available at https://docs.logto.io.
Nothing in this Agreement limits the rights granted to the Customer under the MPL-2.0 or any other open source license that applies to the Open Source Components. The Customer may continue to use the Open Source Components without a Subscription.
Commercial Features are not licensed under the MPL-2.0 or any other open source license, regardless of how their source code is made available. Commercial Features may be used only under a valid Subscription and in accordance with this Agreement.
If a term of this Agreement conflicts with an open source license with respect to an Open Source Component, the open source license controls for that component.
Subject to this Agreement and payment of all applicable fees, Logto grants the Customer a limited, non-exclusive, non-transferable, non-sublicensable license during the Subscription Term to:
Unless otherwise stated in an Order Form, a Subscription covers one production Deployment. The Customer may also apply the License File to non-production Deployments (such as development, staging, and testing) that serve the same production Deployment and do not carry production traffic.
Each non-production Deployment is expected to stay within 50,000 access tokens issued per month across all of its tenants, the same guardrail that applies to development tenants on Logto Cloud. A non-production Deployment that exceeds this guardrail may be treated as carrying production traffic, in which case Section 4.2 applies.
Except as expressly permitted by this Agreement or by an applicable open source license, the Customer shall not, and shall not permit any third party to:
The Customer is responsible for all persons who operate its Deployments or use its License Files and must ensure they comply with this Agreement.
Each Self-hosted Plan has usage limits, including limits on MAU, number of production Deployments, and number of support contacts, as stated on the Self-hosted plans page at the time of purchase or in the Order Form. Self-hosted Pro is intended for Deployments of up to 50,000 MAU.
If a Deployment exceeds the usage limits of the Customer's Self-hosted Plan, the Customer must notify Logto and, within 30 days, either upgrade to a Self-hosted Enterprise Subscription that covers its usage or reduce usage to within the limits. Self-hosted Pro does not offer overage pricing. If the Customer does neither within 30 days, Logto may treat the excess use as a material breach under Section 8.3.
On Logto's reasonable request, no more than once per Subscription Term, the Customer shall provide a written statement of the MAU and number of Deployments covered by its Subscription, prepared in good faith from the Deployment's own records. Logto will not require access to the Customer's systems or Customer Data for this purpose.
Logto will deliver the License File to the Customer's administrator email or through the Customer's account with Logto after the Subscription is confirmed and applicable fees are received.
The License File is applied through the Logto Console of the Deployment. Commercial Features take effect once a valid License File is applied and no restart of the Deployment is required.
The Software verifies the License File locally within the Deployment, so individual requests do not depend on a connection to Logto. The Deployment also refreshes its License File with Logto periodically, which keeps the License File current with renewals, plan changes, and revocation.
If a Deployment goes 30 days without a successful refresh, Commercial Features are disabled and the Deployment continues to operate with the Open Source Components until a refresh succeeds. The Deployment never stops operating because it cannot reach Logto. A Deployment that uses Commercial Features therefore needs to reach Logto's license service at least once every 30 days.
When the Subscription Term ends without renewal, the License File expires. Upon expiry, Commercial Features are disabled and the Deployment continues to operate with the Open Source Components. Expiry does not delete Customer Data or configuration. Configuration that depends on a Commercial Feature may stop taking effect until the Subscription is renewed.
Logto may reissue a License File on the Customer's request, for example to reflect a plan change, a renewal, or a change in the Customer's legal name. Reissuance does not extend the Subscription Term unless a renewal is purchased.
Support Services cover questions and issues relating to the installation, configuration, upgrade, and operation of the Software in the Customer's Deployment. Support Services do not include operating the Customer's infrastructure, writing custom code, or supporting third-party software except as it interfaces with the Software.
Self-hosted Pro includes email support with an initial response within 3 business days of receiving a request, provided by Logto during its normal business hours, for up to 2 named support contacts designated by the Customer.
Self-hosted Enterprise support, including severity levels, response targets, support hours, communication channels, and root cause analysis commitments, is defined in the Order Form.
Support Services for Self-hosted Pro cover the current stable release of the Software and the immediately preceding minor release. Logto may require the Customer to upgrade to a supported version before providing support for an issue. Supported versions for Self-hosted Enterprise are defined in the Order Form.
Logto publishes security advisories for the Software publicly. Subscribers additionally receive guidance by email on applying security fixes to their Deployments.
The Software, including Commercial Features, is distributed through Logto's public release channels. A Subscription does not entitle the Customer to any specific future feature, release schedule, or release cadence.
Logto's ability to provide Support Services depends on the Customer providing reasonable information about the issue, including version numbers, configuration, and relevant logs. The Customer is responsible for redacting Customer Data before sharing logs or other materials with Logto.
The Customer agrees to pay the fees for its selected Self-hosted Plan as stated at purchase or in the Order Form. Fees are stated in US dollars.
Self-hosted Pro is billed annually in advance. Enterprise fees are billed as stated in the Order Form. Invoices are due within 30 days unless otherwise stated.
Unless otherwise stated in an Order Form, Subscriptions renew automatically for successive Subscription Terms of the same length unless either party gives notice of non-renewal at least 30 days before the end of the current Subscription Term. Logto may change fees for a renewal Subscription Term by giving notice at least 60 days before the renewal date.
Fees are non-refundable except as required by law or expressly stated in this Agreement or an Order Form.
Fees exclude taxes. The Customer is responsible for all applicable taxes except those based on Logto's income.
If fees are not paid when due, Logto may suspend Support Services and decline to issue or renew License Files until payment is received.
This Agreement begins when the Customer first purchases a Subscription or activates a License File, and continues for as long as the Customer has an active Subscription.
Either party may allow a Subscription to lapse by giving notice of non-renewal in accordance with Section 7.3. The Customer may continue to use the Commercial Features until the end of the Subscription Term already paid for.
Either party may terminate this Agreement for material breach not cured within 30 days after written notice. Logto may terminate immediately if the Customer breaches Section 3.3.
Upon termination or expiry, the license granted in Section 3.1 ends, all License Files issued to the Customer are revoked, and the Customer must stop using Commercial Features. Termination does not affect the Customer's rights under the MPL-2.0 or other open source licenses to the Open Source Components, and does not require the Customer to delete its Deployment or Customer Data.
Sections 2, 3.3, 7 (as to fees accrued), 9, 10, 11, 12, 13, 14, and 16 survive termination.
Customer Data resides in the Customer's Deployment. Logto does not host, access, or process Customer Data in connection with a Self-hosted Plan, and Logto is not a processor of Customer Data under this Agreement. Accordingly, the Logto Cloud Data Processing Addendum does not apply to Self-hosted Plans.
The Customer is solely responsible for its Deployment, including infrastructure, network security, access control, backups, disaster recovery, applying updates and security fixes, and compliance with laws that apply to its Deployment and Customer Data, including as the controller of any personal data it processes.
If the Customer voluntarily shares Customer Data with Logto in the course of Support Services, for example in logs or screenshots, Logto will use that data only to provide the requested support and will delete it when the support request is resolved. The Customer should minimize the Customer Data it shares in this way.
If the Customer connects third-party services to its Deployment (for example identity providers, email or SMS providers, or storage), the Customer is responsible for reviewing and complying with their terms.
Logto processes Account Data as a controller to manage the Subscription, issue License Files, bill the Customer, and provide Support Services, in accordance with its Privacy Policy.
When a Deployment refreshes its License File as described in Section 5.3, it sends Logto the License File, a randomly generated identifier for the Deployment, the version of the Software, and aggregated usage counts, such as MAU, access tokens issued, and number of tenants. Usage counts are totals only and contain no personal data or records of individual end users. Logto uses this information to keep the License File current, to compare usage with the limits of the Customer's Self-hosted Plan, to count the Customer's active Deployments, and to provide Support Services.
The Customer can stop sending usage counts by setting the SELF_HOSTED_LICENSE_USAGE_REPORTING_DISABLED environment variable on every instance of the Deployment, as described in the Documentation. The License File, deployment identifier, and Software version are still sent with each refresh. Stopping usage counts does not change the Customer's obligations under Section 4.
Apart from the data described in this Section, Logto does not collect Customer Data or operational telemetry from the Customer's Deployment.
Each party must protect the other party's Confidential Information using reasonable care and may disclose such information only to personnel with a need to know and who are bound by confidentiality obligations. License Files, pricing in an Order Form, and non-public information shared in the course of Support Services are Confidential Information.
Confidential Information excludes information that is public, independently developed, already known, or lawfully obtained from a third party.
Logto and its licensors retain all right, title, and interest in the Software, Commercial Features, License Files, and Documentation. No rights are granted to the Customer except as expressly stated in this Agreement or in the applicable open source licenses.
The Customer grants Logto a perpetual, irrevocable, royalty-free license to use feedback and suggestions for improving the Software and Logto's services.
Contributions the Customer makes to the Open Source Components are governed by the contribution terms of the relevant Logto repository, not by this Agreement.
The Software, Commercial Features, License Files, and Support Services are provided "as is" without warranties of any kind. Logto disclaims all implied warranties including merchantability, fitness for a particular purpose, and non-infringement. Logto does not guarantee that the Software will operate uninterrupted or error-free in the Customer's environment, and is not responsible for the Customer's infrastructure, configuration, or the availability of the Customer's Deployment.
The Customer agrees to indemnify and hold Logto harmless against claims arising from the Customer's operation of its Deployment, the Customer's processing of Customer Data, the Customer's misuse of the Software or License Files, or the Customer's violation of this Agreement.
To the maximum extent permitted by law:
These limitations do not apply to the Customer's payment obligations or to a breach of Section 3.3.
The Customer shall comply with all applicable export control and sanctions laws in connection with its use of the Software and License Files, and represents that it is not located in, or a national or resident of, any country or region subject to comprehensive sanctions, and is not on any government list of prohibited or restricted parties.
If the Customer has signed an Order Form or Master Services Agreement with Logto for a Self-hosted Enterprise Subscription, that document governs the Subscription. In the event of a conflict between these Terms and a signed Order Form or Master Services Agreement, the signed document controls.
Logto may update or modify the Software and the set of Commercial Features over time. Logto will provide notice if a change materially reduces the Commercial Features included in the Customer's Self-hosted Plan during a paid Subscription Term.
Neither party is liable for delays caused by events beyond reasonable control.
These Terms are governed by the laws of Delaware, USA.
These Terms, together with any Order Form and referenced documents, constitute the entire agreement regarding Self-hosted Plans and supersede all prior agreements on the subject.
Logto may update these Terms by giving at least 30 days' notice. Updated Terms apply from the start of the Customer's next Subscription Term unless the Customer agrees to them earlier. Renewal of a Subscription after notice constitutes acceptance.
The Customer permits Logto to identify the Customer as a user of Logto in marketing materials. No endorsement is implied. The Customer may opt out of this usage at any time by notifying Logto at [email protected].
The Customer may not assign this Agreement without Logto's written consent, except to a successor in connection with a merger or acquisition that assumes all obligations under this Agreement.
If a provision is unenforceable, the remainder remains in effect.
Failure to enforce a provision does not constitute a waiver.