Loading... Background job is running.
Subscription price includes:
€49 / mo
€ 0 / mo for 0
€ 0 / mo for 0
€ 0 / mo for 0
€ 0 / mo for 0
For Public Package Publishing
€ 0 / mo for 0
Please contact us for additional pricing information
- 14 Days Free Trial
- Email and chat support
- Starts at €49/mo
- Unlimited private packages
- Unlimited git/svn/hg repositories
- Unlimited mirrors
- Team based user permissions
- Security Monitoring
- Separate Composer repository per client project (subrepositories)
- Client-specific credentials per subrepository
- First 3 users and 3 subrepositories included
- One free subrepository for each user
- Free auth tokens for CI/deploy
- Making individual packages available through Composer to customer developers
- Unique URL and auth token for each customer
- Restrict package access based on versions or timeframe
- First 49 customer packages included
- At most €9 per customer per month
- Support for Git, Mercurial, and Subversion
- Access to private code through: SSH, GitHub, GitLab or Bitbucket API Tokens / Apps, or HTTP Basic Authentication
- Composer JSON inline package definitions for packages without Composer support
- Hooks to update package information immediately when you push code
- Import for Satis and JSON repository lists
- Synchronization of packages, teams, members and permissions with a GitHub, GitLab or Bitbucket organization
- Package search
- Version specific package install statistics and graphs
- API access
- Unlimited private and open-source packages
- Unlimited package installations
- Unlimited mirroring of packages on packagist.org or any other Composer repository, e.g. repo.magento.com
- Security Monitoring to alert you of vulnerable dependencies in Composer projects
- License review for all mirrored and private packages
- Authentication tokens for your continuous integration or deploy environments
- Unlimited teams with per-package permissions
- Per-user authentication tokens to easily revoke access for individuals
- Unique Composer repository URL and authentication token per customer
- Grant customers access to individual packages
- Restrict package access by version constraint or timeframe to match your licensing model
- Granular per-customer version specific install statistics
Frequently Asked Questions
Who is a user / How many people do I need to pay for?
Every real person who accesses Private Packagist through the web interface, composer update, or composer install must have their own user account on Private Packagist. Automated systems, who are not humans, are not users. They may use free read-only authentication tokens.
How many users do I have to pay for if I set up a synchronization with GitHub, GitLab, or Bitbucket?
Only users that create a Private Packagist account will count towards the user limit. Active members can be removed at any time and you can prevent them from automatically joining your Private Packagist organization.
What is a subrepository?
Subrepositories are separate Composer repositories with their own URL, authentication tokens and a separate list of packages.
Subrepositories allow you to keep client packages separate, while sharing common organization packages, e.g. at an agency. This is particularly useful if your clients run Composer commands, or if you purchase packages on behalf of clients and don't want other clients to have access to them through Composer, or if you need to mirror packages with client specific credentials, e.g. merchant keys on the Magento Marketplace.
For some agencies a single main Composer repository suffices, others need the separation offered only by subrepositories. You can always start without subrepositories and add them later.
How do I add or remove users and subrepositories? Do I get money back?
You can add or remove users and subrepositories in your organization at any time. When adding them you will be charged a prorated partial amount for the remainder of the subscription period on your next invoice. If you remove a user or a subrepository you will receive a discount for remaining days on your next invoice.
Which payment options do you offer?
You can pay by credit card, we support all major card providers: Visa, MasterCard, American Express, Discover, Diners Club and JCB. Alternatively if you sign up for an annual plan you can contact us to set up payments by SEPA or SWIFT wire transfer to a German bank account identified by an IBAN and a BIC.
Is there a free trial period and how does it work?
All our cloud plans come with a 14-day free trial period. At the end of the trial period, access to your organization will be disabled until you sign up for a subscription. You can enter your billing information at any time during the trial period, and you will always only be charged after the full free trial period. If you need to extend your free trial please email firstname.lastname@example.org.
What level of e-mail and chat support is included? Is there an SLA?
We guarantee next business day responses to all messages sent via email or website chat. All our support is provided by engineers with their own experience in PHP development. We often respond within an hour during business hours on workdays but response times may vary depending on support volume and availability of engineering staff.
Do the prices include VAT?
All prices are exclusive of any local taxes and VAT. European customers are charged their local VAT rate. Please provide your VAT-Id when signing up to remove VAT from invoices (Reverse Charge).
Do you offer invoice billing, do you accept purchase orders and can you send a quote?
For monthly subscriptions we can only accept credit card payments but if you would like to sign up for an annual plan, please email email@example.com and we can set up alternative payment methods or send you a quote or an offer letter document.
Do you offer refunds?
We do not offer refunds, all sales are final. You can cancel your subscription at any time by clicking the cancel button under settings, and you will not be charged again.
What is a customer package? How many do I need?
The vendor add-on is priced based on how many times you grant customers access to packages.
Let's say you have 3 customers Acme, Globex and Initech, and are selling two packages foo/assemble and foo/integrate. Acme gets access to both packages, Globex only has access to foo/assemble and Hooli can only access foo/integrate. Then you have one customer who can access two packages, and two companies that can access one package each, so a total of four customer packages.
You never pay more then €9 for an individual customer, even if they have access to more than 9 packages.
What is the difference between a read-only token for CI/deploy and a user token?
Running composer update or require with an update token, which each user receives by default, will automatically mirror newly required packages from packagist.org or other mirrored third party repositories into your Private Packagist organization.
Read-only authentication tokens are designed for automated processes like CI or deployments. These processes should have predictable results, so these tokens will never automatically add any new packages to your organization.
We recommend using read-only authentications for composer install commands with a lock file present, and using personal user update tokens on development machines for other composer operations.
Is there a discount for non-profits or educational institutions?
Please send us documentation of your charitable status or recognition as an educational institution in your local jurisdiction and we will provide you with a 25% discount code.