Skip to content

Managing Your RunForge Projects

What You'll Learn

How to organize your AI applications into projects, manage multiple projects effectively, and keep your monitoring clean and organized.

Why Use Multiple Projects?

Separate Your Applications

Think of projects like folders for different parts of your AI work: - Production Chatbot - Your live customer service system - Development Testing - Experiments and new features - Content Generation - Blog writing and marketing content - Code Assistant - Programming help and automation

Benefits of Project Organization

  • Clear cost tracking - See exactly what each application costs
  • Isolated metrics - Don't mix development and production data
  • Team collaboration - Share specific projects with team members
  • Better budgeting - Set cost limits per project

Creating a New Project

Step-by-Step Creation

  1. Navigate to Settings
  2. Click Settings in the top navigation

  3. Select Projects from the sidebar

  4. Start New Project

  5. Click the Create New Project button

  6. You'll see a form to fill out

  7. Fill Out Project Details

  8. Project Name: Choose something descriptive

    • ✅ Good: "Customer Support Chatbot"
    • ✅ Good: "Blog Content Generator"
    • ❌ Avoid: "Project 1" or "Test"

  9. Description: Brief explanation of the project's purpose

    • Example: "Production chatbot handling customer inquiries on our website"

  10. Environment (if available):

    • Production, Development, Staging, Testing

  11. Review and Create

  12. Double-check your information
  13. Click Create Project

Project Naming Best Practices

Include the purpose: - "Marketing Email Generator" - "Customer FAQ Bot" - "Product Description Writer"

Include the environment: - "Chatbot - Production" - "Chatbot - Development" - "Content AI - Staging"

Managing Multiple Projects

Project Dashboard

Your projects overview shows: - Project name and description - Recent activity and usage statistics - Cost summary for each project - Quick access to project-specific dashboards

Switching Between Projects

  1. Project Selector: Look for a dropdown in the top navigation
  2. Click to expand: Shows all your projects
  3. Select project: Click the one you want to view
  4. Dashboard updates: Shows data only for that project

Project-Specific Views

When you select a project, everything changes to show only that project's data: - Dashboard metrics - Usage charts - Cost breakdowns - API key settings - Alert configurations

Project Settings Management

Accessing Project Settings

  1. Select your project from the project dropdown
  2. Go to Settings → Projects
  3. Click Edit next to the project you want to modify

Key Settings to Configure

Project Information

  • Name: Update as your project evolves
  • Description: Keep it current with your project's purpose
  • Tags (if available): Help categorize and search projects

Access Control

  • Team members: Who can view this project's data
  • Permissions: View-only or full access for each member
  • API access: Control which applications can send data

Data Retention

  • History length: How long to keep detailed logs
  • Archive settings: What happens to old data
  • Export options: How to back up your data

API Keys Per Project

Why Separate API Keys?

Each project should have its own set of API keys: - Security: Compromised keys only affect one project - Tracking: Clear attribution of costs and usage - Management: Easier to rotate and manage keys

Setting Up Project API Keys

  1. Select your project from the dropdown
  2. Go to Settings → API Keys
  3. Add provider keys (OpenAI, OpenRouter, etc.)
  4. Configure RunForge ingest key for this project

Key Management Best Practices

  • Use descriptive names: "Production OpenAI Key" vs "Key 1"
  • Regular rotation: Change keys every 3-6 months
  • Monitor usage: Watch for unexpected activity
  • Secure storage: Never put keys directly in code

Project Collaboration

Adding Team Members

  1. Project Settings → Team
  2. Invite by email: Add team member's email address
  3. Set permissions:
  4. Viewer: Can see dashboards and data
  5. Editor: Can modify settings and keys
  6. Admin: Full control including team management

Permission Levels Explained

Viewer Access: - View dashboards and metrics - See cost and usage data - Download reports - Cannot modify settings

Editor Access: - Everything viewers can do - Add/edit API keys - Modify project settings - Create alerts and notifications - Cannot manage team access

Admin Access: - Everything editors can do - Manage team members - Delete project data - Change project permissions

Cost Management Per Project

Setting Budget Limits

  1. Project Settings → Budget
  2. Set monthly limit: How much you want to spend
  3. Configure alerts: Get notified at 50%, 80%, 100% of budget
  4. Set actions: Pause tracking, send notifications, etc.

Cost Allocation

  • Track costs separately for each project
  • Generate per-project reports for accounting
  • Monitor budget burn rate to predict monthly costs
  • Compare costs across similar projects

Project Lifecycle Management

Development to Production

During Development: - Create separate "Dev" project - Use lower-cost models for testing - Experiment freely without affecting production metrics

Moving to Production: - Create new "Production" project - Copy settings from development project - Use production API keys - Set up monitoring and alerts

Archiving Old Projects

When projects are no longer active: 1. Export important data before archiving 2. Remove API keys to prevent accidental usage 3. Archive the project to clean up your project list 4. Keep data for compliance if required by your organization

Common Project Structures

By Application Type

📁 Customer Service Bot - Prod
📁 Customer Service Bot - Dev
📁 Content Generator - Prod
📁 Content Generator - Dev
📁 Code Assistant

By Department/Team

📁 Marketing Team - Content AI
📁 Support Team - Chatbot
📁 Engineering Team - Code AI
📁 Research Team - Analysis AI

By Environment

📁 Production Systems
📁 Staging Environment  
📁 Development Testing
📁 Personal Experiments

Troubleshooting Project Issues

Project Not Showing Data

Check these things: - Is the correct project selected in the dropdown? - Are your applications using the right project ID? - Did you configure the ingest API key correctly? - Are you looking at the right time period?

Cannot Access Project

Possible issues: - You might not have permission to view this project - The project might be archived - You might be signed into the wrong organization - Contact your project admin for access

Data in Wrong Project

If data appears in the wrong project: - Check your SDK configuration for projectId - Verify you're using the correct ingest API key - Data cannot be moved between projects after ingestion

Best Practices Summary

Project Organization

  • Use clear, descriptive names
  • Separate environments (dev, staging, production)
  • Group by application or team as makes sense
  • Keep similar projects together

Security and Access

  • Limit access to only necessary team members
  • Use appropriate permission levels
  • Regularly review who has access to what
  • Rotate API keys regularly

Cost Management

  • Set budgets for each project
  • Monitor regularly for unexpected costs
  • Compare similar projects to identify optimization opportunities
  • Archive unused projects to keep things clean

Next Steps