PWSLab External User License Policy

PWSLab External User License Policy


The External User License Policy is primarily for the benefit of customers who want to add temporary External users in PWSLab. This is offered because we don’t want you to follow a cumbersome or inefficient way of accepting external code contributions into your projects, citing pricing reasons.

External users/developers are Freelancers/part-time resources who generally work less than 40 hrs per week and contribute code to your company’s projects in PWSLab.


  1. Pricing for an External user will be only 25% of the Regular user License pricing.
    For example - If the monthly license cost for a user in Standard Plan is ₹1500 then the monthly license cost for an External user will be 25% of ₹1500 i.e. ₹375 only.

  2. External users should not be given a company email address to access PWSLab. This is a strict precaution taken to avoid any code-theft or access to unauthorized resources within PWSLab. They can access PWSLab with their Personal email address only.

  3. At the time of user creation, the Admin should add the Freelancer/Part-time resource as an External user only. If you create them as a Regular user, it will be automatically considered as a Regular user. Learn more about an External user in PWSLab and how to create them.

  4. Customers have to share the expected number of External users in advance every month (in the last week of the current month), as invoices will be raised manually for this kind of engagement.
    For example – For October, you have to share the expected External users, by the last week of September.

  5. If the number of External User Licenses requested in advance is less/more than the actual licenses used in that month then the difference amount will be adjusted in the next month’s invoice.
    For example – If you expect 50 External users to be added in October, you share this figure with us by the last week of September. So October’s invoice will include the payment for all Regular users and 50 External users. But, if by any chance you have created only 30 External users in October, the difference amount collected for the remaining 20 External users will be adjusted in the November’s invoice. 
Note - For any reason, if you fail to share the expected number of External User Licenses, we will by default consider a request for the same number of users as the previous month.


If you have any specific billing-related questions regarding your PWSLab subscription, you can send an email directly to PeerXP’s billing team at

Have more questions? Please email us at
Also, let us know if the article is helpful!

    • Related Articles

    • List of PWSLab CI/CD Environment Variables

      Introduction This document enlists a set of pre-defined environment variables accepted by PWSLab CI/CD for the local environment of the Runner. These can be referenced directly in the .pwslab.yml file or via the Project's Settings > CI/CD > ...
    • How to create and manage External users in PWSLab?

      Introduction In cases where it is desired that a user has access only to some internal or private projects, there is the option of creating External Users in PWSLab. This feature may be useful when for example a Freelancer/Part-time resource is ...
    • Billing Policy for PWSLab Accounts

      Introduction PeerXP offers a DevOps as a Service solutions for enterprises - PWSLab. Pricing plans are based on the number of users/projects for different PWSLab products and services.  If your team doesn't fit neatly into one of the Pricing plan ...
    • Mirroring PWSLab Repositories to GitHub, Bitbucket and GitLab or any Git repositories

      Introduction Repository mirroring allows for mirroring of repositories to external sources. It can be used to mirror branches, tags, and commits between repositories. A repository mirror at PWSLab will be updated automatically. You can also manually ...
    • PWSLab Git Workshop - Useful commands and concepts

      Agenda A brief history of Git. PWSLab walkthrough. Configure your environment. Workshop. Git Introduction Visit: Distributed version control. It does not rely on a connection to a central server. Many copies of the complete ...