Workspaces

Organization-level cloud environments that house all your team's repositories and enable seamless collaboration across projects.

What is a Workspace?

A Workspace is a Cloudflare Container environment that serves as your team's central hub for agentic development. It provides isolated, secure compute resources where your repositories live and where team members can create projects and sandboxes.

Organization Scoped

Each workspace belongs to an organization and provides shared resources for all team members.

Containerized

Built on Cloudflare's container infrastructure for security, performance, and global availability.

Workspace Architecture

Your Organization Workspace

Repositories
Cloned & managed
Projects
Git worktrees
Sandboxes
Execution environments

Creating a Workspace

Prerequisites

  • • Active Rizome organization account
  • • Valid subscription plan (workspace provisioning requires billing)
  • • Organization admin permissions

API Method

POST /v1/workspaces
curl -X POST https://api.rizome.dev/v1/workspaces \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d {{
"name": "my-team-workspace",
"organization_id": "org_123456"
}

CLI Method

Rizome CLI
rizome workspace create my-team-workspace

Workspace Management

Provisioning

Workspaces are provisioned automatically when your organization subscribes. The provisioning process includes:

  • • Container resource allocation
  • • Network security configuration
  • • Storage volume mounting
  • • Access control setup
Provision workspace
POST /v1/workspaces/:id/provision

Repository Integration

Add repositories to your workspace for team collaboration:

Add repository
POST /v1/repositories
List repositories
GET /v1/repositories

Key Features

Git Worktree Management

Create isolated branches for each team member without conflicts. Perfect for AI-assisted development workflows.

Team Collaboration

Shared access to repositories, projects, and resources. Role-based permissions and audit logging included.

Elastic Scaling

Automatically scales based on team usage. Pay only for active compute time and storage used.

Best Practices

Workspace Organization

  • • Use one workspace per team/organization
  • • Group related repositories together
  • • Implement consistent naming conventions
  • • Set up automated backup policies

Security

  • • Enable two-factor authentication for all team members
  • • Regularly rotate API keys and access tokens
  • • Use least-privilege access controls
  • • Monitor workspace activity logs

Performance

  • • Clean up unused projects and sandboxes regularly
  • • Use appropriate instance types for your workloads
  • • Monitor resource usage and optimize accordingly
  • • Leverage caching for frequently accessed repositories

Next Steps

Learn About Projects

Understand how to create and manage git worktrees within your workspace for isolated development.

Read more

Explore Sandboxes

Learn how to create execution environments for your projects and connect AI coding assistants.

Read more

API Reference

Complete API documentation for workspace management endpoints.

View API Reference