Public demo

The product, surface by surface.

Three real screens from aubosmail.com/dashboard. Captured from production (not mocks). To use any of them with your own account, claim a free address at aubosmail.com/signup.

Claim a free address →See a sample proof page
1 · The composer
/dashboard/composer
Try it →
aubosmail.com/dashboard/composer
AUBOSmail The composer — production screenshot

Drag-drop block editor. 36 block types across Hero, Editorial, Layout, and Cinematic groups. Theme tokens at the document level (palette, fonts, spacing). Live three-pane preview shows the inbox card, the rendered web reader, the plaintext fallback, and the canonical JSON — simultaneously, as you edit.

  • ·Subject + preheader inputs with merge-tag autocomplete ({{first_name}}, {{company}})
  • ·Block palette: Gradient hero, Split section, Stat grid, Pull quote, CTA band, Feature grid, Signature, Full-bleed image, Scroll video, Parallax layers, Pinned section, Marquee strip, Reveal text, Timeline, and 22 more
  • ·Save-as-template flow saves the current document as a reusable theme + block tree
  • ·Raw-HTML fallback mode for when you want full control
2 · Tenant settings
/dashboard/settings
Try it →
aubosmail.com/dashboard/settings
AUBOSmail Tenant settings — production screenshot

Per-tenant workspace settings. Account profile, role (owner / member), opaque tenant ID for API calls, and active-session list across devices with revoke-anywhere. Multi-tenant isolation is enforced by Supabase row-level security on every read.

  • ·Account: email, phone, display name, role
  • ·Tenant ID surfaced for API integrations and support
  • ·Active sessions table with IP, last-seen, user-agent, revoke-anywhere
  • ·Audit log of session creation + revocation (visible to owners)
3 · Outreach campaigns
/dashboard/outreach
Try it →
aubosmail.com/dashboard/outreach
AUBOSmail Outreach campaigns — production screenshot

Sequenced cold email with jurisdiction-aware compliance. Sender domain must be verified (DKIM, SPF, DMARC auto-checked) before a campaign can launch. Each step in a sequence runs through a compliance gate — CAN-SPAM, CASL, GDPR — at send time, not at audit time.

  • ·Campaigns require verified sender domain (DKIM / SPF / DMARC)
  • ·Sequence steps with delay (days), step ordering, conditional sends
  • ·Recipient import (CSV / API), de-dup, list hygiene, suppression sync
  • ·Jurisdiction-aware compliance gating at send time

Proof chain — verifiable in your browser.

Every send produces a public proof page anyone can verify without trusting AUBOSmail. Five cryptographic layers: canonical JSON, content hash, DKIM signature, WORM storage, and a daily Merkle root anchored to Bitcoin via OpenTimestamps.

Open sample proof page →How proof works