Projects
Manage your applications and their settings.
Overview
A project represents a single application in Nadi. Each project has:
- Unique application key
- Environment configuration
- Alert rules
- Team access settings
Creating Projects
New Project
- Go to Settings → Projects
- Click New Project
- Enter project name
- Select platform (Laravel, PHP, JavaScript, etc.)
- Click Create
Project Details
After creation:
- Copy your Application Key
- Note the API endpoint
- Configure your SDK
Project Settings
General
| Setting | Description |
|---|---|
| Name | Display name in dashboard |
| Platform | Technology stack |
| Default Environment | Environment for filtering |
Environments
Define environments:
production - Live application
staging - Pre-release testing
development - Local developmentAdd custom environments:
- Go to project settings
- Click Environments
- Add environment name
Data Retention
Configure how long data is stored:
| Tier | Retention |
|---|---|
| Free | 7 days |
| Pro | 30 days |
| Team | 90 days |
| Enterprise | Custom |
Rate Limits
View and configure rate limits:
- Events per minute
- Events per day
- Burst allowance
Project Keys
Application Key
Used by SDKs to identify the project:
NADI_APP_KEY=nadi_app_xxxxxxxxxxxxxRegenerating Keys
If a key is compromised:
- Go to project settings
- Click Regenerate App Key
- Update all SDK configurations
- Old key is immediately invalidated
DANGER
Regenerating invalidates the old key immediately. Update all deployments before regenerating.
Multiple Projects
When to Use Multiple Projects
| Scenario | Recommendation |
|---|---|
| Same app, different environments | One project |
| Different apps, same repo | Separate projects |
| Microservices | Separate projects |
| Frontend + Backend | Separate projects |
Project Organization
Naming conventions:
my-app-frontendmy-app-backendmy-app-worker
Or by team:
team-a-serviceteam-b-service
Project Access
Team Access
By default, all team members can access all projects.
Restricted Access
Limit who can access:
- Go to project settings
- Click Access Control
- Select specific members
- Set their permission level
Project Transfer
Between Organizations
To transfer a project:
- Go to project settings
- Click Transfer Project
- Enter destination organization
- Confirm transfer
Requirements:
- You must be owner of both orgs
- Or have admin in destination
Archiving Projects
Archive
For inactive projects:
- Go to project settings
- Click Archive
- Confirm
Archived projects:
- Stop accepting events
- Data is retained
- Can be restored
Restore
- Go to Settings → Archived Projects
- Click Restore
Delete
Permanently delete:
- Archive the project first
- Go to archived projects
- Click Delete Permanently
- Confirm deletion
DANGER
Deletion is permanent. All data will be lost.
Project Statistics
View project metrics:
- Total events (lifetime)
- Events this month
- Storage used
- Active users
Next Steps
- API Keys - Manage credentials
- Team Management - Manage team members