Tulip Logo IconTulip
Dependencies

Better Auth

Better Auth is the authentication engine Tulip uses for sessions, plugins, and permission-aware app flows.

Better Auth is the authentication engine used by Tulip auth conventions.

Tulip keeps Better Auth visible. Apps configure Better Auth directly, choose plugins directly, and own the database schema and migrations.

Where Tulip uses Better Auth

  • @tulip-systems/auth exposes client context helpers and permission types.
  • @tulip-systems/auth/next/server exposes Next.js server helpers.
  • App templates configure Better Auth with Drizzle and plugins.
  • Commands, Data Tables, Inline, App sidebar, and admin layouts can consume permissions.

What Tulip adds

Tulip adds auth-aware React providers, permission helpers, shared field conventions, Next.js guard helpers, and app-shell integration.

Tulip does not hide Better Auth's plugin system or infer your whole access-control model for you.

What your app owns

  • Better Auth instance
  • plugins
  • roles and access control
  • auth schema and migrations
  • email delivery and provider configuration

Continue reading

ORPC

ORPC is the typed RPC layer Tulip apps use for app-local routers, procedures, and client calls.

TanStack Query

TanStack Query is the server-state cache and mutation layer used across Tulip data flows.

On this page

Where Tulip uses Better AuthWhat Tulip addsWhat your app ownsContinue reading