The user's files come first.
Folders you can find. Archives you can move. No mystery dashboard holding the keys.
RoachWares LLC
Independently built by a stubborn Roach.
Hey, I’m the solo developer behind RoachWares, and I’m sick of the cloud renting me my own productivity. That’s why I’m building RoachNet.
Think of RoachNet as the offline-first shell for everything that should actually live on your machines: AI models, personal archives, media, games, notes, and serious dev work. RoachWares is the company behind that work.
Independent software with a custody line.
RoachWares exists to make local-first software feel serious again: native apps, public release rails, and a hard boundary around what never belongs to someone else's login page.
Company
One developer. One bunker. Fewer excuses.
RoachWares is a founder-run software company with one clear operating line: if the tool handles something important, the user should be able to see where it lives and move it when they need to.
The company stays small on purpose. It keeps the release path short, the custody model obvious, and the excuses harder to hide behind.
- Founder run, not committee shaped.
- Public releases with inspectable artifacts.
- Local custody as a product constraint.
Operating model
Small company. Short chain of command.
RoachWares is structured like a workshop, not a platform department: clear standards, visible output, and no ritual unless it improves the software.
01
One accountable builder.
The same person designs the interface, cuts the release, tests the installer, and uses the software on real machines.
Company 02 Proof over pitch.Release artifacts, docs, casks, and source trails stay visible. A quiet paper trail beats a loud promise.
Releases 03 Network in its lane.Online systems help with discovery, updates, and metadata. They are plumbing, not the place where your work lives.
RoachNet 04 Small tools earn air.Experiments ship only when they solve a real problem, survive daily use, and make the stack quieter than it was.
GitHub
Principles
Standards, not slogans.
RoachWares keeps the company rules short because the software has to be judged by what still opens when the network gets useless.
The machine should feel awake.
Apple Silicon builds get treated like the main road, not an afterthought in a wrapper.
Distribution is not ownership.
GitHub, Netlify, Convex, and CI can ship updates. They do not get custody.
No ceremony without proof.
Every panel, service, and feature has to earn the noise it adds.
Public surface
The public record is part of the product.
Releases, casks, docs, feeds, and issue history are not marketing clutter. They are receipts for users who like checking the bolts.
Open release lanes
Custody boundary
The network helps. It does not hold the work.
RoachWares uses online rails where they make sense and keeps the load-bearing pieces on the user's machine where they can be backed up, moved, and understood.
RoachWares on GitHub
Company record
Open release log
May 12, 2026
RoachWares
RoachWares.org becomes the independent company home.
Company
May 2026
Infrastructure
Company site isolated on its own Netlify project and domain.
Rails
v1.0.4
Product line
RoachNet release lane, installer, Homebrew, and docs.
Product
For the right people
A company for people who still trust their own machines.
RoachWares is for people who would rather inspect a build than decode a pricing page.
The bet is simple: a useful software company can be small, direct, public about its release path, and stubborn about keeping custody close to the machine.