Skip to main content
GitHub

Projects

Create and manage projects.

Projects are the primary unit of organization in Risicare.

What is a Project?

A project represents a single application or service:

  • Separate data: Each project has isolated traces, sessions, fixes
  • Separate keys: Each API key is scoped to exactly one project — this is how the gateway knows where your traces belong
  • Separate settings: Configuration per project

API Key = Project Identity

When you use an API key in the SDK, the gateway automatically resolves the project from the key. No separate project_id is needed in your code — just set RISICARE_API_KEY and you're done.

Creating a Project

Via Dashboard

Only owners and admins can create a project, and creating one needs a sign-in from the last 15 minutes. The dialog does not say why a creation was refused: if Create Project does nothing, sign out, sign in again and retry. If it still does nothing, your role cannot create projects.

  1. Click the project dropdown in the top navigation bar
  2. Select New Project
  3. Enter a project name (e.g., "Production Agents")
  4. Click "Create Project"

A default API key is automatically generated and displayed with a quickstart code snippet. Copy it immediately — the full key is only shown once.

One step to start tracing

When you create a project, you get an API key instantly. No separate key creation step is needed — just paste the key into your SDK configuration and start sending traces.

When to Create Multiple Projects

Create a separate project for each:

  • Application — e.g., "Customer Support Bot", "Research Agent", "Code Reviewer"
  • Team — e.g., "ML Team Agents", "Platform Team Agents"
  • Strict access isolation — when different teams should not see each other's traces
Organization: Acme Corp
├── Project: support-bot       (customer support agent)
├── Project: research-agent    (research assistant)
└── Project: code-reviewer     (code review agent)

Projects vs Environments

You have two options for separating production, staging, and development data:

ApproachWhen to use
Single project + environment paramShared config, same team, want to compare across envs
Separate projects per envStrict access control, different teams per env

For most teams, a single project with the SDK's environment parameter is simpler:

import risicare
 
risicare.init(
    api_key="rsk-...",
    environment="production",  # or "staging", "development"
)

The dashboard filters by environment within a project. All configuration (fix templates, alert rules, evaluators) is shared automatically.

Project Settings

Risicare Settings page showing API keys, project configuration, and data management options

During the beta you can change only the project's name, on the dashboard's Settings page. You cannot change the settings in this table yourself.

SettingDescriptionDefault
trace_content_enabledWhether prompt and completion text is stored for this project. When false, the gateway replaces it with a placeholder at ingest, before anything is stored. The SDK also captures content only when you turn it on (trace_content=True), so both must be ontrue
retention_daysRead-only. Live retention is a fixed ClickHouse TTL that varies by data type (90 days for traces, spans, sessions and prompt/completion content; 365 days for evaluations and scorer results) — see Data Retention.90 (enforced)
rate_limit_requestsRequests allowed per window, per API key. Nothing enforces this value today100
rate_limit_window_secondsRate limit window, in seconds60
auto_diagnosis_enabledRead-only. Consent gate for automatic diagnosis, which sends error context to a third-party LLM subprocessor. It cannot be changed, and automatic diagnosis is also held for the beta — see Diagnosisfalse
auto_fix_enabledReserved for the fix-deployment feature, which is not enabled — currently inert. It has no effect; no fix is ever auto-deployed todayfalse
min_samples_for_deployReserved for the fix-deployment feature, which is not enabled — currently inert. Not read by any runtime100

PII and credential redaction is not a setting: it runs on every span and cannot be turned off.

Deleting a Project

Contact Support

Project deletion is not yet available in the dashboard. Contact support@risicare.ai to request project deletion. Deleted data cannot be recovered.

Next Steps