One workspace for every tenant. Zero operational sprawl.
MSPStudio gives managed service providers a structured operating surface — from onboarding through ongoing delivery — with tenant isolation, SLA tracking, and compliance-ready evidence built in. A 6-step setup wizard configures your AI provider, connects repositories, initializes code intelligence, assigns roles, and provisions your first tenant workspace.
MSPs lose visibility as they scale tenants.
Spreadsheets replace systems. Tickets get lost between inboxes. SLA breaches surface only when customers escalate. Every new tenant multiplies the operational debt.
No single pane of glass
Tenant state lives across email threads, shared drives, and tribal knowledge. Onboarding is ad-hoc; offboarding is incomplete.
SLA blindness
Response time commitments exist in contracts but aren’t tracked in tooling. Breaches are discovered reactively, not prevented proactively.
Audit exposure
When a tenant asks for service evidence, teams assemble reports manually. Proof of delivery should be a byproduct, not a project.
One tenant-aware workspace instead of three disconnected operational surfaces.
MSPStudio gives delivery teams one place to onboard, plan, publish, and govern tenant work without stitching together separate setup tools, planning boards, and admin portals.
Tenant-first operating model
Each customer gets a clear operational boundary for setup, role context, audit evidence, and delivery flow. That matters when service teams scale.
Guided handoff into Azure DevOps and Jira
The point is not another dashboard. The point is getting structured work into the systems teams already execute in, with less manual translation and less drift.
AI support where operators actually work
Code intelligence, story generation, and hierarchy planning live in the workspace itself instead of becoming another sidecar tool people forget to use.
Structured service delivery at scale.
Tenant isolation
Each customer operates in a logically separated workspace. Data, tickets, and configuration never leak between tenants.
Structured onboarding
A 6-step setup wizard walks through provider selection (Ollama, Codex CLI, Claude Code, or custom API endpoint), repository connection via Azure DevOps or local Git, code intelligence indexing, role assignment, integration configuration, and tenant provisioning. Every step validates before advancing — idempotent execution means re-running setup produces the same workspace state.
SLA tracking
Real-time measurement of response and resolution times against contractual commitments. Alerts before breaches, not after.
Ticket automation
Route, prioritize, and escalate tickets based on tenant tier, issue type, and SLA proximity. Reduce manual triage overhead.
Per-tenant audit trail. Always ready.
Every action within a tenant workspace is logged. Generate compliance-ready evidence for any customer, any timeframe, on demand.
From first run to first tenant in minutes.
MSPStudio’s setup wizard eliminates manual configuration. Three steps get you from installation to productive workspace.
First-run wizard
A 6-step setup flow configures your provider, connects repositories, and initializes your workspace. Each step validates before advancing — no silent misconfigurations.
Workspace initialization
Code intelligence indexes your connected repos automatically. The knowledge graph, file explorer, and process flow views are available immediately — no manual indexing step.
Role-based handoff
After setup, each team member lands in the view that matches their role. Developers see planning. Architects see structure. PMs see delivery. No one navigates to find their starting point.
From installation to productive workspace.
The first-run wizard walks through six validated steps. Each step must pass before advancing — no silent misconfigurations, no skipped prerequisites.
Step 1: Provider selection
Choose your AI provider — Ollama for air-gapped environments, Codex CLI for OpenAI, Claude Code for Anthropic, or a custom API endpoint. Provider credentials are validated before proceeding.
Step 2: Repository connection
Connect to Azure DevOps or a local Git repository. The wizard discovers available organizations, projects, and repos automatically. New repos can be created inline during setup.
Step 3: Workspace initialization
Code intelligence indexes your connected repos across 9 supported languages. The knowledge graph, file explorer, and process flow views become available immediately after indexing completes.
Step 4: Role assignment
Select your primary role — Developer, Architect, or Project Manager. The workspace adapts its default views, onboarding flow, and navigation to match your operating mode.
Step 5: Integration configuration
Connect optional integrations: Jira for task publishing, ServiceNow for ITSM bridging, or additional Azure DevOps organizations. Each integration is validated with a test connection before saving.
Step 6: Tenant provisioning
Create your first tenant workspace with isolated data, configuration, and audit trail. The wizard pre-fills sensible defaults based on your provider and role selections from previous steps.
One platform, three operating modes.
MSPStudio adapts its onboarding, defaults, and primary views to the role that matters most to you.
Developer
Auto-create DevOps repos at onboarding. Pre-filled source context, standardized workspace config, and a fast path to the planning view. Ship structured work from day one.
Architect
Start from hierarchy and structure planning. Full access to every planning view with the overview dashboard as your default landing. See the whole system before zooming in.
Project Manager
Focus on task generation and tracking. Publish user stories directly to Azure DevOps or Jira from the primary view. Manage delivery without switching tools.
From service request to sprint-ready tasks — automatically.
New work enters a structured intake queue, gets decomposed by AI, and publishes directly to your project management tool. No manual breakdown required.
Structured intake queue
Service requests enter a governed queue with metadata capture: requester, priority, tenant context, and category. Nothing falls through the cracks — every request is tracked from submission to resolution.
AI decomposition
The planning engine decomposes intake items into epics, user stories, and tasks with acceptance criteria. Decomposition respects your codebase topology via code intelligence — stories map to actual modules, not abstract requirements.
Direct publishing
Generated work items publish directly to Azure DevOps boards or Jira sprints. No copy-paste, no manual reformatting. The planner preserves hierarchy, links parent epics, and sets initial priority based on intake metadata.
Generate, structure, and publish — with AI assistance.
Hierarchy planning
Visualize and restructure work breakdown hierarchies. The AI suggests decomposition based on your codebase topology and project patterns.
User story generation
Describe your requirements in natural language. The AI planning engine generates structured user stories with acceptance criteria, ready for sprint planning.
Code Intelligence
Inherited from Consensus: a pure-JS code analysis engine that indexes repos across 9 languages (JS, TS, Python, Java, C#, Go, Rust, C, C++). Regex-based parsing feeds import resolution, call graphs, heritage tracking (extends/implements), Leiden community detection, and BFS process flow detection. MSPStudio indexes 786 files in ~18 seconds. Visualized as File Explorer, Knowledge Graph, and Process Flows — no native dependencies, no tree-sitter.
Multi-provider AI
Choose your AI engine: local Ollama for air-gapped environments, Codex CLI for OpenAI models (GPT-5.4/GPT-5.4-mini), Claude Code for Anthropic (Opus/Sonnet/Haiku), or a custom API endpoint with configurable auth types. GUI shows auth status per provider with a Test Connection button. Switch providers seamlessly without restart.
Connects to where your work already lives.
Azure DevOps
Discover organizations, projects, and repos. Create new repos during onboarding or connect existing ones. Publish generated stories directly to boards.
Jira
Connect your Jira instance for task publishing and sprint tracking. Generated user stories flow directly into your existing Jira workflows.
ServiceNow
Complementary integration for ITSM-driven organizations. Bridge the gap between service management and development planning.
Containerized, tested, portal-provisioned.
Docker deployment
Single docker compose up spins up the full stack. Isolated container with credential sync from host, per-provider volumes, and cross-platform support (Mac, Linux, WSL).
Portal provisioning
New MSPStudio instances are provisioned from DSS Portal. Licenses, workspace configuration, and AI provider settings are applied automatically during onboarding.
Quality assurance
206 tests across the full stack — covering tenant isolation, onboarding flows, intake pipeline, and DevOps integration. Every release passes lint, typecheck, test suite, and Docker build before deployment. No shortcut path to production.
A complete MSP operating surface.
MSPStudio replaces scattered tools with one structured workspace. Here is what ships on day one.
Tenant-isolated workspaces
Each customer operates in a logically separated environment. Data, tickets, configuration, and audit trails never cross tenant boundaries. Onboard unlimited tenants without operational sprawl.
AI-powered planning engine
Generate user stories with acceptance criteria, decompose work hierarchies, and publish tasks directly to Azure DevOps or Jira. Four AI providers: local Ollama for air-gapped environments, Codex CLI for OpenAI models, Claude Code for Anthropic, or a custom API endpoint with configurable auth (Bearer, Basic, Custom Header). Switch providers per workspace without reconfiguring.
Code intelligence across 9 languages
Pure-JS analysis engine inherited from Consensus. Import resolution, call graphs, community detection, knowledge graph visualization — no native dependencies required.
SLA tracking & compliance evidence
Real-time SLA measurement with proactive alerting. Every action logged for compliance-ready evidence export. Per-tenant audit isolation ensures no data leakage during reviews.
Structured plans. Transparent scope.
All plans include the governance layer, signed audit evidence, and customer portal access.
MSPStudio Starter
For one operator team running structured intake and tenant delivery.
- Up to 3 tenant workspaces
- Intake-to-planner pipeline
- Email support, EU data residency
MSPStudio Growth
For growing operator teams that need code intelligence and AI-assisted planning.
- Up to 12 tenant workspaces
- AI-assisted planning + code intelligence
- Azure DevOps + Jira hand-off integrations
- Priority support, signed audit trail
MSPStudio Enterprise
For multi-region operator estates with custom retention and SSO requirements.
- Unlimited tenant workspaces
- SSO/SCIM, custom retention
- Dedicated CSM + 24/7 on-call
- On-prem or single-tenant cloud
Prices in EUR. VAT shown at checkout. Enterprise plans are billed annually.
From first run to fully operational in one session.
MSPStudio eliminates the gap between procurement and productivity. The setup wizard handles what usually takes weeks of manual configuration.
Intake to planner pipeline
New service requests enter a structured intake queue with metadata capture: requester, priority, tenant context, and category. The AI planner decomposes them into epics, user stories with acceptance criteria, and sprint-ready tasks — respecting your codebase topology via code intelligence — then publishes directly to Azure DevOps boards or Jira sprints with preserved hierarchy.
Auto repo creation
When a new tenant is onboarded, MSPStudio can automatically provision a DevOps repository with standardized structure, branch policies, and CI/CD scaffolding. Developers start shipping from day one.
Tenant idempotency
Provisioning the same tenant twice produces the same workspace state. No duplicates, no drift, no manual cleanup. Safe to re-run during recovery or migration.
Everything your MSP needs. Nothing it does not.
MSPStudio ships as a complete operating surface — not a toolkit you assemble yourself.
Credential sync from host
AI provider credentials (Claude OAuth, Codex OAuth, or API keys) are bind-mounted read-only from the host at container startup. The entrypoint script fixes permissions automatically. No secrets baked into Docker images — rotate credentials on the host and the container picks them up on next restart. WSL auto-discovers credentials from /mnt/c/Users/*/.claude/.
Per-provider volume isolation
Each AI provider (Anthropic, OpenAI, Ollama) gets its own Docker volume for model cache and configuration. Switching providers does not require rebuilding the container.
Error recovery & safe restart
Container state is persisted to mounted volumes. Unexpected shutdowns resume from the last consistent state. No data loss, no orphaned tenant workspaces, no manual intervention.
Scale your service delivery without scaling chaos.
Start an evaluation or explore the interactive demo to see multi-tenant operations in action.