Product FAQ
Product questions, answered.
Core modules, identity model, and rollout basics.
What is Lamba built for?
Lamba provides tenant-aware authentication, authorization, and governance so teams can ship identity without rebuilding the core infrastructure.
How do tenants and projects map to environments?
Tenants represent customer orgs. Projects separate sandbox and production or product lines, each with its own keys, domains, and usage.
Which login methods are supported?
Password, magic link, social login, SMS OTP, and OIDC/SSO-ready flows depending on plan.
How do campaigns, loyalty, and webhooks connect?
Every module runs on the same tenant + project context, so messaging, rewards, audit trails, and events stay consistent with identity data.
Pricing FAQ
Pricing questions, answered.
Usage rules, limits, and plan changes in one place.
How do upgrades and downgrades work?
Upgrades apply immediately so you can unlock higher limits right away. Downgrades take effect on the next billing cycle, and we keep your data intact.
What happens on Free when we hit a limit?
Free has hard caps in production and returns 402 PLAN_LIMIT_EXCEEDED with clear guidance. You can upgrade to keep usage flowing.
How do sandbox and production environments work?
Paid plans include separate sandbox and production projects; sandbox traffic is not billable. The Free plan includes production only.
How does overage billing work?
On paid plans, MAU and campaign email usage can exceed the included amount and bill at the published plan rates at the end of the cycle. We surface usage early so you can avoid surprises.
How do you define MAU?
MAU is the count of unique users or devices with a successful session in a rolling 30-day window.
How long does launch pricing last?
Launch offer pricing is locked through 2026.
Security FAQ
Security questions, answered.
High-level guidance for security and compliance reviews.
How long is data retained?
Retention windows vary by plan and data type. We keep operational logs long enough to support audits and troubleshooting, and we will confirm exact windows during onboarding.
How do you handle incident response?
We follow documented incident response workflows with clear internal escalation and customer communication practices.
How do you separate environments?
We recommend distinct projects for sandbox and production. Paid plans include multiple projects to keep environments isolated.
How are webhooks secured?
Webhook payloads are signed and include timestamps for replay protection. Delivery logs are available for verification.
How do rate limits work?
Rate limits are designed to protect shared infrastructure. You will see usage visibility before limits are reached and can move to higher tiers as needed.