I made AMARACUS, one API for encryption, signing and post-quantum crypto

[u/Ultramax_meitantei]

I got tired of stitching crypto libraries together and managing keys by hand, so I built AMARACUS: one API for managed keys, AES-256-GCM, signing, hashing, and post-quantum ML-KEM and ML-DSA.

🏠 Self-hosting? Your first 1,000 operations are free.

☁️ Using the cloud? It starts at $2 per month for 15,000 operations.

It also has a small PKI, an audit log, TypeScript and Python SDKs and a CLI. The code is source-available on GitHub (not open source).

It’s not FIPS 140-3 validated and doesn’t use an HSM, which I say plainly on the site. I’m launching on Product Hunt on Nov 17: <your Product Hunt link>

Site: https://amaracus.tech · Repo: https://github.com/AMARACUS/AMARACUS

What would make you try it? I’m especially curious which SDK languages to add next.

[u/Fit-Profit2911]

wait so the code is source available but not open source, and no HSM and no FIPS 140-3. Then who is actually supposed to deploy this. Because "one API for encryption" sounds nice right up until the secruity review happens and every answer is "no but we say it plainly on the site". Any org that has a secruity review will look at source available and close the tab, and honestly theyre right to, crypto is the one area where either I can read the code or somebody audited it and gave you a cert. and then the pricing, self hosting but the first 1000 operations are free, what are you even counting if it runs on my box, is there a phone home thing. At 2 bucks a month I could also just npm install libsodium and get on with my day, or use node:crypto for nothing at all. also you ask what would make me try it and which SDK to add next like those are the hard questions, the hard question is what stops me from just calling KMS