← zed-pkg home One tool. Your own way to work.

Start solo. Build together.

Keep a small project simple, or give your team a shared home for packages. Choose how you want to work; your identity stays yours in either path.

I'm working on my own I'm here with a team

An account for you. A workspace for your work.

Your next project

For individuals

Explore packages on your own, then set up a personal namespace when you want to publish.

Use your own identity; no shared team credentials.
A personal publishing namespace is optional.
Trying the CLI does not require creating a hosted workspace.

Individual sign-in · rollout pending Get started with the CLI →

A place for your team

For organizations

Create or choose a workspace for company packages, with a separate identity and explicit membership for each person.

Workspace owners manage product membership and roles.
An existing employee needs membership granted by a workspace owner.
A company email domain alone never grants access.

Organization sign-in · rollout pending Get started with the CLI →

What happens after sign-in?

01 · Your identity

A private sign-in handoff

Authentication belongs to the customer application and Shared Auth. This marketing site never asks for your password, receives a sign-in token, or stores your workspace membership.

02 · Your workspace

Choose where you belong

The application checks your existing memberships. Choose a workspace explicitly, create one if appropriate, or ask your organization owner to grant membership. Signing in does not automatically join a team.

03 · Your packages

Work within your permissions

Zed checks product roles before allowing package or membership changes. Organization owners manage their own workspaces; they do not receive access to the separate platform-administration system.

Just trying Zed?

Start with the CLI walkthrough and public packages. You do not need to create a company workspace just to explore. For a registry you operate yourself, see self-hosting.