MCP DigLab can be delivered as a managed connection or as an independent installation on customer-owned hosting. Choose the model before creating accounts, moving configuration or promising an operating arrangement.
Compare the options#
| Responsibility | Managed connection | Customer-owned installation |
|---|---|---|
| Platform hosting | DigLab-operated infrastructure. | Your compatible hosting, server or container environment. |
| Connection address | The endpoint supplied in your handoff. | An endpoint on your installation's agreed domain. |
| Platform administration | Normally handled by DigLab. | Assigned to your administrator, DigLab or both as agreed. |
| Service accounts | Your authorised business accounts. | Your authorised business accounts. |
| Updates and backups | Covered by the agreed managed-service scope. | Your responsibility unless maintenance is explicitly included. |
| Software activation | Managed for the hosted installation. | Must be arranged and verified for the separate installation. |
Customer-owned hosting#
The standalone application can be installed without WordPress. A WordPress installation is another supported build when that is the agreed delivery route. The software and infrastructure requirements differ between builds; follow the package-specific instructions.
Each installation has its own administrator configuration, encryption key, database, connections and activation. A private MCP endpoint is not a customer dashboard account. Giving someone an administrator login can grant much broader access than giving them a connection key.
Agree ownership before installation#
Record who owns the domain and hosting, who may administer the platform, who manages updates, who holds recoverable backups and who handles incidents. Also agree how activation and access are handled if the service arrangement ends. Branding alone does not grant software redistribution or license-transfer rights.
Hosting the platform yourself does not keep every tool result on that server: results are sent to your chosen AI application, and integrations contact their own upstream services. Review those data paths when deciding where to host.
Continue with self-hosting for the standalone deployment checklist or quick start for an existing managed connection.