Hexaxia Labs

Hexaxia Labs is the open source arm of the Hexaxia Group, a collective of operating companies. Hexaxia Technologies does managed IT, infrastructure, and security consulting. Hexaxia AI runs AI transformation engagements and builds AI infrastructure products. Hexaxia Media handles the creative and media side of the group.

Each division does different work. Some of it is client-specific. Some of it is not. Labs is where the second kind lives.

The projects here grow out of real work across the group: hardening production systems, building compliance baselines, shipping tooling that solves problems we actually have, and integrating AI into infrastructure that has to stay accountable. When something is general enough to be useful outside our own operation, we open source it.

What is shipping right now

HexOps. A developer operations dashboard for engineers who manage a lot of projects at once. When a CVE drops and fifteen repos need patching, HexOps handles concurrent scanning, batch patches, post-patch audits, transitive dependency overrides, and collateral-downgrade flagging from one interface. Includes a code security scanner with sixteen grep-based rules for hardcoded secrets, command injection, weak crypto, and common misconfigurations. MIT license.

HexCMS Studio. A local visual editor for git-based content. WYSIWYG and raw markdown modes, frontmatter editor, live preview, git integration that lets you stage, commit, push, and pull without leaving the UI. Multi-repository support. MIT license. HexCMS, the git-based headless CMS underneath, is in development on AGPL-3.0.

389DS SRG Baseline. A machine-consumable hardening catalog for 389 Directory Server. Forty-three NIST 800-53 and DISA SRG-mapped controls across nine domains. Schema-first markdown source of truth: documentation site renders from the frontmatter, and future phases generate Bash audit scripts, Ansible roles, and OpenSCAP XCCDF content from the same files. Applies to 389DS directly, Red Hat Directory Server, and Red Hat Identity Management. v0.1.0-alpha. GPL-3.0.

How we decide what to open source

The bar is simple. Did this solve a real problem in our own work? Could it solve the same problem somewhere else without us having to be in the loop? Is the code something we are willing to defend? If yes to all three, it goes here. If no, it stays internal.

We do not open source for community-building, social proof, or contribution metrics. We open source because keeping useful tools private is a waste when the gap they fill is general.

Contributing

Pull requests are welcome on every active project. Issues are how most conversations start. If you are not ready to open a PR but want to flag a problem or propose an approach, open an issue and start the discussion. The contribution guide and code-of-conduct live in each repo.

389DS SRG Baseline in particular needs validation testing from people who run 389DS, RHDS, or Red Hat IDM in production. If that is you, running a control's check command against your real instance and reporting the result back is the contribution this project needs most right now.

Get in touch

The fastest path is opening an issue on the relevant repo at github.com/Hexaxia-Labs. For broader questions about the Hexaxia Group or for engagements that fall outside open source, the operating companies are the right door: hexaxia.tech for managed IT and infrastructure work, hexaxia.ai for AI engagements and products, hexaxia.media for creative and media work.