VyOS Community

VyOS started as a community project, and retains that spirit. The entire code base is open for contributions. Even if you are not a programmer, there’s a lot of things to do: writing documentation, answering questions on the forum, testing rolling release images and reporting bugs.

Starting from VyOS 1.2.0, only rolling release builds are available publicly, while LTS releases are only available to subscribers. However, it doesn’t only mean commercial customers! Every active contributor is eligible for a subscription too. We are doing hard work maintaining LTS releases, and we are ready to share the results of that work with everyone who helps us move the project forward, whether they contribute to the project financially by purchasing a subscription, write code, write documentation, actively test VyOS and make good bug reports, or spread the word.

You can apply for a contributor subscription by filling out this form.

How to become a contributor?

There are many meaningful ways in which you can contribute to the VyOS project. We will consider anyone a contributor if they are actively involved in the development of VyOS and do their best to help push the project forward in the following ways:


  • Developing new features.
  • Fixing bugs.
  • Testing VyOS on previously untested hardware.
  • Testing new VyOS features.
  • Reporting  bugs.


  • Promoting VyOS on social media platforms such as Twitter and Facebook
  • Making video tutorials and sharing them on platforms like Youtube and Vimeo
  • Writing blog posts about VyOS
  • Giving talks about VyOS at industry conferences, conventions, etc.
  • Answering questions and suggesting VyOS on public forums such as Spiceworks, Stackoverflow, etc.


  • Helping with documenting new features, improving existing documentation, or rewriting legacy documentation from Vyatta Core.
  • Supporting people on the forums, IRC, or the Slack channel.  This also includes support in localized VyOS forums and/or the creation of localized channels such as the Japanese VyOS community. 
  • Creating detailed feature requests to the developers that would help push the project forward and expand the capabilities of VyOS. 
  • Participating in feature design and architecture discussions.

Much more than good Karma

Being a part of an open-source project is a remarkable experience. Not only do you get the chance to join a passionate community with similar interests, but you earn the right to grow, learn from the best, and make a name for yourself among the people who actually care. Speaking of which, an ongoing bond will boost your reporting, communication, and soft skills as a natural bonus of the open-source relationship.

Become a part of something grand and influence the world through creating something everyone can benefit from!

No skillset lock-in

Despite a common misconception, not everyone involved in open-source development is a software engineer. A project–any project–needs much more than brains and muscle. Writing documentation, managing the community, guiding the team in an appropriate direction, quality assurance, UI, UX, and brand design are just the tip of the typical open-source activities iceberg.

If you have found a project you’d love to be a part of–reach out and in ten cases out of ten you’ll be welcome to join an aspiring team!

How do I sign up?  

If you don’t know where to start, documentation is your best bet. Our documentation is available at vyos.readthedocs.io. To contribute a fix or an improvement, you should create a pull request in github.com/vyos/vyos-documentation.

If you want to test latest VyOS code, grab the latest rolling release image and give it a try. For best results, you may want to run it on your home or lab routers, or try loading your production configs and check if they load correctly. All bugs should be reported in our Phabricator.

If you want to start writing code, you should find or make a Phabricator task first, then reference it in your commit like “T9999: fix handling of the evil bit in IPv6 packets”. Commits with proper ticket references are automatically linked to tickets. Since VyOS consists of more than one repository, tracking changes and writing changelogs is complicated without a central location, so we use Phabricator for that. It also helps ticket watchers know that a fix is available and help you with testing.

Who owns the copyright to contributions?

You do. VyOS intentionally doesn’t have any kind of a contributor agreement and doesn’t require contributors to give up any rights to their code. When the copyright is shared between all contributors, it’s impossible to change the license from GPL/LGPL to something else and create a closed-source version. This guarantees that the project will stay free and open source forever.