An independent software studio

Why self-hosted

Most software asks you to trust somebody else’s server with the things you care about most: your trading account, your passwords, the licenses you sell. When that server changes its prices, its terms or its security, you find out last.

Each of our products takes the opposite approach. TigerTradeBot runs on your computer and talks to your broker directly. TigerPassword keeps an encrypted vault on your devices and syncs it through storage you already use — there is no TigerCodes server to breach. TigerLicense is a license server you run yourself, and the licenses it signs keep verifying even if we disappear.

Our three newest products, still in development, follow the same line. TigerClean scans and cleans on your Mac and sends no file names anywhere. MailTiger talks straight from your devices to your mail provider, with no TigerCodes server in the middle. RemoteTiger connects your devices to each other directly, and when it needs a relay, the relay forwards encrypted traffic it can’t read.

How we build

Secure defaults

Two-factor sign-in is mandatory in TigerTradeBot. TigerPassword derives keys with Argon2id and encrypts every item with XChaCha20-Poly1305. TigerLicense signs licenses and updates with RSA-4096. This website follows the same rules: no cookies, no trackers, no third-party scripts, a strict content security policy, rate limits on every API request, and a short-lived, single-use signed token behind every message sent through the contact form.

Paper first

TigerTradeBot starts every install in paper trading. Live trading only begins when you connect a broker and choose to. We never quote returns or win rates, because software can’t promise either. Trading involves risk of loss, and nothing on this site is financial advice — read the TigerTradeBot risk disclosure.

Honest labels

TigerPassword is a release candidate, and it stays labeled that way until an independent security audit is published. TigerClean, MailTiger and RemoteTiger are labeled pre-release until they ship. We don’t call anything open source until its source terms are settled, and every status on this site comes from the same product data the pages are built from.

One stack, used on ourselves

Our servers are written in Go, our web front ends in Lit, TigerPassword’s core in Rust, and our Mac, iPhone and iPad apps in Swift. We sell our own products with TigerLicense, so every bug a customer could hit, we hit first.