Get started with the app
Create a secure workspace, understand the overview, and establish the minimum operating setup for your team.
Create or access an account
Sign in with Google, GitHub, or email and password. New password accounts require at least 12 characters. If a teammate invited you, open the invitation link and confirm the workspace before continuing.
Your first workspace
On first access, ALLM creates a workspace, a live project, and a default live API key. The full key is displayed once. Save it in a secret manager as ALLM_API_KEY; it cannot be recovered later.
Do not paste secrets into tickets or chat
If the onboarding key is lost or exposed, create a replacement in API keys, update the application, verify traffic on the new key, and revoke the old one.
Read the overview
- API calls this month
- Current usage against the workspace quota.
- Catalog release
- The immutable model-intelligence snapshot currently used for decisions.
- Catalog deployments
- The number of provider-specific deployments tracked globally.
- Active policies
- Stored selection rules owned by the workspace.
- Recent catalog changes
- The latest persisted model, deployment, pricing, or lifecycle changes.
Recommended baseline
- Create separate test and live projects.
- Use a different API key for each environment and workload.
- Enable security, billing, catalog-change, and webhook-failure notifications as appropriate.
- Add a webhook to your incident or catalog-governance service.
- Invite teammates with the smallest role that supports their job.
Security checklist
- Keep the one-time API key and webhook signing secret in a secret manager.
- Rotate credentials when ownership changes or exposure is suspected.
- Remove inactive members and revoke unused endpoints.
- Keep at least two workspace owners before changing owner access.
- Use test projects for experiments so live usage and credentials stay isolated.