Qeet ID — the first product Qeet Group built — is available today. Teams can sign up and have production sign-in working the same afternoon. The product and its documentation live at id.qeet.in.
We started Qeet ID from a question we kept hearing inside other organisations: why does every engineering team still have to choose between identity software that is pleasant to work with and identity software that satisfies a security review? Those have been treated as separate categories of product for fifteen years, and the result is that teams either outgrow their tooling at the worst possible moment or pay for capability they will not need for years. We do not think that trade is permanent. Qeet ID is what closes it.
What is available
The things an organisation actually needs from identity, in one place. Signing in with a password, without one, or with a code. A second factor, and recovery when someone loses it. Deciding what each person may do, once, and having every product respect that decision. Software that needs access getting its own credentials rather than borrowing a person's. And a record of consequential actions that can be produced later and shown not to have been altered.
What "available" means, and what it does not
It means the capabilities above run in production and organisations are using them.
It does not mean finished. More integrations are coming, the first software libraries are being written, and parts of the platform's edges want more depth. Formal security attestation is on the roadmap and is not claimed today — when it exists, we will say so, and not before.
The point of shipping is not that the product is complete. It is that it is ready for the people who will tell us what to build next. If you are running identity for a team that is growing quickly, we would like to hear what you find.