Infrastructure · required
Inboxy. The email infrastructure
every campaign sends through.
Inboxy provisions the domains and mailboxes, warms them against a live network, monitors reputation and rotates capacity before placement drops. EMY sends through it. It is the layer that makes email outreach possible at all.
- Owned domains and mailboxes
- Network warmup
- Reputation monitoring and rotation
- Inbox placement testing
Inboxy Infrastructure
Email infrastructure · No email leaves the engine without it.
Scrubby Inboxy Sending domains
12
Mailboxes
48 active
Inbox placement
98.4%
Owned by Vendisys · warmed against a live network · rotated before placement drops
24
years running email outbound on infrastructure we own
100k+
meetings booked through email
24
years operating email outbound, since 2002
Infrastructure
Email needs mailboxes with reputation. Inboxy builds and keeps them.
Cold email fails on the infrastructure side long before the copy matters: shared domains, cold mailboxes, no rotation. Inboxy is required for every email program because no email leaves the engine without it.
Owned domains and mailboxes
Vendisys registers and operates the sending domains and mailboxes a program uses. Nothing is rented from a shared pool, so no one else’s sending habits touch your reputation.
Network warmup
New mailboxes are warmed against a live network of real inboxes before they carry a single campaign email, and they keep warming in the background.
Reputation monitoring and rotation
Every mailbox is watched for placement and reputation. Capacity rotates out before placement drops, and rotates back in once it recovers.
Inbox placement testing
Seed-list placement tests run continuously, so a deliverability problem is caught on the infrastructure side instead of in your reply rate.
Agent
EMY · Email outreach
Email sequences, sent at scale through infrastructure we own.
EMY is the email sending agent. It runs personalised sequences to the contacts CAM and Scrubby hand it, paces every send across Inboxy mailboxes, stops on reply, and hands the conversation to Underfive.
-
Account research
Before writing, EMY researches the account: what changed, who joined, what the company is doing.
-
Signal-aware copy
The note references what actually happened. A competitor demo, a new hire, a funding round, not a template.
-
Sends through Inboxy
EMY never sends from a mailbox Inboxy has not warmed and verified. Deliverability is handled before the first word is written.
-
A/B at the sentence level
Variants are tested one sentence at a time, so the winning version is learned rather than guessed.
EMY To: VP Sales · Subject: the competitor call last week
Saw your team took a demo with Competitor A on Thursday. Most teams we talk to at that point are comparing catch-all coverage. We clear it without bounces.
Worth 15 minutes next week?
How it works
An email program, end to end.
- 01
Provision
Inboxy sets up owned domains and mailboxes for the program, with authentication configured and placement baselined.
- 02
Warm and verify
Mailboxes warm against the network. Scrubby verifies every address on the list, including catch-all domains, so nothing bounces.
- 03
Write and send
EMY researches each account, writes the note and sends it through a warmed Inboxy mailbox at a pace the mailbox can hold.
- 04
Reply
Replies land in Underfive, which classifies them, drafts the answer and books the meeting.
Email programs
Run by the team that builds the engine.
Vendisys email programs run on Inboxy and EMY, with Scrubby verifying the list and Underfive handling replies. The full program page is coming soon; the infrastructure has been in production for 2,200+ companies since 2002.
Inboxy and EMY run inside programs for teams at
And portfolio companies of
