Concepts

This section defines the core nouns of the AISafe platform and the relationships between them. These concepts map to the dashboard, the API, and your continuous security workflows.

The object model at a glance

Organization
├── Members (owner / admin / manager / member)
├── Teams
├── Integrations (GitHub, GitLab, Slack, Linear, Jira)
├── Projects
│   ├── Source (repo or archive series)
│   ├── PR Review
│   ├── Scheduled Scans
│   └── Monitoring
├── Assessments
│   ├── Findings
│   ├── Reports
│   └── Artifacts
└── Credits & Billing

An Organization is your tenant. It contains Members in Teams, plus Integrations with external services. Within an organization, you create Projects (continuous security entities tied to a repo or target) and Assessments (individual scan runs). Each assessment produces Findings (vulnerabilities with evidence and severity) and Reports (PDF deliverables). Credits are the consumption unit that funds assessment runs.

A Project can own assessments. A project-bound assessment loads context from the project's living knowledge base for faster, more accurate runs, and the project can enable continuous capabilities like PR review, scheduled scans, and monitoring. Standalone assessments (not bound to a project) retain their existing behavior.

Concept pages

OrganizationAn Organization is the top-level tenant in AISafe. Assessments, findings, reports, integrations, team members, and billing all live inside an organization. You create your first organization on sign-up. You can belong to multiple organizations if you work across teams or companies.

ProjectA Project is a continuous security entity within an organization. While an Assessment is a single scan run, a Project represents an ongoing relationship with a specific codebase or target. It owns a source (repository or archive series), can enable PR review, scheduled scans, and monitoring, and maintains a living knowledge base that makes each subsequent assessment faster and more accurate.

AssessmentAn Assessment is one run of AISafe against one target: a codebase, a URL, or both. It is the central work unit of the platform. Findings, reports, artifacts, and triage all belong to one assessment. You create an assessment by clicking "Start assessment" in the dashboard or calling POST /api/v1/assessments via the API.

FindingA Finding is one vulnerability or observation that an Assessment produces. It is the unit of remediation. Each finding carries evidence, a severity, a lifecycle status, and a suggested fix. You triage findings, export them to your issue tracker, and track them to closure.

ReportA Report is a PDF deliverable from a completed Assessment. Each report presents the assessment's findings, evidence, and remediation recommendations as a shareable document suitable for stakeholders, compliance packages, and executive review.

Credits & billingAISafe uses a credit-based consumption model. Credits are the currency that funds assessment runs, report generation, and continuous capabilities like PR review and monitoring. You purchase credits upfront or subscribe to a plan that includes a monthly credit allowance.