---
title: About SendHQ — Email infrastructure for products and agents
description: SendHQ brings verified sending domains, inbound addresses, hosted templates, delivery events, and workspace-scoped API access into one email platform.
canonical: https://sendhq.cc/about
last-updated: 2026-08-26
---
# One place for everything that *emails.*

SendHQ gives products, services, and AI agents a shared email foundation without collapsing their domains, identities, inboxes, or delivery history into one tangled integration.

01 / IDENTITY

## Verified senders stay explicit.

Each workspace owns its domains and sending identities. SendHQ checks ownership before outbound mail reaches the provider.

02 / CONVERSATION

## Outbound and inbound belong together.

Named inboxes, retained messages, attachments, and thread metadata keep replies connected to the workflow that started them.

03 / OUTCOME

## Delivery state is evidence, not a promise.

Events, bounces, complaints, and suppressions are recorded separately. SendHQ does not turn provider acceptance into an inbox-placement claim.

## Why it exists.

Email infrastructure tends to spread as a company grows: one provider for a product, another domain for an internal service, an agent with its own credentials, and a separate tool for receiving replies. SendHQ is designed to keep those pieces visible and governed inside one workspace.

The platform exposes a versioned, [machine-readable API contract](https://sendhq.cc/openapi.json) alongside a web dashboard. It supports verified domains, expected outbound email, inbound addresses, hosted templates, private attachments, delivery events, suppressions, and scoped API keys.

SendHQ is built by [Vynara (formerly Wavicle Technologies)](https://www.vynaratechnologies.com/). Questions about a workflow, integration, domain, billing, security, or deliverability can be sent through the [contact page](https://sendhq.cc/contact.md).

**Build the next email workflow on a contract you can inspect.**