Studio B Platform Architecture

Studio B operates as a services company with SaaS offerings — consulting engagements produce deployable software products that generate recurring revenue.

Core Stack

┌──────────────────────────────────────────────────────────────────┐
│  Claude Code + MCP Servers (150+ tools)                          │
│  Unified: studiob-api (Acumatica, GitHub, Railway, GoDaddy,     │
│           Zoom, Microsoft, HubSpot)                               │
│  Native: HubSpot, Slack, Gmail, Chrome, Preview                  │
├──────────────────────────────────────────────────────────────────┤
│  Railway (Agents, Cron, BullMQ)                                  │
├──────────┬──────────┬───────────┬──────────┬─────────┬──────────┤
│ Acumatica│ Orderful │  HubSpot  │  Shopify │  Zoom   │ M365     │
│   ERP    │   EDI    │  CRM+Call │  E-comm  │  VoIP   │ Mail/Cal │
├──────────┴──────────┴───────────┴──────────┴─────────┴──────────┤
│  GitHub (IaC, CI/CD, Config-as-Code)                             │
└──────────────────────────────────────────────────────────────────┘

Platform Services

The Studio B platform consists of shared services that power all client deployments, plus per-client services provisioned based on AcuOps subscription tier.

Shared Platform Services

Service	Purpose	Stack
studiob-api	Unified API gateway + MCP server — all Acumatica, GitHub, Railway, GoDaddy, Zoom, Microsoft, HubSpot access	Fastify + MCP SDK + StreamableHTTP
business-dashboard	Ops dashboard, 12 health probes, sales intelligence	Express + EJS
studiob-docs	Documentation site (docs.b.studio)	Docusaurus 3

Per-Client Services (Tiered)

Per-client services are provisioned into isolated Railway projects during onboarding. The tier determines which services are deployed:

Service	Tier	Purpose
webhook-router	Validate+	Webhook intake, Acumatica↔HubSpot sync, CI/CD deploy hooks
support-agent	Managed	AI customer support (Claude + Qdrant KB)
provisioning-agent	Managed	Employee onboarding/offboarding automation
note-intelligence	Managed	AI note classification (8-tag taxonomy)
compliance-engine	Managed	Requirement enforcement, deadline cascades, escalation
PostgreSQL / Redis / Qdrant	Varies	Data stores provisioned per tier requirements

See AcuOps Pricing for full infrastructure breakdown by tier.

Key Principles

1. Config-as-code — Every system configuration versioned in GitHub
2. CI/CD everything — No manual promotions; every change validated through pipeline
3. Discovery-first — Field mappings extracted from live systems, not hardcoded
4. Direct TypeScript — No visual workflow builders; Railway cron + BullMQ for orchestration
5. MCP API first, browser last — API tools for all operations; browser only for UI validation
6. Build for reuse — Everything templated for multi-tenant deployment
7. Gateway architecture — No client service holds direct ERP credentials; all access routed through studiob-api

MCP Server Architecture

All MCP tools are consolidated into the unified studiob-api service:

• Runtime: TypeScript + Fastify 5
• Protocol: MCP SDK with StreamableHTTP transport at /mcp
• Auth: Bearer token via Authorization header
• Deploy: Railway with GitHub auto-deploy on push to main
• Systems: Acumatica (26 tools), GitHub (8), Railway (14), GoDaddy (15), Zoom (65), Microsoft (22), HubSpot

Service Model

Stream	Type
Consulting	Project-based engagements
SaaS Products (AcuOps)	Monthly recurring subscription
Managed IT	Retainer-based operations
Platform Licensing	Monthly recurring subscription