Projects
Everything under Organization → Projects is project-scoped. You create a project first; then that project owns environments, ClickHouse Database Configs, connectors (data sources, memory, and scanners), and signal routing.
Organisation └── Project ← create this first ├── Environments ├── Database Configs (ClickHouse) ├── Connectors (data sources, memory, scanners) └── Signal routingWhen to create a project
Section titled “When to create a project”Create a project for:
- Separate teams that share the same organization
- Customer-specific deployments
- Workloads that should use different ClickHouse Database Configs
Use environments (production, staging, …) inside a project when you need multiple backend targets without splitting projects. See Environments.
Create a project
Section titled “Create a project”
Select Organization from the sidebar.
Use the projects list to see projects already available in the organization.
Click Create project, enter a project name, and submit.
Use the project selector in the top navigation to make the project active. Then pick an environment.
What a project contains
Section titled “What a project contains”| Resource | Description |
|---|---|
| Environments | Named partitions (production, staging, …) |
| Database Configs | ClickHouse app-store connections per environment |
| Connectors | Data-source (Tempo, Loki, Prometheus, Jaeger, ClickHouse), memory (Claude, Mem0, Zep), and scanner (Trustabl) |
| Signal bindings | Which connector serves traces / logs / metrics per environment |

Member access
Section titled “Member access”Project access controls which organization members can use a project. Existing organization members are assigned to existing projects during migration so current installations continue to work. New members can be invited to the organization first and then granted access to specific projects as needed.