Agenxy

Agenxy develops sovereign software.

About

Agenxy is a collection of open-source projects. Each runs on your own machine.

Every project is open source and free, and is built to require no third-party service, commercial hosting, subscription, or data collection to be fully functional.

All of it is licensed under Apache 2.0 and runs locally. No project sends usage or diagnostic data to Agenxy, and none requires an Agenxy account or a service we host.

How the work is done

Small, exact tools that do one thing. A tool that reports is better than a tool that acts on your behalf and is sometimes wrong. Where a limit exists it is written down: in the documentation, in the security notes, and in the code comments beside the thing it limits.

The register on the front page is the whole catalogue. There is no roadmap of unbuilt things and no product that exists only as a page.

What we will not do

  • Collect telemetry, or ship an analytics script, here or in any product.
  • Require an account to run software you have downloaded.
  • Pay for placement, listings, or reviews.
  • Claim a security property the implementation does not have.

This site

The site is files on disk. There is no server, no database, no backend and no login, so there is nothing running here to attack and nothing stored here to leak. The typefaces are subsetted from upstream and committed; the texture is generated in the page at your display's pixel density.

One page departs from that, and it does not change it. Contributing reads the open issues from GitHub in your browser. The request is anonymous and carries no key, because the data is public — the same list anyone can see on the repositories themselves. It is worth knowing that GitHub sees the request, as it would if you had opened the issues directly. Nothing about it comes back to us.

Every page has a Markdown twin for agents and command-line tools, listed in llms.txt. The writing is findings from building the software.

Contact

Issues and discussion belong on GitHub. Security reports have their own route, documented in security.txt.