nSelf Bundle License

Version: 1.0 Effective date: pending owner sign-off Last updated: September 11, 2026

This page is a draft. It replaces the retired “Source-Available License” that named a product (“nSelf Pro”) which no longer exists. It does not take effect, and this notice does not come down, until the owner signs off (gate G-P6-BUNDLE-LICENSE-TEXT).

Applies to every plugin distributed as part of a paid nSelf bundle (ɳClaw, ɳChat, ɳFamily, ClawDE, ɳSentry) and to ɳSelf+ (“Bundle Plugins”).

The nSelf CLI, the nSelf Admin UI, the reference applications, and every plugin in the free registry are MIT licensed and are not covered by this license. Free means free: no key, no phone-home, no restriction.

In plain language

Question	Answer
Is the CLI free?	Yes. MIT. So are the Admin UI, the reference apps, and every free-registry plugin.
What does a bundle key buy?	The right to run that bundle’s plugins on one nSelf installation, plus full source access.
Can I read the code?	Yes, all of it.
Can I change it?	Yes, for your own installation.
Can I share or resell it?	No.
How many servers?	One key = one installation (one Compose project or one Helm release). Dev/test/CI copies of the same installation are included.
Does it phone home?	Only to validate the key on install/restart, and never your data. Exact offline windows: §4 below.
What happens if I stop paying?	A grace period, then the plugins go dormant. Your database and your copy of the source stay yours.
What if nSelf shuts the license server down?	Active subscribers get a perpetual offline license for the versions they hold.
Refunds?	Per the Refund Policy.

1. What you get

A valid, active bundle subscription key grants you a non-exclusive, non-transferable license to:

Run the Bundle Plugins covered by your key on one nSelf installation per key.
Read and audit the complete source code of those plugins (“source-available”).
Modify them for use in that installation, including building from your modified source.
Keep the source, and your modifications, after your subscription ends (see §4).

One “installation” means one running nSelf stack — one Docker Compose project on one host, or one Kubernetes Helm release — regardless of how many applications, users, or nodes it serves. No per-user, per-app, or per-node charges.

Non-production development, test, and CI copies of the same installation, operated by you, do not need additional keys.

2. What you may not do

Redistribute, publish, sublicense, sell, or offer the Bundle Plugins (or modified versions) to third parties, in source or binary form.
Share or resell your key.
Remove, disable, or circumvent license validation, signature verification, or the dormant state.
Use the Bundle Plugins to provide a competing hosted nSelf service or plugin marketplace.
Represent a modified version as the original.

3. How validation works

Your key is checked when you install or restart a Bundle Plugin. A signed entitlement is cached locally. If nself.org cannot be reached, the cache keeps a Bundle Plugin running for a period, then with a warning, then the plugin goes dormant until validation succeeds. See §4 for the exact windows. An offline workflow (nself license export / nself license import) is available for disconnected environments. We never read your data, code, or configuration during validation.

4. Grace periods

There are two different grace periods. They are triggered by different things and do not stack.

After your subscription expires: Bundle Plugins keep running for 30 days past the expiry date, with a warning. This is the only grace period that applies to an expired subscription, and it applies whether or not our servers are reachable.
When we cannot be reached: this covers an active, unexpired subscription during a period nself.org cannot be validated against, for example a network problem on our side or yours. Your last validated key keeps a Bundle Plugin running silently for up to 72 hours. From 72 hours to 7 days, it keeps running with a warning. Past 7 days without a successful validation, the plugin goes dormant until nself.org is reachable again. A revoked key does not get this grace period at any cache age.
After either grace period ends: the plugins enter a dormant state and will not start until the subscription is renewed or validation succeeds. Your data stays in your PostgreSQL database and remains yours.
Source rights survive: you may keep, read, and modify the source you obtained while licensed. You may not run it in production without an active key.
Refunds: per the Refund Policy.

5. Continuity

If nSelf permanently discontinues the license validation service, every subscriber active at that time receives a perpetual offline license file for the plugin versions they hold, at no charge. Your ability to run what you paid for does not depend on our servers staying up forever.

6. Revocation

We may revoke a key for non-payment, chargeback, fraud, or breach of §2. Revocation takes effect at the next validation and you will be notified by email. Revoked installations enter the dormant state.

7. Contributions

If you send us a modification, you grant nSelf the right to include it in the Bundle Plugins under this license. You keep ownership of your contribution.

8. Warranty and liability

The Bundle Plugins are provided “as is”, without warranty of any kind. To the maximum extent permitted by law, nSelf is not liable for any damages arising from their use. Sections 9-14 of the Terms of Service apply.

9. Relationship to other documents

This license is the “Plugin Marketplace Addendum” referenced by Terms of Service §17. Where this document and §17 differ, this document governs Bundle Plugin licensing. Pricing is at nself.org/pricing; the technical description of validation, grace, and offline behavior is at Licensing.