Launch offer: 50% off.Paid plans only.See pricing
Skip to content
Lamba
Open menu
Get started
Product

Identity infrastructure that stays coherent from first tenant to global scale.

Track tenants, enforce policy, and keep identity state coherent from a single system map.

Start for freeCompare plans

Joining a project? Create a platform account to manage memberships across workspaces.

Feature atlas

Core modules, fully connected.

Campaigns, loyalty, audit, and webhooks stay tied to tenant and project context.

Engagement

Campaigns that keep tenant context.

Design segments, orchestrate journeys, and keep delivery governed by plan limits.

  • Segments combine auth, engagement, and tenant signals.
  • Email + SMS journeys ship with schedule windows.
  • Delivery metrics map to tenant and project scopes.

Templates and approvals stay versioned for every tenant.

Key signals

Segments
Journeys
Templates
Delivery rate
Core identity

Sessions

Session-aware tokens with refresh rotation.

  • Per-device sessions with rotating refresh tokens.
  • Access tokens carry session + environment context.
  • Membership changes invalidate stale tokens.

Authorization

Roles that follow tenant + project boundaries.

  • Tokens include tenant and project role claims.
  • Tenant admins act as project admins by default.
  • Owner uniqueness is enforced per tenant/project.

Authentication and authorization stay in the center.

The same identity core powers every tenant, so teams ship without forking auth logic by environment or product.

Security, product, and growth operate on one consistent contract instead of stitching separate systems together.

  • One policy surface for every tenant and project.
  • Consistent developer experience across clients.
  • Fewer integrations to maintain as you scale.
Social providers

One auth surface, broad provider coverage.

Launch with core global providers and expand into regional networks without changing your tenant model.

GoogleAppleFacebookGitHubMicrosoftXDiscordLinkedInSteamEpic GamesYandexXiaomiHuaweiWeChatQQ ConnectLINE LoginKakaoGoogleAppleFacebookGitHubMicrosoftXDiscordLinkedInSteamEpic GamesYandexXiaomiHuaweiWeChatQQ ConnectLINE LoginKakao
Tenant model

Tenants hold projects, projects hold identity context.

The tenant is the billing boundary; projects keep environments, teams, and policies scoped.

Tenants define the account boundary. Every project, domain, and plan decision inherits from that tenant context.

Projects are workspaces inside a tenant, keeping auth settings and usage scoped while roles stay consistent across the organization.

Tenant->Projects->Users & Sessions->Policies & Environments

Tenant boundary

Billing, add-ons, domains, and usage roll up to the tenant.

Project workspace

Environments and teams live per project, with scoped settings.

Roles + membership

Tokens carry tenant + project roles so authorization is consistent.