This title slide features "Edison Mail – From Inbox to Intelligence" as the main heading. The subtitle reads "AI-Powered Email Evolution | Director of Engineering."

Edison Mail – From Inbox to Intelligence

AI-Powered Email Evolution | Director of Engineering

The product provides cross-platform clients for iOS, Android, Web, and Desktop, with a unified inbox featuring AI-powered insights, automation, bundles, fast search, and receipt extraction. It strategically evolves from an email client into an intelligence hub.

Product Overview & Strategic Purpose

• Cross-platform clients: iOS, Android, Web, Desktop
• Unified inbox with AI-powered insights and automation
• Core features: Bundles, fast search, receipt extraction
• Strategic evolution: From email client to intelligence hub

Source: Cross-platform clients & core features. Email client + AI-powered intelligence. Strategic goals for leadership review.

• Cross-platform clients on iOS, Android, Web, Desktop
• Unified inbox powered by AI insights
• Bundles threads, fast search, receipt extraction
• Smart Cards (SHIP) for flights, hotels, purchases
• Real-time notifications for instant updates
• E-Receipt streamlines revenue management

The slide presents a workflow for Edison Mail's architecture, starting from client apps initiating email sync, through middleware routing, core services for API/email handling, AI extraction via SHIP model for E-Receipts, and ending with push notifications. Key components include Edison Mail clients (iOS/Android/Web), Email Plan Service, OpenService/Email Service/MQ, Sift, and platform-specific push services like APS and GCM/FCM.

Architecture Overview

{ "headers": [ "Step", "Description", "Key Components" ], "rows": [ [ "Client", "User initiates email sync or action via app", "Edison Mail Clients (iOS/Android/Web)" ], [ "Middleware", "Routes requests based on email plans and user data", "Email Plan Service" ], [ "Core Services", "Handles API calls, email fetching, queuing", "OpenService, Email Service, MQ" ], [ "Extraction", "AI extracts structured data (SHIP model), generates E-Receipts", "Sift (SHIP model), E-Receipt" ], [ "Notifications", "Pushes updates to client (parallel pipeline)", "APS (iOS), GCM/FCM (Android)" ] ] }

Source: Edison Mail Architecture Flow

Prioritize Email Reliability

Unlock Scale & Revenue. Questions?

Middleware (Email Plan) Manages user preferences for personalized email experiences. Serves as the primary HTTP entry point for incoming requests. Forwards processing by calling OpenService to integrate additional services seamlessly.

OpenService Securely stores encrypted credentials for authentication. Maintains comprehensive SHIP data for operations. Provides developer APIs for custom integrations. Handles billing and subscription management efficiently.

Email Service Fetches emails from providers like Gmail, Outlook, Yahoo, and IMAP servers. It periodically polls inboxes for new messages and publishes them to a Message Queue (MQ) for downstream processing and delivery.

Notification Pipeline Leverages APNS for iOS and GCM/FCM for Android to deliver real-time push notifications. Enables instant alerts directly to user devices without polling, improving efficiency and user experience.

The slide "Scale Metrics & Reliability Challenges" showcases key growth statistics for the platform. It reports over 10M monthly active users with cross-platform engagement, 25M+ connected email accounts, and 50K daily net new accounts.

Scale Metrics & Reliability Challenges

• 10M+: Monthly Active Users

Cross-platform engagement

• 25M+: Connected Email Accounts

Total provisioned accounts

• 50K: Daily Account Growth

Net new accounts per day Source: Edison Mail Internal Analytics

• IP throttling by providers like Comcast.
• Redis dependency for connections and state.
• Manual sharding limits to 1M per shard.
• MQ backlogs accumulate in Redis and disk.
• Provider rate limits cause connection drops.

The roadmap timeline spans Days 1-30 for stabilization (reducing Redis dependency, automating sharding, improving IP throttling), Days 31-60 for scaling operations (enhancing metrics, optimizing notifications, boosting observability), and Days 61-90 for innovation (modernizing architecture, automation, AI features). Ongoing cross-org collaboration promotes partnerships between product and engineering for sustained growth and feedback.

Roadmap & Call to Action

Days 1-30: Stabilization Phase Address reliability challenges: reduce Redis dependency, automate sharding, improve IP throttling. Days 31-60: Scaling Operations Enhance scale metrics handling, optimize notification pipeline, boost observability tooling. Days 61-90: Innovation Acceleration Modernize architecture, implement automation, advance AI-powered intelligence features. Ongoing: Cross-Org Collaboration Foster partnerships across product and engineering for sustained growth and feedback.

Source: Edison Mail Engineering Roadmap