Feature 01 / 04
Use case
Support every customer like they're your only customer
Managed service providers run hundreds of customers on one Helpdash. Each customer gets a workspace; each workspace has its own brand, SLAs, audit log, and exportable archive.
Outcomes
What MSPs trade up for
MSPs running Helpdash report audit-log requests resolved in minutes, not days — and zero cross-tenant data incidents in 18 months of production.
Feature 02 / 04
Tamper-evident audit log per workspace, exportable to any SIEM
Feature 03 / 04
Workspace-scoped storage so customer attachments never co-mingle
Feature 04 / 04
Reseller-friendly billing
aggregate invoices, per-workspace charge-back
Inside the isolation model
Multi-tenant, but every tenant feels like single-tenant
Feature 01 / 03
Query-layer scope
Every query is bound to a workspace boundary at the data layer. Cross-tenant queries fail loudly.
Feature 02 / 03
Per-workspace audit
Every change is signed and survives workspace deletion. Export to your SIEM hourly, daily, or on demand.
Feature 03 / 03
Scoped storage
Each workspace gets its own filesystem prefix and signed download URLs. No bucket shared across customers.
FAQ
Frequently asked questions
Can I move a customer to dedicated tenancy later?
Yes. Enterprise customers can graduate a workspace to a dedicated database, region, or even a customer-supplied VPC. Migration is online — no downtime.
How do you handle data-residency requests?
Workspaces pick their region at creation (EU, UK, US). Dedicated tenancy adds region-locked storage and a contractual residency guarantee.
What's your stance on subprocessors?
Published list, change notifications via email, and a 30-day notice window before any new subprocessor is added. The list lives at helpdash.io/legal/subprocessors.
Onboard your first customer in an afternoon
Helpdash workspaces stand up in minutes. Talk to sales about reseller pricing and migration support.