Skip to main content

Teams & reseller

Agencies, boutique hosts, and internal platform teams share a pattern: many applications, many stakeholders, and a constant tension between speed and safety. DeployDock approaches “teams and reseller” as a governance layer—roles that mean something, boundaries that reduce blast radius, and audit trails that survive employee turnover.

Roles are contracts​

Every button in a panel should map to a role decision: who may issue TLS, who may restore backups, who may see billing-adjacent metadata. DeployDock encourages least privilege defaults with obvious escalation paths for break-glass maintenance. Conceptual background: Users & roles.

Poor role design shows up as shared passwords in Slack, “temporary” admin grants that never expire, and Friday-night panic when nobody knows who changed the firewall. Invest time naming roles after outcomes (“deployer”, “auditor”, “billing viewer”) rather than job titles that drift.

Isolation between customers​

Reseller hosting is multi-tenancy without a hypervisor between customers. Isolation must be OS-level and operational: separate system users, separate database credentials, separate TLS contexts, and clear filesystem roots so one customer cannot read another’s uploads.

The panel should make cross-customer navigation deliberate—never accidental. When you onboard a new client, treat it like a mini production launch: checklist domains, backups, monitoring, and owner on call.

Templates scale kindness​

Templates turn “the right way” into “the default way.” Capture vhost patterns, PHP-FPM pools, Node cluster sizes, and backup schedules as reviewable templates so new sites inherit policy instead of improvising. See Templates for how concepts map to repeatable stacks.

Templates also shorten onboarding: a junior engineer selects “standard Laravel” and inherits the org’s hardened baseline rather than rediscovering sysctl values from a blog post.

Support workflows​

Agencies often want ticket-shaped communication even if the panel is internal. Pair DeployDock with your ITSM tool of choice; the panel supplies technical truth (what deployed, when certs renew) while tickets carry customer intent. If you need SSO or SCIM integrations for larger orgs, start at Enterprise overview.

Billing honesty​

This OSS documentation site does not implement billing engines. It does expect you to document your commercial packaging clearly: what a seat includes, what happens when a client leaves, and how data export works. Confusion here creates legal risk and bad reviews.

Migration from legacy panels​

Moving dozens of sites from cPanel, Plesk, or bespoke scripts is a project, not a weekend chore. Inventory domains, certificates, mail dependencies, and cron jobs first. Use compare pages like vs cPanel to sanity-check feature gaps before promising parity to customers.

When to engage commercially​

If you need multi-tenant hardening reviews, custom RBAC, or white-label packaging, Contact with approximate customer count and regions served.