Organizations
An organization gives a team shared ownership of LPM.dev Registry packages, member roles, Registry credentials, and Marketplace purchases.
Create an Organization
- Open Dashboard > Organizations > New.
- Choose the organization name and namespace.
- Complete the organization subscription checkout through Stripe.
The namespace becomes the owner in every package name, so choose it carefully:
{
"name": "@lpm.dev/acme-corp.design-system",
"version": "1.0.0"
}
| Context | Example |
|---|---|
| Package name | @lpm.dev/acme-corp.design-system |
| Package page | https://lpm.dev/acme-corp.design-system |
| Install command | lpm install @lpm.dev/acme-corp.design-system |
The organization is created only after payment succeeds. The creator becomes its owner, and the first billed seat covers that owner.
An owner or admin can rename the namespace until the organization owns its first package. After a package has been published under the namespace, the namespace cannot change.
Publish an Organization Package
Put the organization namespace in package.json, authenticate LPM CLI, and publish:
lpm login
lpm publish --check
lpm publish
LPM CLI does not need an organization flag. The LPM.dev Registry reads the owner from the package name and verifies that the authenticated account is an owner, admin, or maintainer of that organization.
See Organization Packages for distribution and role behavior. The LPM CLI publish reference covers local checks, publish targets, provenance, and flags.
Plan and Billing
| Organization plan | |
|---|---|
| Subscription | $8 per member each month |
| Minimum | 1 billed seat |
| Marketplace platform fee | 10% |
| Private packages | Unlimited |
| Included package storage | 5 GB per member |
| Additional package storage | $0.20 per GB |
Stripe calculates applicable tax during checkout. A pending invitation does not add a billed seat. When the invitation is accepted, the member count and subscription quantity update with proration. Removing or leaving the organization updates the quantity the same way.
If a Stripe synchronization cannot complete immediately, the membership change remains recorded and billing synchronization retries automatically.
If Billing Is Interrupted
A failed or ended subscription does not delete the organization immediately. The paid period is followed by a nine-day grace period during which organization access continues.
After the grace period expires:
- New invitations cannot be sent or accepted.
- Package publishing is blocked.
- Private organization packages cannot be installed.
- The Marketplace platform fee becomes 15% while billing is lapsed.
Owners can update the payment method or manage the organization subscription from Dashboard > Organization > Settings > Billing.
Organization Workflows
- Managing Members — Invitations, roles, removal, and ownership transfer
- Organization Packages — Names, publishing permissions, and distribution
- License Management — Marketplace purchases and member seat assignments