Lazers/Documentation/Authentication Architecture
Security & Privacy

Authentication Architecture

Server API Keys (laz_live_) vs Client DSNs (laz_ci_): two-tier credential separation and security rules.

Two-Tier Credential Model

1. Server API Key (`laz_live_...`) - **Prefix**: `laz_live_` - **Use Cases**: Backend microservices, cron jobs, background workers, and OpenTelemetry Collectors. - **Permissions**: Authorized to ingest server-side signals and OpenTelemetry logs/traces. - **Handling**: Must be stored securely in server environment variables or secret vaults (e.g. AWS Secrets Manager).

2. Client DSN (`laz_ci_...`) - **Format**: `https://laz_ci_<token>@api.lazers.app/<projectId>` - **Use Cases**: Flutter apps, React/Vue browser single-page apps, iOS/Android mobile clients. - **Permissions**: Strictly **write-only**. Cannot query incidents, cannot view operational history, and cannot modify project settings. - **Rate Limiting**: Enforces strict per-minute rate limits (configurable from 1 to 600 req/min) to prevent abuse.

Ready to test with your service?

Create a project, generate an API key or Client DSN, and send a signal in 2 minutes.