Skip to main content

​
Multiple Workspaces

A single Hubify account can run multiple workspaces, each at its own subdomain with its own template, agent personality, skills, memory, and integrations. Every workspace is fully isolated — its own Fly.io machine, its own persistent volume, its own Convex hub. Use multiple workspaces to separate concerns: one for personal productivity, one for development, one per client, or any combination that fits your workflow.

​
Why Multiple Workspaces

  • Separation of concerns. Your personal OS does not need to see your client’s data. Your dev workflow does not need your GTM integrations.
  • Client isolation. Agencies can spin up a dedicated workspace per client with its own credentials, memory, and agent personality.
  • Different agent personalities. Your personal assistant (MyOS) behaves differently from your coding agent (Dev OS) which behaves differently from your GTM agent (Founder OS). Each workspace has its own SOUL.md.
  • Template specialization. Each workspace can run a different template optimized for its use case.

​
Plan Limits

PlanMax Workspaces
Free1
Pro3
Team10
AgencyUnlimited
Each workspace runs on its own dedicated Fly.io machine. Workspace limits are tied to your plan tier. Upgrading your plan increases the number of workspaces you can run simultaneously.

​
Creating and Managing Workspaces

​
Creating a New Workspace

# Interactive workspace creation — prompts for name and template
hubify workspace create
The creation flow prompts you to:
  1. Choose a subdomain (e.g., research for research.hubify.com)
  2. Select a template (MyOS, Dev OS, Founder OS, Research OS, Client OS, Minimal)
  3. Confirm and deploy

​
Listing Your Workspaces

# Show all workspaces on your account
hubify workspace list
Example output: 
Workspaces (3/3 Pro tier)

  houston.hubify.com    MyOS         active    last active: 2m ago
  bamf.hubify.com       Founder OS   active    last active: 15m ago
  research.hubify.com   Research OS  sleeping  last active: 3d ago

​
Opening a Workspace

# Open a workspace dashboard in your browser
hubify workspace open bamf

​
Switching Between Workspaces in CLI

When you run hubify connect, the CLI connects to the workspace defined in the HUB.yaml in your current directory. To switch workspaces, navigate to the directory containing that workspace’s HUB.yaml, or specify the workspace explicitly: 
# Connect to a specific workspace
hubify connect --workspace bamf
Workspace creation and listing work via both CLI and web UI. A visual workspace switcher for quick navigation between workspaces in the dashboard is being built.

​
Workspace Isolation

Each workspace is fully isolated from every other workspace:
ComponentIsolation
ComputeSeparate Fly.io machine per workspace
StorageSeparate persistent volume per workspace
NetworkSeparate subdomain with independent HTTPS
DatabaseSeparate Convex hub per workspace
MemorySeparate memory store per workspace
SkillsIndependently installed per workspace
IntegrationsIndependently configured per workspace
By default, workspaces share nothing. You can opt into sharing specific resources (vault, intelligence) as described below.

​
Vault Sharing

The vault stores encrypted credentials (API keys, OAuth tokens, MCP configs). You can configure whether your vault is shared across all workspaces or isolated per workspace. 
# In HUB.yaml
privacy:
  vault_shared_across_workspaces: true   # All workspaces share one vault

# Or isolate per workspace
privacy:
  vault_shared_across_workspaces: false  # Each workspace has its own vault

​
When to Share the Vault

  • Share when multiple workspaces need the same credentials (e.g., GitHub token used by both Dev OS and Founder OS)
  • Isolate when workspaces belong to different clients or security domains (e.g., agency client workspaces should never share credentials)
For agency use cases, always set vault_shared_across_workspaces: false on client workspaces. Each client workspace should have its own isolated vault with only that client’s credentials.

​
Memory Sharing

Each workspace has its own memory store by default. Memory does not cross workspace boundaries unless you explicitly configure intelligence sharing.

​
Intelligence Levels

# In HUB.yaml
intelligence:
  global: opt-in    # Contribute anonymized learnings to the Singularity
  org: null          # No org-level sharing (or set org ID for org sharing)
LevelWhat Gets SharedWith Whom
isolatedNothingNo one
orgLearnings, knowledgeOther workspaces in the same organization
global (opt-in)Anonymized learnings onlyAll Hubify workspaces via the Singularity
Memory sharing refers to the intelligence layer (learnings, knowledge). Your episodic memory files (memory/YYYY-MM-DD.md), personal notes, and project files are never shared across workspaces regardless of intelligence level.

​
Multi-Workspace Strategies

​
Agency: One Workspace Per Client

The most common agency pattern. Each client gets their own isolated workspace with the Client OS template. 
bamf.hubify.com              Founder OS   (agency operations)
client-acme.hubify.com       Client OS    (ACME Corp account)
client-contoso.hubify.com    Client OS    (Contoso account)
client-initech.hubify.com    Client OS    (Initech account)
Configuration:
  • Each client workspace has vault_shared_across_workspaces: false (isolated credentials)
  • Each client workspace has intelligence: isolated (no cross-client data)
  • The agency workspace (bamf) may share vault with one or two workspaces for shared tools like GitHub

​
Founder + Dev: Workflow Separation

Run your GTM workflow and your coding workflow in separate workspaces with different templates, personalities, and skills. 
houston.hubify.com           MyOS         (personal OS, daily driver)
dev.hubify.com               Dev OS       (coding, PRs, deployments)
Configuration:
  • Shared vault (vault_shared_across_workspaces: true) so both workspaces can access GitHub
  • Separate memory (each workspace tracks its own context)
  • Different SOUL.md in each (personal assistant vs. coding agent)

​
Personal + Work: Context Boundaries

Keep personal and professional contexts completely separate. 
houston.hubify.com           MyOS         (personal: fitness, hobbies, life admin)
work.hubify.com              Founder OS   (work: GTM, clients, revenue)
Configuration:
  • Isolated vault (vault_shared_across_workspaces: false) for clear security boundaries
  • Isolated intelligence (personal learnings stay personal, work learnings stay at work)
  • Different integrations (personal has Strava; work has LinkedIn, CRM)

​
Research Multi-Domain

Run multiple research workspaces for different domains, each with their own knowledge base and agent specialization. 
ai-research.hubify.com       Research OS  (AI/ML papers and synthesis)
bio-research.hubify.com      Research OS  (biotech and longevity research)
market-research.hubify.com   Research OS  (market analysis and competitive intel)
Configuration:
  • Each workspace uses the same Research OS template but with different SOUL.md specializations
  • Shared vault for common tools (Perplexity, arXiv access)
  • Org-level intelligence sharing so research learnings cross-pollinate

​
Next Steps

Templates

Browse templates to pick different ones for each workspace

Customizing Templates

Customize each workspace after deployment

Guardrails & Safety

Configure safety settings per workspace

Workspace Isolation

How workspace-level security works