customer •

Pilot: self-hosted rollout

Deployment in-tenant with zero internet egress and private connectors.

By Howzer Team, Customer Success

Why self-hosted first

Some teams handle regulated customer data and need full control over processing. In this pilot we deployed Howzer entirely inside the customer’s tenant: private connectors, zero internet egress by default, and customer-managed keys.

  • No egress: processing stays in-tenant (VNet/VPC).
  • Private connectors: email, chat, ticketing run behind your network boundary.
  • Human-in-the-loop: approvals and audit built-in.
Tenant flow (pilot topology)
Sourcesemail · chat · ticketsConnectorsprivate / allow-listRedactPII at ingestAnalyzelikelihood × impactApprovehuman-in-the-loopRouteSLA / teamsSIEMaudit export

Architecture highlights

  • Identity: Microsoft Entra ID SSO (OIDC/SAML); SCIM user/group sync.
  • Data controls: field/entity-level PII redaction at ingest; retention windows.
  • Keys & secrets: customer-managed keys (e.g., Key Vault) and per-env secret rotation.
  • Networking: private subnets; outbound allow-listing; default zero internet egress.
  • Auditability: immutable logs for approvals, prompts/responses, policy changes.
The pilot mirrors production posture: if internet egress is required for a specific sub-processor, it is explicit and policy-gated.

Deployment steps

  • Day 0 – Security review & data-flow walkthrough.
  • Day 1 – Connect shared inbox + ticketing in private network; enable PII redaction.
  • Day 2 – Define approval paths and SLA routing; enable audit export to SIEM.
  • Day 3 – Golden set validation; go-live in a limited channel.

Early outcomes

In the first week the pilot surfaced high-risk items faster and reduced back-and-forth in approvals. Latency stayed within the target envelope under load. (Numbers below reflect pilot data, not public benchmarks.)

  • Throughput: steady with burst handling; queues remained p95-aware.
  • Response quality: fewer re-approvals due to guided playbooks.
  • Operations: clearer hand-offs via SLA routing and audit trails.

What’s next

  • Expand connectors (additional shared inboxes and ticketing projects).
  • Introduce evaluation golden sets for side-by-side comparisons.
  • Optional air-gapped mode for specific environments.
Set up a security review
← Back to updates