Skip to content
← All work

HiTek product (pre-launch)

Every AI agent gets an inbox. People stay in control.

Give every AI agent its own inbox, with configurable human approval controls

AIInfrastructureEmail
TekMail fleet overview showing agent health, mail volume, review needs, and recent activity
Industry
AI infrastructure
Relationship
HiTek product (pre-launch)
Current state
Deployed and hardening — public launch in preparation

TekMail is one of our own products — a piece of infrastructure we built and operate, not a client engagement. It is deployed and being hardened ahead of its public launch. Product screens are shown with sample data.

The situation

What was getting in the way.

As AI agents start taking real actions, they need to send and receive email like a teammate would. But handing an autonomous agent an inbox with no oversight is risky — you need provisioning, deliverability, and a human in the loop before anything goes out.

  • —AI agents need real email addresses to act on the world
  • —Letting an agent send unsupervised email is risky
  • —Deliverability (SPF/DKIM/DMARC) is hard to get right
  • —No clean way to provision and govern email per agent

What HiTek changed

A system people can rely on.

TekMail gives each agent its own email address over REST and hosted MCP, with scoped credentials, approval workflows that can hold outgoing mail for review, authenticated sending domains, custom-domain support, and per-agent rate limits and allowlists — so teams can govern how agents communicate.

  • ✓Per-agent email addresses provisioned over REST and hosted MCP
  • ✓Human-in-the-loop approval and hold-before-send with undo
  • ✓Authenticated delivery with SPF, DKIM, and DMARC
  • ✓Custom domains, per-agent rate limits, and allowlists
  • ✓Quarantine, content policies, and violation tracking
  • ✓Activity dashboard with bounce and spam tracking

The message journey

The boundary lives outside the model.

Prompts can guide behavior. They cannot be the final enforcement layer. TekMail makes identity, permissions, review, and delivery durable parts of the mail system itself.

  1. 01

    Identity

    Provision an address and revocable credentials for one agent.

  2. 02

    Connection

    Use the REST API or hosted MCP from the runtime doing the work.

  3. 03

    Policy

    Apply permissions, rate limits, allowlists, and content controls outside the model.

  4. 04

    Decision

    Deliver, hold, quarantine, or route the message to a person for review.

TekMail approval queue with agent messages waiting for human review
The approval queue makes consequential mail visible before it leaves the system. Reviewers can inspect the message and its risk signals, then approve, release, or reject it. Screens show sample data.
TekMail agent inbox showing message context and injection-risk signals
Risk signals stay attached to the message where a person can act on them.

A product, not a demo

The unglamorous infrastructure is the product.

The visible workflow sits on top of tenant isolation, authenticated domains, suppression handling, idempotent delivery, scoped keys, auditable events, and operational tooling. That is what turns an impressive agent demo into something a team can actually operate.

Visit TekMail.app Why we built it

Before / after

The change in plain language.

Agent identity
BeforeA borrowed human inbox or a shared transactional account
AfterA dedicated address and revocable credentials for each agent
Safety boundary
BeforeBehavioral instructions that depend on the model complying
AfterPermissions and policy enforced by the mail infrastructure
Human review
BeforeScattered across logs, drafts, and provider dashboards
AfterOne approval queue with message context and risk signals
Changing runtimes
BeforeReconnect or recreate the mailbox for every agent client
AfterKeep the identity, rules, and history while the client changes

What matters

Policy-controlled

Approval and sending rules are set per use case

Own inbox

Each provisioned agent gets its own email address

Authenticated

SPF, DKIM, and DMARC support trustworthy delivery

Deployed

Built and hardening ahead of public launch

The work in context

Screens with a reason to exist.

TekMail agents screen showing separate inbox identities, volume, and approval modes
Every agent has its own address, credentials, history, and approval posture.
TekMail activity stream showing delivered, pending, and quarantined messages
A single operational timeline makes outcomes across the fleet inspectable.
TekMail policy list with block, approval, auto-delivery, and quarantine actions
Policy decisions are explicit and enforced before mail reaches an agent or recipient.
Technology and platformsNext.jsReactHonoPostgreSQLDrizzleBetter AuthStripeAWS S3

Bring us the problem that does not fit neatly in a service box.

Start a conversation
BevBridge →