Partner Platform — Technical Details
Architecture
The Partner Platform runs on Studio B's multi-tenant infrastructure. Each client environment is fully isolated with its own:
- Acumatica API credentials (session gate per tenant)
- Redis key namespace (
{tenantId}:*) - Health probe configuration
- Schema drift baselines
- Slack alerting channels
- HubSpot pipeline (optional)
Dashboard
The multi-tenant dashboard provides a single view across all client environments:
- Fleet health — Green/yellow/red status for every client, updated every 15 minutes
- Schema drift alerts — Field changes detected across any client environment
- Upgrade readiness — Per-client customization risk scores and compatibility reports
- Deploy history — CI/CD deployment logs with test results per client
- License utilization — Acumatica license usage across the portfolio
Health Monitoring
12 probes per client environment, running every 15 minutes:
| Probe | What It Checks |
|---|---|
| API connectivity | Acumatica REST API session auth |
| Schema integrity | Field types, required flags, custom fields present |
| Customization status | Published projects, pending changes |
| Session availability | API license utilization |
| Integration health | Webhook endpoints responding |
| Performance | API response times |
CI/CD Pipeline
Per-client customization deployment:
- Import — Upload customization project via Acumatica Customization API
- Publish — Trigger publish with co-publish conflict checking (all active projects)
- Validate — Run 66 Playwright tests against post-publish environment
- Notify — Slack alert with pass/fail summary and detailed test report
Client Onboarding
Adding a new client to the Partner Platform:
- Create client configuration (Acumatica URL, credentials, tenant name)
- Run initial schema scan (baseline for drift detection)
- Configure Slack channel for alerts
- Run first health check cycle
- Deploy monitoring — operational in under 1 hour
API Access
Partners get API access for integration with their own tools:
- Health status endpoint (JSON)
- Schema drift events (webhook)
- Deploy trigger (CI/CD API)
- Client provisioning (create/update/deactivate)