Web applications
Nexylius
The independent software line the products below are published under.
- Role
- Founder — product, engineering and infrastructure
- Period
- 2025 — present
- Status
- Live
The problem
Most small utilities arrive with a price attached to something that costs nothing to run: an account before you can try them, a credit balance for work your own machine could do, telemetry you did not ask for, or a free tier that exists to become a paid one. The tools themselves are often simple. What is scarce is a set of them built by one person to one standard, where you already know the answer to what it costs and what it sends.
The approach
Nexylius is that standard, applied across a catalogue. Every product is free, with no account and no metering. Where the work can be done on the user's own machine it is — the extensions never upload an image, PasaFile moves files between two devices without the file touching a server, and High Bias and EqualStream process audio entirely in the browser. Where the code is mine to publish, it is published. The line covers browser extensions, browser-based applications and native desktop software, each on its own site, so a product is judged on its own terms rather than as a feature of a suite.
What it does
Free, with no account
Nothing in the catalogue asks you to sign up, holds a credit balance, or keeps a feature back for a paid tier. There is no paid tier.
Local-first where it can be
The extensions never upload a capture, PasaFile sends files between two devices without the file touching a server, and both audio applications process sound entirely in the browser. No accounts means no data to hold, and no telemetry anywhere in the line.
Open source where the code is mine
Six of the projects here link their own repository, and every one of them is MIT-licensed — all three extensions, and all three desktop tools.
Three kinds of software, one standard
Chrome extensions, browser applications and native desktop software in C++ and Python. Each runs on its own site and is documented on the hub, so the products stand alone rather than as parts of a suite.
Built and maintained by one person
Every product in the catalogue is designed, built, deployed and maintained by the same author, which is why the commitments above hold across all of them.