Organizations

An organization gives a team shared ownership of LPM.dev Registry packages, member roles, Registry credentials, and Marketplace purchases.

Create an Organization

  1. Open Dashboard > Organizations > New.
  2. Choose the organization name and namespace.
  3. 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"
}
ContextExample
Package name@lpm.dev/acme-corp.design-system
Package pagehttps://lpm.dev/acme-corp.design-system
Install commandlpm 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
Minimum1 billed seat
Marketplace platform fee10%
Private packagesUnlimited
Included package storage5 GiB per member
Additional package storage$0.20 per GiB a month, rounded up to a whole GiB

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, and the new seat's storage, remote cache and tunnel requests start once that invoice is paid. Removing or leaving the organization lowers the quantity, and credits the seat's unused time only while every invoice is paid. With a payment overdue, a removal credits nothing.

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. Tunnel and remote cache overage pause during the grace period, and a publish that would go past the included storage is refused until billing is active again; while the subscription is past due, storage already past it stays billed. After a failed payment, remote cache above the included quota is kept, up to the cap, for three days, then removed; a cache is kept this way at most once in 27 days, and the billing page shows which applies. Remote cache overage that is off can be turned on once the payment succeeds. When the subscription ends, remote cache overage turns off and cache above the included quota is removed.

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 manage payment methods and subscriptions from Dashboard > Organization > Settings > Billing.

For a failed renewal, the nine-day grace period starts when the previous paid period ends. Payment retries and cancellation do not extend it.

If an invoice is open, select Pay invoice to complete payment through Stripe. Invoice history also shows the next automatic retry when one is scheduled. Updating a card alone does not settle an unpaid invoice.

If the subscription has ended, select Restart Subscription. LPM charges the saved card for the current member count, plus applicable tax, and bills package storage past what the seats include on the new subscription. Access returns after payment succeeds. A failed restart preserves the existing grace deadline. An unpaid subscription that never activated can be canceled immediately.

A restart waits while the organization has an unpaid invoice. Pay it in Invoice History first. A restart also waits while a payment for the organization is disputed.

If a card's owner disputes a payment for the plan and the money is taken back, the organization gets the same nine-day grace as for a failed payment. If LPM wins the dispute, access returns once nothing else is owed. If the dispute is lost, the subscription ends, and LPM sends an invoice for the disputed amount. The organization can restart after that invoice is paid.

Organization Workflows