PackagePass

Contact

Building private package distribution into your product?

Talk to us if you ship customer SDKs, generated TypeScript libraries, internal packages, or preview packages and need tighter control over who can install what.

Start a conversation

What to include

Send the package distribution problem, not a polished requirements doc.

A useful first email can be short. We mainly need to understand what you publish, who consumes it, and what access control is hard today.

Packages

What kinds of TypeScript packages you ship and how often they change.

Consumers

Whether installs are for customers, agents, CI jobs, services, or internal teams.

Workflow

How packages are published, promoted, previewed, deprecated, and audited today.

Constraints

Any security review, custom domain, billing, migration, or support requirements.

Best fit

B2B SDK programs

You need to distribute private npm packages to customers without inviting them into internal repos or broad npm organizations.

Best fit

AI-generated libraries

You generate TypeScript modules that can become installable, versioned, policy-checked packages.

Best fit

Platform engineering

You own shared SDKs, auth clients, design systems, or API clients and need package-level grants, tokens, previews, and audit trails.