Web apps
A browser is the right place for some of this, and the wrong place for most of it
Anything that only involves your own files belongs on your own machine. What genuinely belongs on the web is the stuff that has to reach someone else.
Not open yet. In active development. Listed so you know the shape of it.
ArmoredSend
Secure messaging that sits on top of the email you already use. You send from your normal inbox, your recipient clicks through and reads on a clean page with your logo on it.
The thing I'm reacting to is the attachment named securedoc.html. If you've received one you know the feeling, a file that looks exactly like malware, from a bank, asking you to open it and log in to something. Half the point of secure messaging is the recipient trusting the message enough to read it, and that attachment actively destroys that.
Encrypted links, chat and intake forms in one place. Recipients are always free, because charging the person receiving your message is a good way to make sure your message doesn't get read. Zero-knowledge in the real sense, the key is not mine to hand over.
The account layer under all of it
This one isn't a product you buy, it's plumbing, and I'm describing it because it explains why the rest exists in the order it does.
Every product I make signs into one shared account system. One login, one place your licences live, one place your subscriptions are visible. If you buy the rank tracker and later the encryption tool, that's one account and one billing relationship, not two vendors who happen to be the same person.
I built that first, before any of the products on top, which felt slow at the time. The alternative was seven products each with their own bolted-on login and no way to ever join them up, and retrofitting that later is the kind of job that never gets done.
One account, and any single product can go away without breaking the others or locking you out of the ones you kept.
There's a practical consequence for you. Because the licensing lives in its own layer rather than inside a storefront, a website going down cannot stop the software you already paid for from working. That is a deliberate separation and it's the sort of thing you only appreciate the day something breaks.
Two stores, same account
You'll eventually be able to buy the same products from two places. This site, which is my own name, and a separate storefront under the OctoIO brand. Same catalogue, same account, same licences.
Why two? Because some people would rather buy from a person and some would rather buy from a company, and I'd rather not force that choice. Whichever one you use, your account works in both.
FAQ
If it's a web app, isn't my data on your server anyway?
For ArmoredSend, what's on the server is encrypted with a key I don't hold, so it's stored but not readable. That's a genuinely different situation from a tool that encrypts in transit and keeps a copy of the key for convenience. I'd rather you check that claim than take it, so it's written into the product docs and not just this page.
What happens if you stop working on one of these?
Fair question to ask a one-person shop. For the desktop apps, the answer is that a licence you own keeps working on the machine it's on. For anything web-hosted, I would give notice and an export rather than a shutdown email one Friday. I can't put a contractual SLA behind that yet and I'm not going to pretend I can.
Is there a free tier?
Recipients of an ArmoredSend message never pay, that part is settled. Beyond that I haven't set pricing, and I'd rather leave it open than announce a number I change later.
Can I try it before it launches?
Ask me. Send a note saying which one and roughly what you'd use it for. Early testers who describe a real workflow are more useful to me than a long waiting list, so those messages get read properly.