In modern cloud-native environments, platform engineering teams face a persistent challenge: how do you enable multiple teams to collaborate on infrastructure designs, share best practices, and maintain consistency across diverse deployment environments—all while preserving team autonomy and security boundaries?

Enter Meshery Workspaces: a powerful organizational construct designed to facilitate exactly this kind of cross-team collaboration. Workspaces provide isolated, multi-tenant environments where teams can design, test, and share cloud-native infrastructure patterns without stepping on each other’s toes.

What Are Meshery Workspaces?

At their core, Workspaces are logical boundaries within Meshery that allow you to organize your infrastructure designs, deployments, and environments. Think of them as collaborative project spaces where:

  • Teams maintain separate environments for development, staging, and production
  • Designs and configurations are scoped to specific organizational units or projects
  • Access controls ensure that only authorized team members can view or modify resources
  • Shared catalog items can be imported and customized without affecting the source

Each Workspace operates as an independent namespace, complete with its own set of:

  • Designs: Visual topology configurations for your infrastructure
  • Environments: Kubernetes clusters and cloud provider connections
  • Credentials: Securely stored access tokens and keys
  • Team members: Role-based access control for collaborators

Why Platform Engineers Love Workspaces

Platform engineering is fundamentally about creating self-service capabilities that empower development teams while maintaining organizational standards. Workspaces excel at this by providing:

1. Isolation with Collaboration

Workspaces give each team their own sandbox to experiment and iterate, while still allowing platform engineers to share golden paths and reference architectures across the organization.

Organization
├── Platform Team Workspace
│   ├── Reference architectures
│   ├── Approved patterns
│   └── Baseline configurations
├── Backend Team Workspace
│   ├── Microservices infrastructure
│   └── API gateway configurations
└── Data Team Workspace
    ├── Data pipeline designs
    └── Analytics infrastructure

2. Design Reusability

Rather than reinventing the wheel, teams can clone proven designs from Meshery’s public Catalog or from other internal Workspaces. This accelerates development while ensuring consistency with organizational standards.

3. Environment Management

Platform engineers can configure multiple Kubernetes clusters and cloud environments within a Workspace, making it trivial to promote designs from dev to staging to production with confidence.

4. Audit and Compliance

Every action within a Workspace is tracked, providing clear visibility into who made what changes and when. This audit trail is invaluable for compliance and troubleshooting.

Real-World Example: Multi-Team Microservices Platform

Let’s walk through a practical scenario. Imagine you’re a platform engineer at a company building a microservices platform. You have:

  • A Platform Team maintaining infrastructure standards
  • Multiple application teams deploying microservices
  • A security team enforcing policies

Here’s how you’d leverage Workspaces:

Step 1: Create the Golden Path Workspace

The Platform Team creates a Workspace containing reference architectures:

  • Service mesh baseline (Istio with mTLS enabled)
  • Observability stack (Prometheus, Grafana, Jaeger)
  • Ingress patterns with rate limiting
  • Database operator configurations

These designs are marked as “approved” and published to your organization’s internal catalog section.

Step 2: Application Teams Clone and Customize

The Backend Team needs to deploy a new microservice. Instead of starting from scratch:

  1. They navigate to the Meshery Catalog
  2. Find the “Service Mesh Baseline” design from the Platform Team’s published patterns
  3. Click “Clone to Workspace”
  4. The design appears in their Workspace, ready for customization

Now they can:

  • Adjust resource limits for their specific workload
  • Add application-specific sidecars
  • Configure custom routing rules
  • Deploy to their dev environment for testing

Step 3: Iterate with Confidence

As the Backend Team refines their design:

  • Changes are isolated to their Workspace
  • They can validate configurations against Kubernetes and OPA policies
  • The visual designer shows real-time topology updates
  • Once tested, they promote to staging and production environments

Step 4: Share Back to the Organization

After proving their pattern works, the Backend Team can publish their customized design back to the internal catalog with a description like “High-Throughput API Service Pattern.” Now other teams benefit from their learnings.

Workspace Features That Drive Adoption

Visual Design Collaboration

Meshery’s visual designer is Workspace-aware, meaning multiple team members can collaborate on the same infrastructure design in real-time, similar to Figma for infrastructure-as-code.

Environment Promotion

Workspaces support multi-environment workflows, allowing you to:

  • Test designs in a sandbox cluster
  • Validate in staging with production-like data
  • Deploy to production with a single click (with appropriate RBAC checks)

Team Management

Fine-grained role-based access control ensures:

  • Owners can manage Workspace settings and membership
  • Editors can modify designs and environments
  • Viewers can browse designs without making changes

Integration with GitOps

Workspaces integrate seamlessly with GitOps workflows:

  • Export designs as Kubernetes manifests or Helm charts
  • Commit to your Git repository
  • Let your CI/CD pipeline apply changes
  • Meshery tracks drift between desired and actual state

Try It Yourself: Clone a Design from the Catalog

Ready to experience the power of Workspaces? Here’s a hands-on challenge:

  1. Sign up for Meshery Cloud (free tier available) or install Meshery locally
  2. Navigate to the Catalog at meshery.io/catalog
  3. Find a design that interests you, such as:
  4. Click “Clone to Workspace” - this imports the design into your personal Workspace
  5. Open the Visual Designer and explore the topology:
    • See how components are connected
    • Adjust configurations to match your environment
    • Add or remove resources as needed
  6. Connect your Kubernetes cluster (if you haven’t already)
  7. Deploy the design to your environment with a single click
  8. Monitor the deployment through Meshery’s built-in observability features

Within minutes, you’ll have a production-ready infrastructure pattern running in your cluster, customized to your needs. That’s the power of Workspaces and the Catalog working together.

Best Practices for Workspace Organization

Based on patterns we’ve seen from successful platform engineering teams:

Structure by Team and Environment

├── platform-team-workspace
│   ├── Environment: prod-cluster
│   ├── Environment: staging-cluster
│   └── Designs: Reference architectures
├── backend-team-dev-workspace
│   ├── Environment: dev-cluster-1
│   └── Designs: Experimental features
└── backend-team-prod-workspace
    ├── Environment: prod-cluster
    └── Designs: Production deployments

Establish Naming Conventions

  • Workspaces: <team>-<environment>-workspace
  • Designs: <service>-<version>-<purpose>
  • Environments: <cluster-name>-<region>

Implement a Promotion Workflow

  1. Develop and test in team dev Workspace
  2. Promote stable designs to team staging Workspace
  3. After validation, promote to team prod Workspace
  4. Share successful patterns to organization-wide Workspace

Leverage Teams and RBAC

  • Create Teams that span multiple Workspaces
  • Grant minimum necessary permissions
  • Use Viewer role for cross-team visibility
  • Reserve Owner role for platform engineers

The Future of Collaborative Infrastructure

Meshery Workspaces represent a fundamental shift in how platform engineering teams approach infrastructure management. By combining:

  • Visual design tools that make complex topologies understandable
  • Collaborative features that break down silos
  • Reusable patterns through the Catalog
  • Strong isolation with flexible sharing

Workspaces empower organizations to move faster without sacrificing control. They enable the kind of self-service infrastructure that development teams crave, while giving platform engineers the governance capabilities they need.

Get Started Today

Whether you’re managing infrastructure for a small startup or orchestrating deployments across a large enterprise, Meshery Workspaces can transform how your teams collaborate.

Start your journey:

Join the community:

Clone a design, customize it in your Workspace, and deploy it to your cluster today. Experience firsthand how Workspaces can accelerate your platform engineering efforts while maintaining the control and visibility your organization demands.

Have questions about Workspaces or want to share your use case? Join us in the Meshery community - we’d love to hear from you!