Account

In this section, you will find information on creating an account to access our package management services. An account is required to upload and manage your own packages.

Note: For more information about creating a package, please visit our guide on Package Creation.

Creating an Account

Creating an account is the first step to start using our package management services. To begin, follow the steps below:

  1. Visit our Website: Open your web browser and navigate to our website.

  2. Sign-Up Page: On the homepage, click on the "Sign Up" or "Create Account" button. This will take you to the account creation page.

  3. Username: Choose a unique lowercase username for your account. This username will also be associated with each of the packages you upload, making it easy for others to identify your contributions.

  4. Provide Information: Fill in the required information, including your email address and a secure password. Make sure to use a strong password to keep your account secure.

  5. Verification: Complete any necessary verification steps, such as solving a CAPTCHA or confirming your email address through a verification link sent to your email inbox.

  6. Confirmation: Once you've successfully completed the registration process, you'll receive a confirmation message indicating that your account has been created.

Now that you have an account, you can start uploading and managing your packages. Your lowercase username will be displayed before the name of each package you upload, making it easy for the community to recognize your contributions.

If you ever forget your password, you can refer to our guide on Resetting Your Password for assistance. Additionally, your password can also be reset via the account settings page when you are signed in.

Thank you for joining our community and contributing to the world of package management! If you have any questions or need further assistance, feel free to reach out to our support team.

Resetting your password

If you ever forget your password or need to reset it for any reason, follow these steps to regain access to your account:

  1. Visit our Website: Open your web browser and go to our website.

  2. Log In Page: On the login page, click on the "Forgot Password" or "Reset Password" link. You'll be directed to the password reset page.

  3. Email Verification: Enter the email address associated with your account. You will receive an email containing instructions on how to reset your password.

  4. Reset Password: Follow the link provided in the email. This will take you to a page where you can create a new, secure password for your account.

  5. Confirmation: After setting your new password, you will receive a confirmation message indicating that your password has been successfully changed.

Now, you can log in to your account using your updated password. If you encounter any issues during this process or have further questions, please feel free to reach out to our support team.

API Keys

API keys let you authenticate the pxpm CLI without an interactive login — ideal for deploy scripts and CI pipelines. Requires pxpm 1.1.0 or newer.

Creating a key

  1. Sign in to the website and open the Account menu, then choose API Keys.

  2. Name the key after where it will be used (for example, "production deploy server") so you can recognize it later.

  3. Choose an expiration: 30, 90, or 365 days, a custom date, or never. For unattended machines like CI runners, "never" is acceptable as long as you revoke the key when it is no longer needed.

  4. Copy the key immediately — for security reasons it is shown only once, right after creation. If you lose it, revoke it and create a new one.

Using a key

Set the PXPM_TOKEN environment variable in your deploy or CI environment (recommended; nothing is stored on disk):

PXPM_TOKEN=<your-api-key> pxpm install

Or log the machine in once with the key:

pxpm login --token <your-api-key>

Managing keys

The API Keys page lists all of your keys with their creation date, last-used time, and expiration. You can revoke any key at any time — anything still using it will stop authenticating immediately. Tokens created by signing in on the website or through the interactive CLI login also appear here, marked with a "Website login" or "CLI login" badge, so you can review and revoke active sessions as well.

Keep your keys secret. Anyone with your key can access packages on your behalf. Prefer your CI system's secret storage over committing keys to files.