Contributors

Built by people
who care about craft.

Nyxever is an open project. The people behind it believe that good infrastructure is made deliberately, documented honestly, and improved by anyone willing to do the work.

Founder

Charles Côté

Founder & Systems Architect

Charles is a systems architect with a career built at the intersection of infrastructure, security, and operations. He has designed and operated environments across network engineering, cybersecurity, and distributed systems — in environments where getting it wrong has real consequences.

Nyxever is the distillation of that experience into an open platform: the architecture patterns, operational practices, and accumulated judgment that come from years of doing deep work without shortcuts. The goal is to make that foundation available to anyone willing to learn it.

How to contribute

Docs Improve the documentation If a page explains the how but not the why, or something is unclear or wrong, file an issue or propose a fix.
Practice Share an operating practice Hard-won operational knowledge is valuable. Write up what worked, what failed, and the context it applies to.
Decisions Challenge a decision Read the decision records. If you have new information or a better option, make the case in the issue tracker.

The mission has room for more people.

The goal is a reference foundation for resilient infrastructure, built on open technology, with architecture guidance and best practices that anyone can learn from. That’s the north star. Getting there means the documentation has to teach, the configuration has to be readable, and the decisions have to be visible. That work is too large for one person.

If you understand distributed systems, network architecture, storage, identity, or observability — and you care about building things that actually work and can be explained — there is meaningful work here. Documentation that teaches rather than just describes. Configurations that are readable rather than just functional. Tools that expose their reasoning rather than hiding it behind abstractions.

Contributions don't require permission. The project is open. Start with an issue, a documentation improvement, or a question worth answering well.