Your licence works offline
Licences verify against a key compiled into the application itself. If our servers vanish tomorrow, the software you paid for still opens. That is a design constraint, not a promise.
Windows software that runs on your own computer, not on somebody else's. Graphics card tools, dictation that works offline, phone to desktop, and software for running a business. Bought here, downloaded here, updated here.
Everything in the catalogue is still in development. You can read what each application does, what it needs, and what it cannot do yet. Nothing here is open to download or buy. Leave your email and you will hear from us the day that changes, once and about that only.
Every application here was written to solve a problem in our own workshop first. That is why they are narrow, fast, and free of the features nobody asked for.
These are not marketing lines. Each is a constraint the platform is built around, and each is testable.
Licences verify against a key compiled into the application itself. If our servers vanish tomorrow, the software you paid for still opens. That is a design constraint, not a promise.
Every release publishes a reference code for the exact file we built, and your computer checks it for you before anything is installed. You never have to take our word for what landed on your machine.
One application in this catalogue is a 19 GB download. If it stops, it picks up where it left off, and a small fix only downloads the part that changed rather than the whole thing again. Nothing is metered.
No approval queue, no category somebody else put us in, no reviewer deciding when a fix reaches you. A fix goes out the moment it passes our own checks.
Small businesses call us with something slow, expensive or annoying. We work out what is actually wrong and tell you how to fix it, including when the honest answer is that you do not need us to build anything.
Every release has to pass a full run of checks before it is allowed out, and the result of that run is published beside the download. The counts, and whether it passed or failed. A failed run reported honestly is a fine outcome. A confident sentence with no numbers behind it is not.
// every release, before it goes out every function still works ...... pass every screen looks right ........ pass every button leads somewhere .... pass the file is the one we built .... verified // one failure anywhere and the release does not go out