Provider control plane
Static mockup of how volume could be watched by inbox provider.
Gmail
41%
volume
99.3%
accepted
0.4%
deferred
Microsoft
22%
volume
98.9%
accepted
0.7%
deferred
Yahoo
11%
volume
99.1%
accepted
0.5%
deferred
Apple
9%
volume
99.4%
accepted
0.3%
deferred
Other
17%
volume
98.7%
accepted
0.8%
deferred
180K/s
Emails sent per second
Peak throughput placeholder
1.4s
Median time to inbox
Measured from accept to inbox
99.2%
Inbox placement
Average placement placeholder
99.99%
Platform uptime
Rolling 90-day placeholder
The pipeline
Four stages. Milliseconds apart.
Ahrefs talks about crawling and processing the web. Bento's version is the path from event capture to inbox placement.
<200ms
API accept latency
API, SMTP, form, and event traffic lands in the same intake layer before it is normalized and queued.
2.1M/s
Events processed
Behavioral events, profile changes, suppression checks, and automation triggers move through one pipeline.
47ms
Median webhook latency
Provider-aware routing, batching, and reputation checks decide how each message should leave Bento.
1.4s
Median time to inbox
Campaigns, automations, and transactional emails share the same delivery mesh and feedback loops.
Throughput and scale
The numbers operators ask for first.
One section for the metrics you will replace later: send rate, event volume, contact graph size, region coverage, and suppression speed.
Emails delivered per month
9.2B
Marketing, automation, and transactional sends on one delivery layer.
Peak hourly capacity
650M/hr
Room for launches, seasonal sends, and transactional spikes.
Lifetime events stored
1.3T
Delivery and behavior data available for segmentation and automation.
Active contacts managed
640M
Profiles, custom fields, and consent status in one customer graph.
Sending regions
12
Regional routing and redundancy for high-volume senders.
Suppression handling
<200ms
Bounces, complaints, and unsubscribes are processed before the next send.
Delivery mesh
Tuned for time to inbox.
Campaigns, automations, and API sends share queue workers, provider lanes, and reputation signals. The product view beside this copy is real Bento UI reused as proof, not a stock server graphic.
Inbox timing
Fast sends are only useful when they arrive.
The mock panel tracks time-to-inbox percentiles by send type, which is more useful than a single vanity throughput number.
Time to inbox
Percentile placeholders by send type. Real numbers can replace this data set without changing the layout.
Transactional
p50 0.9s · p95 3.8s · p99 7.2s
Automation
p50 1.3s · p95 5.1s · p99 8.4s
Broadcast
p50 1.8s · p95 6.4s · p99 11.6s
Authentication checks
SPF, DKIM, and DMARC setup is verified before serious volume goes out.
100%
Plans with auth guidance
Reputation monitoring
Blocklists, complaint rates, and provider feedback are watched continuously.
24/7
Reputation coverage
Provider-aware batching
Bento adjusts volume so Gmail, Microsoft, Yahoo, and Apple are not treated like one inbox.
5
Provider lanes shown
List hygiene
Bad addresses are caught and suppressed before they keep hurting your reputation.
$0
Included infrastructure
What it means
Scale only matters when it helps the send.
This section translates infrastructure into outcomes instead of leaving the page as a wall of hardware-adjacent stats.
Launch without babysitting queues
High-volume broadcasts can be batched and watched without stitching together a separate sending vendor.
Keep product email close to marketing data
Password resets, receipts, campaigns, and lifecycle automations can all update the same customer profile.
React to delivery feedback quickly
Bounces, complaints, unsubscribes, and webhook events feed suppression and automation logic in near real time.
Infrastructure questions
Are these numbers final?+
Why make infrastructure a top-level page?+
Does this replace the deliverability page?+
Can Bento handle transactional and marketing email together?+
Built to send at any scale.
Use Bento for product, marketing, and transactional email with deliverability controls built in.
Delivery status
Healthy
1.4s
Time to inbox
180K/s
Peak send rate