Terms before a purchase
Each application has its own planned purchase model and device requirements. Review the actual release terms when it becomes available. The website is not currently issuing software licences.
Apps for Windows, Android and the web, plus custom software, automations and AI for small businesses. Graphics card tools, offline dictation, phone to desktop, design and motion tools, AI bots, and software for running a business.
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.
These projects address problems in our own workshop and business workflows. Each page distinguishes current functionality from proposals, private previews and paused work.
These are not marketing lines. Each is a constraint the platform is built around, and each is testable.
Each application has its own planned purchase model and device requirements. Review the actual release terms when it becomes available. The website is not currently issuing software licences.
Private release pages show the file size and SHA-256 reference value. You can compare the downloaded file yourself before installing it. Installation and device checks depend on the actual package.
Private release delivery supports downloads that resume after an interruption. Available files and their device requirements appear with the release. An update downloads its complete release file; application installation depends on the product.
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