Yekar.AI
Login

Protect the workspace

Protect the keys to the workspace

Store the credentials people sign in with so that a copy of the database does not become a set of working logins.

Get startedRead the docs
Captured from the product Demo workspace
Hash passwords with Argon2id and refuse breached ones, expire and scope every API key, and seal each surface separately.

What this changes for your team.

Passwords are hashed with Argon2id and are never recoverable from storage, and a new password found in a known data breach is refused - only the first five characters of a one-way fingerprint are sent for that check, so the password itself never leaves Yekar.AI. An API key is random material shown once at creation; only its hash is kept, with a short hint so keys stay tellable apart in a list, and every key expires and opens only the scopes its owner chose. Each surface seals its own sessions, so a compromise of one cannot mint a session for another, and a surface whose secret is unset refuses sign-in instead of falling back to a shared one.

How it works in practice.

  1. 01

    Check a new password against known breaches and hash it with Argon2id on the server before it is ever stored.

  2. 02

    Show a newly created API key once with its expiry and scopes, then keep only its hash and a short identifying hint.

  3. 03

    Seal product, staff and partner sessions with separate secrets that cannot substitute for one another.

What you can plan around.

What to expect, including limits that matter to your team.

Stored password material is an Argon2id hash, not an encrypted or encoded original.

An existing API key cannot be redisplayed because only its hash is retained; a key expires after at most a year and is rotated in place to keep a system running.

Ten failed sign-ins for one address within fifteen minutes lock it for the rest of the window, even for the right password.

Yekar.AI's own staff sign in to internal tools through federated sign-in for existing accounts only, with no self-service path.

Complete the operating path

View all capabilities
Protect the workspaceAdd a second step to sign-in, and see where you are signed in

Keep a leaked password from being enough, and keep a forgotten browser from staying signed in.

Protect the workspaceContain where a tool can send data

Limit each integration to the destinations it declares, so a compromised tool has nowhere to send your data.

Make actions accountableMake every external action accountable

Make every integration call act as a deliberate team, user, platform, or customer identity.

Bring one real process

See how Yekar.AI fits the way you work.

Start with a job your team already owns, plus the tools and decisions around it.

Get started