zerotrustnetworkaccess.info

This ZTNA vendor directory is curated and maintained by the team at https://enclave.io and other contributors. We hope you find it useful.

Like us, you might also be fed up with the outlandish Zero Trust marketing claims and hype coming from some vendors.

We believe Zero Trust Network Access is here to stay, and that the community as a whole benefit from honest, impartial, and open knowledge. We built this site as a technical resource to help bring engineering discourse back to the conversation and to highlight the different architectures, approaches, and options.

Contributing

A big welcome and thank you for considering contributing to the the The no-bullshit ZTNA vendor directory!

It’s people like you that will help to ensure this is a site useful resource for the community as a whole benefit from honest, impartial, and open knowledge about the vendors operating in this space.

Before getting started

Reading and following these guidelines will help us make the contribution process easy and effective for everyone involved. It also communicates that you agree to respect the time of the developers managing and developing this open source project.

In return, we will reciprocate that respect by addressing your issue, assessing changes, and helping you finalize your pull requests.

We love your input! This is a fast-moving and incredibly diverse space. We want to make contributing to this project as easy and transparent as possible, whether it's:

• Reporting a bug
• Adding a new vendor or architecture
• Reclassifying an existing vendor into a different architecture
• Improving the strengths, weaknesses and trade-offs of each architecture
• Addressing inaccuracies or mistakes
• Discussing the current state of the code
• Submitting a fix
• Proposing new features
• Becoming a maintainer

How to contribute

We Develop with Github

We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.

We use GitHub Flow, so all code changes happen through pull requests

Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:

1. Fork the repo and create your branch from main.
2. Test your changes to make sure they work as expected.
3. Ensure the test suite passes.
4. Make sure your code lints.
5. Issue that pull request!

Any contributions you make will be under the MIT Software License

In short, when you submit code changes, your submissions are understood to be under the same GPL 3.0 license that covers the project. Feel free to contact the maintainers if that's a concern.

If you need further guidance, you can contact team@enclave.io or join us on Slack at https://enclave.io/slack