Skip to content
RT Softs

Sanctum vs Passport vs Breeze: choosing Laravel auth in 2026

Most Laravel apps need Sanctum and nothing else. Passport is for full OAuth servers; Breeze and Jetstream are starter kits, not auth strategies.

A Admin
April 29, 2026 2 min read Updated Nov 19, 2026

Sanctum handles API tokens and first-party SPA sessions with almost no configuration. Passport implements a complete OAuth2 server. Most teams reach for Passport because a tutorial said so, then spend a week on grant types they never use.

Sanctum: the default choice

Use Sanctum for a mobile app, a first-party SPA on the same domain, or simple API tokens for integrations. Tokens are hashed in the database, scoped by abilities, and revocable individually. It is a small package that does one job.

Passport: when you are the identity provider

Choose Passport when third parties need to obtain tokens on behalf of your users — an OAuth2 authorisation server with clients, scopes and refresh tokens. If nobody outside your organisation is registering an app, you probably do not need it.

Breeze and Jetstream are scaffolds

Breeze gives you login, registration, password reset and email verification in Blade, Livewire, Vue or React. Jetstream adds teams, API tokens and profile management on top of Livewire or Inertia. Neither is a replacement for Sanctum or Passport; they wire the UI and the session.

What we ship on client projects

Breeze (Blade or Inertia) for the authenticated UI, Sanctum for API tokens, and a role/permission layer of our own. Passport appears only when a client integrates with a partner who genuinely needs OAuth2.

Frequently asked questions

Can Sanctum and Passport be installed together?

They can coexist but the middleware and guards get confusing. Pick one and document which routes use which guard.

Do Sanctum tokens expire?

Not by default. Set an expiration in config/sanctum.php or revoke tokens on logout, especially for mobile clients that may lose the token.

Which is better for a React SPA?

Sanctum, on the same top-level domain, using cookie-based SPA authentication. Cross-domain SPAs need token authentication instead, which is more work to secure.

More on this topic: Laravel articles.

A

Admin

Related articles