1. Getting started

First, you’ll need to decide which services you want to offer. Popular services are:

  • Support hours: Offer an hour bank for support.
  • Bug fixing: Provide bug fixing or priority issue solving
  • Consulting: Share your expertise and provide project related guidance
  • Customization: Add custom features per request

2. Import your Github repository

Now, add your Github repository, which is the foundation on which you will create your paid items.

Click “Add repository” and follow the instructions. Your repository has to be public, and you’ll need to install our Read-only Github app on you repository for verification purposes.

3. Create a “Service” item

Now, create your paid item. In the repository editor, click “Add item“, and select the “Service” item type. Be sure to add a description of exactly what you are offering, and if you have any special terms, such as your availability.

4. Set a price

Choose your item’s price and billing model:

  • One-time payment
  • Monthly \ Annual subscription

Subscriptions are great for providing ongoing support or maintanance. You can create both subscriptions types, each with a different price.

5. Update your Readme.md on Github

The best place to start promoting your paid items, is on your readme file.

Use our badge to place a link to your xs:code repository page to notify your users about the items you are offering.

You can also use social media, blogs and developer community websites to promote your project.

Need any help? Our community team is here.

Click on the chat icon or email us at: [email protected]

Setting up your items

Can’t decide what to offer? Need help with pricing? Get one-on-one guidance.

Technical support

Our support team is here to help with any technical issue via Chat or email.

Marketing & promotion

There’s a lot you can do to get more paying users. Get our best practices and tips.

Ready to Get Started?

Read more: Paid CodePaid Licenses

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.