# Deck Auth: The login layer for every site

> Your users connect their accounts once. Deck keeps credentials in an encrypted vault, handles sign-in and MFA, and tells you when a login stops working.

Source: https://deck.co/auth

Authentication

Your users connect their accounts. Deck stores the credentials, manages sign in, prompts for MFA, and runs tasks.

[Get Started](https://console.deck.co/)

[Talk to Sales](https://deck.co/contact)

## Your app never touches a password

Passwords are encrypted and tokenized in the Deck Credential Vault. Your product only ever holds a credential ID, so passwords never end up in your database, your logs, or a support ticket.

*Diagram: a user signs in with their User ID, password and MFA code. The credentials go into the Deck Credential Vault, where they are encrypted and tokenized. Your app gets back a credential ID.*

### Tokenized on submit

Plaintext credentials never reach your systems.

### Independently audited

SOC 2 Type II and PCI DSS.

### Keep it or delete it

Store credentials for future task runs, or delete them as soon as the task finishes.

## Advanced auth, handled.

When a site sends a text code or asks a security question, Deck pauses the task and asks your user for the answer. They enter it in your product, and the agent continues from the same screen.

[Learn about interactions](https://docs.deck.co/guides/interactions)

## Logins that don’t get flagged

Plenty of portals block automated traffic on sight, and that’s usually where automation falls apart. Stealth Mode runs every session in a full browser with a consistent fingerprint and human pacing, so your users’ logins look like what they are: a person signing in to their own account.

[Learn about Stealth Mode](https://docs.deck.co/platform/stealth-mode)

## When a login breaks, you’ll know.

Credentials go stale for ordinary reasons. Someone changes their password, or an account gets locked after a few bad attempts. When a saved login stops working, Deck marks it invalid and lets you know, so you can ask your user to reconnect before their next task.

[Learn about credentials](https://docs.deck.co/concepts/credentials)

## Drop-in UI or your own design

### Auth Component

The Auth Component is the fastest way to get started. Drop it into your product, add your logo, colors, and copy, and your users can connect accounts the same day.

[View Auth Component](https://docs.deck.co/components/auth)

### Custom UI

Design your own screens and copy, and your team wires them up to Deck. The Vault, MFA handling, and credential checks work the same way underneath, so you don’t give anything up by going custom.

[View the auth flow guide](https://docs.deck.co/guides/building-auth-ui)

## If your users can log in to it, Deck can too.

Start building or talk to us about scale.

[Get Started](https://console.deck.co/) · [Talk to Sales](https://deck.co/contact)

## More from Deck

- [Deck home](https://deck.co/)
- [Browser Agents](https://deck.co/agents)
- [Tasks & Automation](https://deck.co/tasks-and-automation)
- [Observability](https://deck.co/observability)
- [Pricing](https://deck.co/pricing)
- [Security](https://deck.co/security)
- [Customers](https://deck.co/customers)

Docs: https://docs.deck.co · Site index for agents: https://deck.co/llms.txt