Magnexis is an independent software organization building practical open-source technology across the developer stack.

Our work ranges from focused libraries and package ecosystems to programming languages, operating-system experiments, distributed infrastructure, desktop tools, APIs, developer platforms, and public-interest software.

We build in the open because software is easier to trust, improve, and extend when its architecture and implementation can be inspected.

Software should not be a black box.

Contributions are welcome. By submitting a contribution for inclusion in a Magnexis repository, contributors agree to the Magnexis Individual Contributor License Agreement. Contributors retain ownership of their work while granting Magnexis and downstream recipients the licenses necessary to use and distribute it.

• repo-dna — Repository intelligence for understanding the structure, identity, and evolution of software projects.
• stackmend — Software intelligence and repair tooling for understanding real systems and diagnosing failures.
• APIHub — A platform for discovering, organizing, and working with developer APIs.
• bridgeABI — Interoperability infrastructure for connecting software across ABI boundaries.
• permissionkit — Reusable permission and policy primitives for application development.

• typeYAML — A typed superset and tooling ecosystem for structured YAML workflows.
• Proton — A systems-oriented programming language and runtime experiment.
• COBOLX — A modern COBOL-inspired language platform for readable, deterministic business logic.
• Steel — A language experiment focused on approachable syntax and custom execution tooling.
• go-idempotent — Reusable idempotency primitives for Go services and applications.
• go-shutdown — Structured shutdown and lifecycle coordination for Go applications.
• lifecycle.NET — Application lifecycle coordination and shutdown infrastructure for .NET.

• Omniforge — A local-first distributed execution fabric built around the Omniforge Protocol.
• AetherOS — A modern desktop-shell and operating-environment foundation.
• Obsidian Linux — A reproducible Debian-based Linux distribution experiment.
• anti-cloud — Local-first and resilient infrastructure designed to reduce unnecessary cloud dependence.
• Agent Portal — A desktop-native environment for controlled agent interaction with real user interfaces.
• Agent Studio — A development environment for building, supervising, and operating software agents.
• LLM Bridge MCP Server — An MCP server for model access, repository inspection, and local-first development workflows.

• AquaStat — Water-aware infrastructure data and estimates for understanding data-center water usage.
• Public Oversight — Open tooling for civic transparency, public records, and technology accountability.
• Grid Share — Experimental infrastructure for distributed energy and resource coordination.

• PaletteSmith — A Figma-oriented color and design-system generation tool.
• GitPad — A lightweight developer workspace for Git-connected writing and editing.
• Pixel Wall — An experimental collaborative visual surface.

Public code, visible decisions, and reviewable architecture create stronger software.

Small libraries and modules should solve real problems and compose cleanly into larger systems.

Local-first operation, portability, clear data boundaries, and minimal lock-in matter.

Diagnostics, documentation, observability, and explicit behavior are core product features.

Experimental work should still have coherent structure, reproducible setup, honest documentation, and a clear purpose.

Projects should be inspectable, reusable, extendable, and open to thoughtful contributions.

Magnexis repositories span multiple ecosystems:

TypeScript · JavaScript · Go · Rust · Python · Ruby · C# · .NET · C++ · Lua · React · Next.js · Vite · Node.js · FastAPI · PostgreSQL · Docker · GitHub Actions · Linux

The exact stack varies by project. Each repository should document its runtime requirements, development workflow, release process, license, and stability level.

Contributions are welcome throughout the organization.

1. Choose a repository and review its README, issue tracker, and contribution guidance.
2. Open an issue before beginning a major architectural change.
3. Keep pull requests focused, documented, and testable.
4. Include tests or clear validation steps when behavior changes.
5. Report security-sensitive problems privately when a repository provides a security policy.

Bug reports, compatibility testing, documentation improvements, design feedback, and focused pull requests are all valuable.

Magnexis contains projects at different stages of maturity. Review the documentation, releases, open issues, and stability notices in each repository before depending on it in production.