Projects & Workloads

AVAILABLE

A Project is an isolated workspace within an Organization dedicated to a specific application, microservice, or AI initiative.

Rendering diagram...

Why Use Projects? #

Projects enforce strict resource and credential isolation between different workloads:

  • Credential Segregation: API Keys and Service Tokens created in Project A cannot access models or resources in Project B.
  • Customer Member Directory: End-user identities (external_user_id) and individual budgets are strictly scoped per project.
  • Portal User Assignment: Team members are granted access to specific projects through ProjectAccessAssignment.
  • Autonomous Agents: Agents, prompt templates, skills, and MCP tools are scoped to the project.
  • Budget Allocation: Assign specific monthly budgets to individual projects to prevent runaway costs from affecting other teams.

Project Structure #

Every Project contains:

  • Environments: Two-tier isolation stages (Test and Production).
  • Customer Members: Workload and end-user directory with individual spending limits.
  • Portal User Access: Assigned developers and operators via ProjectAccessAssignment.
  • Service Tokens: Machine-to-machine credentials scoped to the project and environment.
  • Routing Policies: Custom fallback cascades and latency/cost optimization rules.
  • Agent Ecosystem: Autonomous agents, tools, skills, and MCP server integrations.

Managing in the Developer Portal #

  1. Navigate to the Projects list at https://console.naagmani.com/projects.
  2. Click + Create Project to initialize a new workspace.
  3. Select any project to view its dedicated dashboard, members, service tokens, agents, and analytics.

Next Steps #