Skip to Content
Protocol D Partner Architecture: How MSPs, SysAdmins, and Web Studios Monetize Enterprise ERP Without Losing Account Control

Protocol D Partner Architecture: How MSPs, SysAdmins, and Web Studios Monetize Enterprise ERP Without Losing Account Control

A non-compete engineering and commercial framework enabling IT infrastructure providers and digital agencies to earn 15–20% referral commissions or deliver 100% White-Label Odoo 19 cores while protecting their recurring retainers.

Every established Managed Service Provider (MSP), outsourced systems administration practice, Microsoft 365 integrator, and B2B web studio eventually confronts the same boardroom inflection point. For five or seven years, your team has maintained ironclad uptime across a mid-market client's infrastructure: Entra ID and Active Directory domain controllers, Fortinet or MikroTik site-to-site routing, Proxmox hypervisor clusters, endpoint detection agents, or high-converting corporate web storefronts. Because your engineers answer tickets in minutes and prevent ransomware incidents before they reach production, the client's chief executive treats you as their primary technology advisor.

Then the client crosses forty to one hundred employees, adds a second warehouse or assembly line, and outgrows disconnected spreadsheets and legacy desktop bookkeeping software. The managing director invites you into an executive planning session and asks a direct question: can your team deploy a unified Enterprise Resource Planning (ERP) core covering multi-level Manufacturing Resource Planning (MRP), barcode Warehouse Management (WMS), automated B2B procurement portals, and AI-assisted sales workflows?

At that moment, traditional IT infrastructure providers and digital studios face an asymmetric strategic trap where both conventional responses destroy enterprise account value:

  1. The Passive Referral Surrender (Account Poaching): You decline the ERP engagement to stay focused on network administration, cloud licensing, or frontend web development. Within thirty days, a generalist "full-service" IT vendor enters the client's boardroom to deliver the ERP. Once embedded in executive financial reviews with visibility into server topologies and SaaS budgets, that competitor bundles managed M365 licensing, cloud hosting, firewall maintenance, and web support into their post-launch SLA—poaching your €1,800 to €5,500 monthly recurring retainer within two quarters.
  2. The Improvised Subcontractor Gamble (Reputational Contagion): To keep competitors out of the account, you attempt to assemble an ERP internally using freelance PHP or JavaScript developers, e-commerce inventory plugins, or unvetted ERP subcontractors billed by the hour. Within six months, stock valuation drifts from general ledger balances, unguarded PostgreSQL queries lock warehouse barcode scanners during peak dispatch, and the chief financial officer escalates the failure directly to the CEO—erasing years of infrastructure trust overnight.

To eliminate both failure modes, we engineered Protocol D within our DLAB Shuttle Launch Protocols: a deterministic commercial and technical alliance architecture built specifically for MSPs, outsourced SysAdmins, M365 integrators, and digital studios. Backed by a legally binding Zero-Poaching Perimeter and a clean Layer-3 to Layer-7 operational boundary, Protocol D allows channel partners either to earn 15–20% transparent referral commissions while locking in 100% of their infrastructure retainers (Track D1), or to front a 100% White-Label Odoo 19 core under their own agency brand (Track D2).

Protocol D Channel Architecture & Account Protection Benchmarks

Contractual and operational metrics governing MSP, SysAdmin, and Web Studio alliances on Single-Tenant Odoo 19

15–20%
Protocol D Referral Commission
Partner payout on fixed-scope Odoo 19 architecture and implementation contracts under Track D1 with zero delivery liability.
100%
Contractual Retainer Non-Compete
Binding Zero-Poaching Perimeter prohibiting DLAB.MD from quoting M365, endpoint, LAN/VPN hardware, or creative media retainers.
6 Weeks
Fixed-Scope ERP Core Delivery
Deterministic Single-Tenant Odoo 19 CE Golden Image rollout replacing open-ended hourly subcontracting.
0
Junior Outsourcing Risk
Principal-level engineering across ACID double-entry ledgers, MRP costing, WMS routing, and scoped MCP AI agents.

Anatomy of Channel Cannibalization: Why Infrastructure SLAs Collide with Transactional Ledgers


Systems administration and transactional ERP engineering appear adjacent to non-technical executives, yet they rely on orthogonal engineering disciplines. An elite MSP or outsourced SysAdmin team optimizes for infrastructure determinism: packet forwarding latency across WireGuard and IPsec tunnels, BGP and VLAN isolation, ZFS snapshot replication intervals, zero-trust conditional access policies in Microsoft Entra ID, and fifteen-minute RPO/RTO disaster recovery runbooks. Similarly, a specialized B2B web or performance studio optimizes for acquisition velocity: Core Web Vitals, brand design systems, headless storefront UX, and paid media conversion funnels.

Enterprise ERP architecture operates inside a completely different failure domain—stateful financial and physical ledger invariants:

  • Every warehouse receipt (stock.picking), manufacturing consumption line (stock.move), and supplier landed-cost allocation (stock.landed.cost) must atomically generate balanced double-entry accounting journal items (account.move.line) inside PostgreSQL without race conditions or rounding drift.
  • Multi-company procurement rules, automated FIFO or Average Cost (AVCO) inventory revaluations, and gross margin floor constraints must execute strictly inside server-side ORM transactions (models.Constraint and SELECT ... FOR UPDATE NOWAIT row-level locks) rather than brittle webhook glue.
  • Autonomous AI assistants interacting with customer orders or stock availability must enforce role-based access control (ir.model.access and ir.rule) through strongly typed Model Context Protocol (MCP) tools so an external chat prompt can never leak wholesale cost tables.

As we documented in our analysis of why your enterprise systems integrator is often the weakest link, generalist IT conglomerates weaponize ERP complexity during presales. They enter a mid-market manufacturing or distribution company promising an "all-in-one digital transformation," bill hundreds of open-ended discovery hours, and immediately audit the incumbent MSP's firewall rules, cloud VM invoices, and Microsoft CSP tenant. Whenever their own buggy ERP customizations run slowly, the generalist integrator blames "the incumbent sysadmin's network latency" or "the web studio's DNS configuration" to justify seizing the entire IT and marketing budget.

Protocol D Architecture: Two Deterministic Tracks Under a Zero-Poaching Perimeter


Protocol D resolves channel conflict by codifying a strict division of technical labor and commercial ownership before the first client discovery call takes place. Because our engineering practice is built around why we never sell source code and deliver ERP as managed infrastructure, we have zero economic incentive to sell workstation support, office networking hardware, Microsoft 365 seat licenses, or creative advertising retainers. Our sole domain is high-integrity Single-Tenant Odoo 19 ERP, MRP, WMS, Server-Side AdTech telemetry, and MCP AI infrastructure.

Every Protocol D partnership is governed by a bilateral Zero-Poaching Perimeter Schedule containing three non-negotiable covenants:

  1. Strict Service Non-Compete: DLAB.MD is contractually barred from pitching, quoting, auditing-for-replacement, or delivering LAN/WAN switching, MikroTik/Fortinet firewall administration, workstation helpdesk, on-premise Proxmox/VMware virtualization, Microsoft 365 / Google Workspace licensing, PBX hardware, or creative agency media buying to any partner-registered account for the lifetime of the relationship plus thirty-six months.
  2. Infrastructure Co-Anchoring: Rather than bypassing the incumbent MSP or web studio, our Single-Tenant Odoo 19 deployment explicitly integrates with the partner's existing control plane—delegating corporate OIDC Single Sign-On, DNS zone authority, site-to-site industrial printer tunnels, and external Prometheus uptime monitoring directly to the partner's NOC.
  3. Fixed-Scope 6-Week Delivery: End-clients are never subjected to runaway time-and-materials billing that erodes executive goodwill. Every core deployment follows a fixed-budget, six-week engineering sprint on isolated cloud compute.

Track D1 — Transparent Referral & Co-Managed Perimeter (15–20% Partner Commission)

Track D1 is engineered for outsourced SysAdmins, MSPs, telecom/network integrators, cloud infrastructure consultants, and B2B fractional CIOs who want to monetize enterprise ERP demand immediately while assuming zero software delivery or accounting liability.

Under Track D1:

  • The MSP or IT advisor registers the opportunity via the Protocol D intake channel and co-hosts a structured 24-hour Architecture X-Ray briefing with DLAB.MD principal architects.
  • DLAB.MD contracts directly with the end-client for the Single-Tenant Odoo 19 ERP, MRP, WMS, and MCP AI implementation and ongoing L3 application SLA.
  • The partner earns a 15% to 20% referral commission on the architecture and implementation contract value (tiered by partner involvement in network/SSO readiness and annual deal volume), settled transparently within ten business days of client milestone clearing.
  • Crucially, the MSP expands its own recurring billable footprint with the client: configuring Entra ID / Keycloak OIDC groups for ERP role mapping, provisioning isolated WireGuard VLAN spokes for warehouse Zebra thermal printers and electronic scales, and adding ERP endpoint probes to the MSP's 24/7 NOC dashboard.

Track D2 — Silent 100% White-Label Engineering Core

Track D2 is engineered for B2B Web Studios, E-Commerce Agencies, Performance Marketing Firms, and Management Consultancies that want to own the entire client contract under their own corporate identity, transforming one-off €6,000 web builds into €30,000–€90,000 enterprise commerce + ERP platforms with multi-year recurring retainers.

Under Track D2:

  • DLAB.MD operates as your invisible, principal-grade backend engineering division under mutual NDA and GDPR Article 28 sub-processor governance.
  • Every visible surface of the Single-Tenant Odoo 19 environment is completely debranded via our dlab_corporate_brand architecture: custom agency subdomains, custom login portals, white-labeled transactional SMTP relays (SPF, DKIM, and DMARC aligned to the agency or client domain), branded PDF commercial proposals, and role-based operational manuals bearing your studio's visual identity.
  • As detailed in our blueprint on recovering the lost 42% of EU ad attribution via Server-Side Meta CAPI, Omnichannel AI, and White-Label ERP delivery, digital agencies can bundle headless or native Odoo 19 storefronts, WhatsApp/Instagram MCP conversational agents, and ledger-verified Server-Side CAPI telemetry—locking in recurring retail margin above our fixed wholesale SLA rate.

Protocol D Execution Pipeline: From Partner Registration to Quarterly Settlement

01

Joint 24h Architecture X-Ray

Partner registers the account under NDA; principal architects map ERP, MRP, WMS, and AI scope within 24 hours without disrupting incumbent IT.

02

Perimeter & Non-Compete Matrix

Execution of the Zero-Poaching Schedule defining Track D1 (15–20% commission) or Track D2 (100% White-Label) and L1–L7 SLA boundaries.

03

6-Week Isolated Odoo 19 Deployment

Single-Tenant Odoo 19 CE Golden Image provisioning, ledger migration, OIDC/WireGuard binding to partner NOC, and operator training.

04

Co-Managed SLA & Quarterly Partner Settlement

Deterministic milestone commission payouts or wholesale White-Label billing alongside shared read-only Prometheus SLA telemetry.

Operational Demarcation Matrix: Layer-1 to Layer-7 Responsibility Split


To eliminate finger-pointing during peak production operations, Protocol D attaches an explicit Responsibility Demarcation Matrix to every engagement. Neither team ever holds root credentials inside the other team's failure domain, yet both systems interoperate seamlessly over documented cryptographic interfaces.

Infrastructure & Application LayerEnd-Client Internal TeamMSP / SysAdmin / Web Studio PartnerDLAB.MD Single-Tenant ERP Core
Corporate LAN, Wi-Fi 6 & Firewall RoutingPhysical facility access100% Owned & Billed by Partner (MikroTik, Fortinet, VLANs, ISP failover)Zero access; consumes isolated WireGuard spoke if industrial LAN printing is required
Workstations, Barcode Hardware & M365Daily operator usage100% Owned & Billed by Partner (Windows/macOS MDM, Entra ID, M365 seats, Zebra scanners)Zero hardware/seat reselling; validates browser & Zebra ZPL compatibility
Identity & Single Sign-On (OIDC / SAML)Approves HR onboarding & offboarding100% Owned by Partner (Manages Entra ID / Keycloak groups & MFA policies)Consumes signed OIDC JWKS tokens mapped to Odoo 19 res.groups
Storefront UX, SEO & Paid Media BuyingApproves brand campaigns & pricing100% Owned by Web Studio (Creative, paid social, CRO, custom domain DNS)Provides Odoo 19 e-commerce / headless APIs & Server-Side CAPI webhook dispatch
Single-Tenant Cloud VM & PostgreSQL 17Data controller ownership (GDPR)Read-only Prometheus /healthz & TLS expiry scraping into partner NOC100% Managed by DLAB.MD (Golden Image, IPC hardening, WAL PITR backups)
Odoo 19 ORM, Accounting, MRP, WMS & MCP AIEnters orders, posts invoices, runs productionZero code maintenance or ledger debugging liability100% Engineered & Guaranteed by DLAB.MD (Zero-Hardcode modules, L3 SLA)

Mathematical Formulation of Partner Account Lifetime Value (LTVMSP)


We can quantify why passive ERP avoidance is financially destructive for an MSP or web studio—and how Protocol D transforms client expansion into a compounding capital asset.

Consider an incumbent MSP or digital agency managing a mid-market B2B client on a monthly recurring retainer RMSP (measured in EUR), operating at a gross delivery margin ratio mMSP over an evaluation horizon of T months (for example, T = 36 months).

When the client requests an enterprise ERP and the incumbent partner declines involvement, an external "full-service" IT integrator enters the account. Let cpoach denote the monthly account churn hazard induced by that competitor cross-selling managed infrastructure, cloud hosting, M365, or web retainers once they control the client's ERP boardroom cadence (empirically cpoach ≈0.065 per month, corresponding to a >55% cumulative probability of losing the retainer within twelve months). The expected Churn-Adjusted Standalone Retainer Value (LTVstandalone) decays geometrically:

LTVstandalone = ∑t=1T RMSP ·mMSP ·(1 - cpoach)t ≈RMSP ·mMSP ·1 - (1 - cpoach)Tcpoach

Now contrast this against Protocol D. By proactively anchoring the Single-Tenant Odoo 19 transformation, the partner neutralizes competitive entry and binds the ERP to the partner's own OIDC identity and WireGuard network fabric, compressing monthly churn down to baseline structural attrition cprot ≈0.012. Simultaneously, the partner captures either a fixed-scope referral commission VERP ·kcomm (where VERP is the ERP architecture and implementation contract value and 0.15 ≤kcomm ≤0.20 in Track D1) or a recurring monthly net White-Label ERP and CAPI margin MWL (in Track D2):

LTVMSP = VERP ·kcomm + ∑t=1T (RMSP ·mMSP + MWL) ·(1 - cprot)t

Evaluating this model on a representative European 70-employee wholesale and light-manufacturing account over T = 36 months demonstrates the asymmetry:

  • Baseline Parameters: Monthly MSP infrastructure and M365 retainer RMSP = 2,400EUR at gross margin mMSP = 0.65 (net monthly contribution of €1,560); fixed-scope Odoo 19 MRP/WMS/AI contract VERP = 38,000EUR.
  • Scenario A — Passive Surrender (LTVstandalone at cpoach = 0.065): Because survival probability drops rapidly once a rival full-service vendor enters C-level steering meetings, the expected 36-month net value of the €2,400/month retainer collapses from a nominal €56,160 down to €21,810.
  • Scenario B — Protocol D Track D1 Referral (kcomm = 0.18, MWL = 0, cprot = 0.012): The MSP collects €6,840 in immediate upfront referral commission (18% of €38,000) with zero ERP engineering hours at risk, while retaining €45,190 in protected 36-month net infrastructure margin—yielding €52,030 in total net value.
  • Scenario C — Protocol D Track D2 White-Label Agency (MWL = 850EUR/month net recurring markup plus €7,600 implementation margin spread): Total 36-month net account value reaches €77,410.

Across both tracks, the Protocol D Partner Capital Ratio satisfies:

LTVMSPLTVstandalone ≥2.38

Technical Perimeter Separation: Zero-Hardcode Odoo 19 Telemetry, OIDC & WireGuard Integration


A serious systems administrator or agency CTO will rightfully distrust marketing promises of "co-management" unless the boundary is enforced in code. When an MSP shares root SSH keys with an external software vendor, audit accountability vanishes; conversely, if the MSP has zero visibility into whether the ERP application server is healthy, the client still calls the MSP helpdesk first when a warehouse tablet fails to load a picking slip.

Protocol D solves this through a Zero-Share Cryptographic Perimeter implemented natively on our Odoo 19 Golden Image:

  1. Identity Federation Without Database Superuser Sharing: The MSP configures an OpenID Connect (OIDC) enterprise application inside the client's Entra ID or Keycloak tenant. Odoo 19 validates bearer tokens and maps identity claims to ERP security groups, while res.company enforces the designated OIDC provider via foreign-key restriction (ondelete='restrict'). When an MSP technician disables a departing sales manager's account in Active Directory, ERP access terminates immediately without the MSP needing base.group_system privileges inside Odoo.
  2. Point-to-Point WireGuard Spoke for Industrial Hardware: Warehouse label printers (Zebra ZPL over TCP 9100) and serial floor scales reside on an isolated /29 industrial VLAN on the MSP's MikroTik or Fortinet router. The DLAB Odoo 19 VM connects exclusively to that print-spooler subnet via an unprivileged WireGuard spoke interface—zero lateral network routing to corporate file shares or domain controllers is permitted at the kernel nftables layer.
  3. Read-Only HMAC-Scoped NOC Telemetry (/api/v1/perimeter/healthz): In full compliance with our Universal Zero-Hardcode Doctrine, every partner monitoring parameter—health-probe enablement, constant-time bearer secret, SLA worker latency threshold, and industrial WireGuard gateway target—is stored as typed fields on res.company and managed visually in res.config.settings. The MSP's Prometheus, Zabbix, or Datadog instance scrapes /api/v1/perimeter/healthz every 30 seconds to verify PostgreSQL ACID read readiness, cron queue health, and print-tunnel reachability—receiving zero financial ledger rows (account.move) and zero personal data (res.partner).
# -*- coding: utf-8 -*-
import hmac
import json
import logging
import socket
import time
from odoo import api, fields, http, models
from odoo.http import request

_logger = logging.getLogger(__name__)


class ResCompany(models.Model):
_inherit = "res.company"

x_protocol_d_noc_enabled = fields.Boolean(
string="Enable Partner NOC Health Telemetry",
default=False,
help="Expose read-only infrastructure health metrics to the MSP monitoring stack.",
)
x_protocol_d_partner_id = fields.Many2one(
comodel_name="res.partner",
string="Designated Protocol D MSP / Agency Partner",
ondelete="restrict",
help="Registered channel partner responsible for L1-L4 network and SSO perimeter.",
)
x_protocol_d_oauth_provider_id = fields.Many2one(
comodel_name="auth.oauth.provider",
string="Enforced Partner OIDC Identity Provider",
ondelete="restrict",
help="Corporate Entra ID or Keycloak OIDC provider managed by the partner NOC.",
)
x_protocol_d_noc_bearer_secret = fields.Char(
string="Partner Prometheus Bearer Secret",
groups="base.group_system",
copy=False,
help="Cryptographic token validated via constant-time HMAC comparison.",
)
x_protocol_d_sla_latency_ms = fields.Integer(
string="PostgreSQL Probe SLA Ceiling (ms)",
default=85,
required=True,
help="Maximum acceptable database round-trip latency before degraded status.",
)
x_protocol_d_wg_spooler_host = fields.Char(
string="WireGuard Print Spooler Endpoint (Host:Port)",
help="Optional partner VLAN CUPS/ZPL endpoint verified via TCP socket handshake.",
)


class ResConfigSettings(models.TransientModel):
_inherit = "res.config.settings"

x_protocol_d_noc_enabled = fields.Boolean(
related="company_id.x_protocol_d_noc_enabled",
readonly=False,
)
x_protocol_d_partner_id = fields.Many2one(
related="company_id.x_protocol_d_partner_id",
readonly=False,
)
x_protocol_d_oauth_provider_id = fields.Many2one(
related="company_id.x_protocol_d_oauth_provider_id",
readonly=False,
)
x_protocol_d_noc_bearer_secret = fields.Char(
related="company_id.x_protocol_d_noc_bearer_secret",
readonly=False,
)
x_protocol_d_sla_latency_ms = fields.Integer(
related="company_id.x_protocol_d_sla_latency_ms",
readonly=False,
)
x_protocol_d_wg_spooler_host = fields.Char(
related="company_id.x_protocol_d_wg_spooler_host",
readonly=False,
)


class ProtocolDPerimeterController(http.Controller):

@staticmethod
def _probe_tcp_endpoint(endpoint_str: str, timeout_sec: float = 1.5) -> int:
if not endpoint_str or ":" not in endpoint_str:
return 1
host, port_raw = endpoint_str.rsplit(":", 1)
try:
with socket.create_connection((host.strip(), int(port_raw)), timeout=timeout_sec):
return 1
except OSError:
return 0

@http.route(
"/api/v1/perimeter/healthz",
type="http",
auth="none",
methods=["GET"],
csrf=False,
save_session=False,
)
def partner_noc_healthz(self, **kwargs):
"""
Zero-PII, Zero-Ledger read-only telemetry endpoint for MSP Prometheus / Zabbix NOCs.
Authenticates via company-scoped Bearer secret using constant-time digest comparison.
"""
auth_header = request.httprequest.headers.get("Authorization", "")
if not auth_header.startswith("Bearer "):
return request.make_response(
json.dumps({"status": "unauthorized"}),
headers=[("Content-Type", "application/json")],
status=401,
)
provided_token = auth_header[7:].strip()

company = request.env["res.company"].sudo().search(
[("x_protocol_d_noc_enabled", "=", True)], limit=1
)
expected_token = (company.x_protocol_d_noc_bearer_secret or "") if company else ""
if not company or not expected_token or not hmac.compare_digest(
provided_token.encode("utf-8"), expected_token.encode("utf-8")
):
return request.make_response(
json.dumps({"status": "forbidden"}),
headers=[("Content-Type", "application/json")],
status=403,
)

t0 = time.monotonic()
request.env.cr.execute("SELECT 1")
request.env.cr.fetchone()
db_latency_ms = round((time.monotonic() - t0) * 1000.0, 2)

spooler_up = self._probe_tcp_endpoint(company.x_protocol_d_wg_spooler_host or "")
sla_ok = int(db_latency_ms <= company.x_protocol_d_sla_latency_ms and spooler_up == 1)
base_origin = request.httprequest.host_url.rstrip("/")

payload = {
"status": "healthy" if sla_ok else "degraded",
"origin": base_origin,
"metrics": {
"odoo_db_ping_ms": db_latency_ms,
"odoo_sla_ceiling_ms": company.x_protocol_d_sla_latency_ms,
"wireguard_spooler_up": spooler_up,
"oidc_enforced": int(bool(company.x_protocol_d_oauth_provider_id)),
"perimeter_sla_compliant": sla_ok,
},
}
http_code = 200 if sla_ok else 503
return request.make_response(
json.dumps(payload),
headers=[
("Content-Type", "application/json"),
("Cache-Control", "no-store"),
],
status=http_code,
)

On the MSP side, integrating this isolated Odoo 19 core into an existing Prometheus or Grafana NOC stack requires fewer than fifteen lines of declarative scrape configuration—giving L1 sysadmins instant diagnostic clarity (whether a warehouse issue stems from local ISP packet loss, the WireGuard print tunnel, or cloud compute latency) without touching a single accounting table:

# MSP NOC: prometheus-erp-perimeter.yml (Zero-Credential Ledger Isolation)
scrape_configs:
- job_name: "protocol_d_odoo19_perimeter"
scrape_interval: 30s
scrape_timeout: 5s
scheme: https
metrics_path: "/api/v1/perimeter/healthz"
authorization:
type: Bearer
credentials_file: "/etc/prometheus/secrets/protocol_d_client_token"
static_configs:
- targets:
- "erp.client-industrial-domain.eu"
labels:
perimeter_track: "protocol_d1_comanaged"
l1_owner: "partner_msp_noc"
l3_owner: "dlab_single_tenant_core"

Ad-Hoc Subcontracting vs. Protocol D Non-Compete Architecture


Many web studios and IT consultancies have been burned in the past by informal "referral handshakes" or offshore freelance outsourcing. In informal arrangements, either the referred software house stops paying commissions on Phase 2 expansions and quietly pitches managed cloud hosting directly to the client, or the white-label freelancer disappears mid-migration leaving undocumented monkey-patches inside core Odoo files.

Protocol D eliminates both failure vectors through contractual transparency, architectural discipline, and deterministic SLA boundaries:

Channel Engagement Models: Informal Subcontracting vs. Protocol D Alliance

Ad-Hoc ERP Subcontracting or Passive Referral

High Churn Risk
  • No binding service non-compete; ERP vendor cross-sells M365, cloud hosting, and web retainers
  • Open-ended hourly billing blows past client budgets and erodes executive trust in your advice
  • Hardcoded database IDs and brittle plugins break double-entry accounting and stock valuation
  • Shared SSH root credentials blur GDPR Article 28/32 liability during security audits
  • Opaque or uncollected referral payouts once initial discovery converts into multi-phase work

Protocol D Non-Compete MSP & Agency Architecture

Protected LTV
  • Binding Zero-Poaching Perimeter protecting 100% of partner IT, M365, network, and media retainers
  • Track D1 pays 15–20% commission on fixed-scope 6-week Odoo 19 deployments with zero delivery risk
  • Track D2 delivers 100% White-Label ERP, MCP AI, and Server-Side CAPI under your agency domain
  • Clean OIDC, WireGuard, and HMAC healthz integration anchoring the ERP to your partner NOC
  • Zero-Hardcode Single-Tenant Golden Image with full ACID ledger integrity and L3 SLA

Governance, GDPR Sub-Processor Clarity, and When Protocol D Is Not the Right Fit


Operating across European Union and cross-border B2B markets requires rigorous legal alignment alongside technical isolation. Under Track D1, DLAB.MD executes the Data Processing Agreement (GDPR Article 28) directly with the end-client for the Single-Tenant ERP virtual machine, ensuring the MSP carries zero statutory sub-processor liability for financial, HR, or customer ledger records. Under Track D2 (White-Label), DLAB.MD operates under a back-to-back GDPR Article 28/32 Technical Sub-Processor Schedule with EU regional cloud residency, encrypted point-in-time PostgreSQL backups, and strict RemoveIPC=no POSIX daemon hardening—giving the agency partner turnkey enterprise compliance documentation ready for corporate procurement audits.

Equally important, architectural integrity requires stating clearly when Protocol D is not the right fit:

  1. Micro-Businesses Seeking €30/Month Shared SaaS Bookkeeping: Solopreneurs or three-person firms looking only to issue five PDF invoices a month with zero warehouse inventory, zero BOM manufacturing, zero B2B customer portals, and zero omnichannel AI workflows do not need a dedicated Single-Tenant Odoo 19 server. Standard entry-level cloud accounting tools serve that segment at lower overhead.
  2. Hourly "Body-Shop" Staff Augmentation Without Architectural Governance: If a digital agency wants to rent a junior Python developer for fifteen hours a week to commit unreviewed patches directly into an existing, broken third-party ERP repository with hardcoded SQL queries, we decline the engagement. We only guarantee SLAs on clean, Zero-Hardcode architectures we audit and govern end-to-end.
  3. Pure Hardware Box-Movers With Zero Executive Advisory Relationship: Protocol D relies on a warm, trusted executive handover during the Joint 24h Architecture X-Ray. Transactional hardware resellers who drop off boxed laptops once a year without maintaining an active infrastructure, M365, network, or digital marketing relationship lack the strategic context required to co-anchor an enterprise transformation.

For established MSPs, outsourced SysAdmin teams, M365 integrators, and B2B digital studios whose best clients are actively outgrowing legacy accounting and fragmented spreadsheets, Protocol D turns your biggest churn threat into a protected, high-margin growth lever. You keep every euro of your recurring infrastructure or agency retainer, lock full-service competitors out of your client's boardroom, and monetize enterprise-grade Odoo 19 engineering with zero operational guesswork.

Protocol D Partner Program for MSPs, SysAdmins & Web Studios FAQ


Before you disclose client identity, both parties execute the Protocol D Zero-Poaching Schedule, which imposes a strict contractual prohibition against DLAB.MD quoting or delivering endpoint support, LAN/WAN networking, Microsoft 365 licensing, on-premise hypervisors, or creative media buying for the life of the client plus 36 months. Technically, our Odoo 19 Single-Tenant deployment delegates OIDC Single Sign-On, DNS, and industrial WireGuard routing to your NOC, cementing your team inside the client's architecture.

In Track D1, you introduce DLAB.MD as the specialized ERP engineering partner; we contract directly with your client, assume 100% of delivery and accounting SLA liability, and pay you a 15–20% commission on the architecture and implementation contract within 10 business days of milestone completion. In Track D2, your web studio or consultancy fronts the entire contract under your own brand, domain, and custom SMTP using our debranded Odoo 19 Golden Image, capturing full retail markup over our fixed wholesale engineering rate.

No. DLAB.MD principal engineers handle 100% of Odoo 19 ORM customization, PostgreSQL 17 tuning, double-entry financial ledger migration, MRP/WMS configuration, and L3 application support. Your infrastructure team only manages familiar Layer-1 to Layer-4 and identity touchpoints—such as Entra ID OIDC group assignments, WireGuard print tunnels, and scraping our read-only /api/v1/perimeter/healthz JSON endpoint.

Once registered via Launch Protocol D on shuttle.dlab.md, our principal architects execute a Joint Architecture X-Ray within 24 hours, delivering a fixed-scope engineering blueprint, perimeter matrix, and deterministic 6-week Single-Tenant Odoo 19 deployment schedule ready for C-level sign-off.

OPEN-CORE ERP (€0/SEAT) • DLAB SHUTTLE DLAB.MD // ENGINEERING ADVISORY

Ready to Replace Fragmented Micro-SaaS & Middleware with One Owned Ledger?

Explore interactive 3D architecture blueprints, live 36-month TCO & revenue simulators, Smart QR + WhatsApp commerce pipelines, and Protocol D 15–20% MSP/Agency partnerships on Dlab Shuttle—or request a 15-minute Quote X-Ray.