Projects & Quotas

Projects#

A project maps to one application or service. Each project has its own DSN, event count, and settings.

Create projects from Settings > Projects > New Project. Give each project a descriptive name that matches the service it represents: api-server, frontend, worker, etc.

DSN#

Each project has one or more Client Keys (DSNs). Find them under Settings > Client Keys for the project.

A DSN looks like:

https://your-key@your-hostname.tindra.sh/1

The number at the end is the project ID. You can create multiple keys per project and revoke them individually. Useful if a key leaks or you want to rotate credentials.

Event quotas#

Tindra does not enforce hard per-project quotas by default. All projects on a self-hosted instance share the same Postgres database.

For managed instances, quotas depend on your plan. Check your current usage from Settings > Usage in the dashboard.

Retention#

Events are retained for the number of days set in RETENTION_DAYS (default: 90). Older events are purged nightly. This applies globally. You cannot set different retention per project.

Deleting a project#

Go to Settings > Projects, open the project, and scroll to the danger zone. Deleting a project permanently removes all associated events, issues, and client keys. This cannot be undone.

Multiple environments in one project#

Most teams use one project per service and configure environment in the SDK to separate production from staging. There is no need to create separate projects for each environment.

SENTRY_ENVIRONMENT=production