Skip to content

Who does what

The principle is simple: you do everything that concerns your own applications, HD Services does only what you cannot and is the safety net when something does not work out. The portal, the API and the MCP server give you the same abilities; HD Services works in the same portal, with the same screens.

Topic What you can do
Stacks Change settings, compose file and variables; deploy and stop; nightly update on or off; view and restore revisions; manage the git source and the deploy webhook; maintain the access list.
Containers View state; start, stop, restart; read logs.
Sites Create and edit sites; set up syncing; upload files; restore previous versions; manage the check webhook.
Backups Create, change and run backups; view, download and delete files.
Alerts View active alerts and history; manage your own e-mail and webhook channels; send test alerts.
Certificates Request or upload certificates for your own domains.
Integrations Create and revoke API tokens; connect and disconnect assistants; manage logins for private registries.
Topic Why
User accounts Creating accounts, disabling them and resetting passwords.
Networks for the portal Which addresses may log in (the IP filter).
Creating and deleting stacks A new application is set up from the template library; deleting is irreversible.
DNS A records for domains HD Services manages.
The web gateway Traefik, the portal’s certificate, the e-mail address for Let’s Encrypt.
Security markers Ports directly to the outside, exemptions from the platform rules, protected services, the HD networks on access lists.
Platform and operating system Updates of the portal software and of the server itself; disk space; the backup disk.
Copy outside the server The destination and the encryption of the offsite backups.
Restoring backups A manual procedure (self-service restore is on the roadmap).

Mail helpdesk@hdservices.nl or call +31 348 473340. Mention the address of your environment and, for a stack, its name. Never include a token or password: HD Services does not need them.

An assistant that works through a token or a connection can do exactly what the token or connection allows, and never more than your own account. It cannot delete stacks, sites, backup files or certificates and cannot manage tokens or users. See The MCP server.