3,592Runs a monthacross every live integration
93%Auto-decidedno human in the loop
190+Countriesscreening and credit coverage
0Raw biometrics storedby design, not by policy
What we believe
These are not values on a wall. Each one closes a door that would have made the product easier to build and worse to trust.Four decisions we will not trade away
01Proof beats promiseEvery claim a system makes about a person should be checkable by a third party. Not logged. Not asserted in a dashboard. Checkable — by the counterparty, by a regulator, by anyone the person hands the receipt to.
02Hold nothingThe safest way to protect funds, keys and faces is to never hold them. We built the architecture around that constraint before we built a product on top of it, so there is no breach worth staging against us.
03The rail, not the businessWe do not compete with the companies on our rails. We will never launch a lender, a clinic or a ticketing brand. If an integration succeeds, our customer owns the customer — and the brand on the screen is theirs.
04Ship the whole thingA verification API leaves the customer to build eleven screens, a console and a billing loop. We ship the operation end to end, because the last mile is where projects die.
How we got here
Sieve Technologies became Sidaxis.
Same company, same team, same architecture. The name changed when the scope did — a sieve filters, and we had stopped filtering and started carrying.2021
Sieve TechnologiesFounded to solve one problem for banks: proving a live human was behind a transaction, without warehousing their biometrics.
2023
The rail generalisesLenders wanted the same proof. Then clinics, then landlords. The verification stopped being a feature and became infrastructure.
2025
Agents arriveLLMs could reason but could not act — no way to prove who authorised them, no rail to execute on. The authorisation layer became the thesis.
2026
SidaxisA new name for what the company had become: identity, payments and AI protocols as one layer. Same team, same architecture, a name that points where we are going.
How we work
Small team, remote-first, headquartered in Frisco, Texas.
Engineers talk to customers directly — there is no layer between the two.
We publish what is in progress, including the certifications we do not have yet.
Written decisions over meetings, and a receipt for every one of them.
Where we are
Sidaxis2591 Dallas Pkwy
Frisco, TX 75034
United States
Frisco, TX 75034
United States
Careers
If none of these fit and you think we are wrong about something on this page, write anyway. Tell us what we got wrong.Build the layer, not the feature
Protocol engineerRemote · Americas
Rust and Go. You will work on the settlement rail and the attestation format.Applied cryptographerRemote · Global
Selective disclosure in production, not in a paper. Liveness and selective disclosure.Forward-deployed engineerFrisco or remote
You land with a customer, configure their integration and leave it running. Half engineer, half product.Compliance leadFrisco
You take SOC 2 and ISO 27001 from in-progress to certified, and own the regulatory map across 190 countries.