Mailforge

There is no model here and the vendor does not pretend otherwise. Across the pricing page, the calculator and both question sets, everything described is deterministic infrastructure work: registering domains, writing authentication records, provisioning mailboxes, hosting them and maintaining them. No generation, no scoring, no recommendation and no inference appears anywhere on this product's own surface.

The removal test does not really engage, because there is nothing to remove and the vendor makes no claim that would fail it. The only artificial intelligence signal attaching to this product is the family it belongs to and the address it sits at, and the navigation promotes a sibling agent product rather than any capability of this one. Graded in the middle of the band as a competent product that makes no such claim, which is the convention rather than a penalty. A buyer wanting model driven work is looking at a different product in this family.

Automation that provisions rather than acts, with the spending bound stated openly. What runs without a person is setup: domains are registered, authentication records are written across them and mailboxes are created, all in one pass. Nothing sends afterwards, because sending happens in whichever sequencing tool the customer connects, so there is no unattended outreach to contain.

The commercial bound is the slot count, and the vendor is unusually direct about how it behaves, stating that unused slots are still charged and advising a buyer to size the order exactly rather than leaving headroom. Domain purchases are explicit and one off.

The gap is the programmatic route: the family documents a command line tool and a machine interface for assistant clients through which mailboxes can be provisioned, which means an automated client can create billable sending capacity, and nothing published states what limits or role restrictions apply there. Ask what an automated client can provision and who can authorise it.

No model layer exists to disclose, and the machine facing surface that does exist is documented elsewhere. Nothing on this product's pages describes generation, inference, scoring or routing, so there is no provider, family or version that could be named and no explainability question a buyer could put. Graded in the middle of the band with the scope stated rather than at the floor, because the floor asserts that an undisclosed model is operating and that is not what was found here.

The one adjacent disclosure is the programmatic surface: the family publishes a command line tool and an interface for external assistant clients through which this product's mailboxes can be provisioned and managed, and that documentation is precise about what it does while sitting under the sibling platform's name rather than this one. Ask whether any automated decisioning applies to mailbox provisioning, throttling or suspension, and if so on what basis.

Well attributed testimony and no operating metric, on a product whose entire value is operational. The testimonials are properly sourced, three of them carrying a full name, a job title and a named employer, which is better attribution than most records in this category manage, and a case study section sits alongside them.

The numbers inside them belong to the customers rather than the vendor: a claim of roughly three times lower cost per mailbox than a mainstream provider and a description of hundredfold improvement in setup time are both quoted testimony, published without sample, method or period. What is absent is the category of evidence this product should find easiest.

It hosts mailboxes and sends mail, so delivery rate, inbox placement rate, uptime, blacklist incidence and mailbox failure rate are all measurable by the vendor as a matter of routine, and none of them is published. Ask for delivery and placement rates across the shared pool, and the uptime record for mailbox hosting.

Authentication is handled properly and the abuse question is left where it will hurt other customers. On the good side, every domain is configured automatically with the sender authentication records that receiving providers require, which is the single most consequential compliance control at the infrastructure layer, and the vendor publishes volume guidance as actual figures rather than advice.

Set against that, nothing reached states an acceptable use position, an anti spam policy, a complaint threshold, or what the vendor does when a customer's mailboxes generate abuse reports. That matters more here than on a dedicated infrastructure product because this is a shared pool, and it is sharpened by the vendor's own guidance: a buyer who anticipates a high volume of spam complaints is steered towards this product rather than the dedicated sibling, which places the highest complaint senders in the pool everyone else shares. Ask for the acceptable use policy, the complaint threshold, and what happens to your sending when another pool member breaches it.

Three instruments published at this product's own addresses, governing the deepest data position in this family. Terms, a privacy policy and a data processing agreement each sit on this domain rather than being routed to a sibling, which is good link hygiene. None was retrieved on this pass and none is characterised here either way. What is established from the product pages is what the vendor holds, and it is a great deal.

This is the mail host: every message a customer sends and every reply a prospect writes back passes through and rests on infrastructure the vendor operates, so the personal data at stake includes the correspondence of people who have no relationship with the vendor and never chose it. Nothing on the pages reached addresses how long hosted mail is retained, whether it is scanned, who can access it, or what happens to it after an account closes. Ask for the retention period on hosted mail content and the access controls over it.

No corpus to license, and one provenance question that matters more than it first appears. There is no contact database here, no enrichment and nothing brokered, so the usual chain of sources, licences and lawful bases does not apply and the axis is largely out of scope. What does sit in scope is the provenance of the domains themselves.

A cold outreach buyer inherits whatever reputation a domain already carries, and a previously registered domain with a history of abuse arrives poisoned in a way no amount of correct authentication will repair. The pricing page sells domains at a per unit rate and the questions section covers registration, control and cost, and nothing anywhere states whether the domains sold are newly registered or previously used, or whether any reputation screening is performed before one is handed over. Ask whether domains sold are freshly registered, and what history checking is done before a domain is allocated.

The one product in this family that operates on nobody else's platform. There is no browser extension, no professional network automation, no third party account access and no borrowed interface: the vendor registers domains, runs its own sending infrastructure and hosts the mailboxes itself, so the customer's exposure is to the vendor rather than to an intermediary who could withdraw permission.

That architecture is what this axis rewards and it is a genuine distinction from the sibling products, two of which sit at the floor of this axis for automating a professional network. What remains is real but different in kind: the mail lands at the major receiving providers, whose bulk sender requirements govern what arrives, and the shared pool means those providers judge a customer's sending partly on other customers' behaviour.

It stops below the top band because no conformance position of the vendor's own is stated anywhere against those requirements, so the grade rests on architecture rather than on a documented commitment.

Governance titles published at group level, and the stewardship question this product raises is the largest in the family and goes unanswered. The shared trust portal names a set of controls addressing artificial intelligence governance, covering awareness, change planning, communication, competence, concern reporting and continual improvement, and reports no documents behind any of them, so the titles are the whole disclosure.

The question that matters here is simpler than artificial intelligence and larger in scope. This vendor hosts the mailboxes, which means it holds the full body of a customer's outbound messages and every reply written back by people who are not its customers. Nothing published states whether that content is read, scanned, analysed, aggregated across accounts or used to improve anything, including the copy generation sold by the sibling platform. Ask for a written commitment that hosted mail content is neither analysed nor used to train or tune anything.

The product neither writes nor sends, and one paid feature sits squarely in this axis anyway. Most of what this axis records cannot arise here: no message is composed, no sender identity is invented and no outreach is initiated, because all of that happens in whichever sequencing tool the customer connects, so the grade is set in the middle of the band with that scope stated rather than at the floor. The exception is sold as an add on at a published price.

Domain masking is described by the vendor as secure redirection that masks the domain so a customer can display a branded site without revealing their primary domain, which means the stated purpose of a paid feature is to prevent a recipient establishing which domain is actually contacting them. The vendor is open about what it does, and nothing addresses what a recipient can determine about who is behind the approach. Ask what a recipient sees when a masked domain is used, and whether the underlying registrant is discoverable.

Integration by standard protocol rather than by proprietary connector, which for infrastructure is the stronger form. The mailboxes are ordinary ones that connect to any sequencing tool with the usual credentials, so a buyer is not choosing a sending platform when they choose this, and the vendor states that domain control is identical to holding the domain at any other registrar, including editing records directly. That is real portability rather than a claim of openness.

Alongside it the family documents a command line tool and an interface for external assistant clients through which mailboxes can be provisioned and managed programmatically, which is a genuine automation surface and rare in this category, and one click connection into the sibling sending platform.

It stops below the top band because the programmatic routes are documented under the sibling platform's name rather than this product's, so what they expose for infrastructure specifically is unestablished, and no marketplace listing exists under this product's own name.

The architecture is described and its geography is entirely absent. What the vendor does state is the shape: a shared pool with customer mailboxes distributed across sending addresses used by many other businesses, compared by the vendor to how the mainstream mail platforms operate, with a dedicated server alternative sold as a separate product. That is a clear architectural disclosure and more than many infrastructure vendors give. What is missing is every question of location.

No hosting region, no sending address geography, no mailbox storage location, no residency election and no cross border transfer mechanism appears anywhere reached, and this product's own privacy policy was not retrieved on this pass so nothing is attributed to it either way. For a product that stores business correspondence, where it rests is a first order question.

The shared trust portal publishes a subprocessor list of fifteen named third parties with no statement of which products it covers. Ask where mailboxes are hosted and where sending addresses are located.

A live trust portal with current certifications, claimed on this product's own pages rather than inferred from a corporate relative. Two badges sit in this product's footer and link out to the portal, so the vendor publishes the assertion on this surface, which is the distinction that decides the grade against a subsidiary claiming nothing of its own.

The portal is substantive: two current certifications, a service organization control attestation of the first type and a cloud application security assessment at the second tier, held across three frameworks, with twenty five policies named by domain covering access control and least privilege, change and release management, risk management, remote access, physical security and data subject rights, more than a hundred and thirty controls described as continuously monitored, and a security questionnaire available through a named request route.

Held below the top band because the portal publishes no documents at all, names no auditor, and carries the point in time attestation rather than the period type, with no scope statement identifying which products it covers. Ask for the report, its auditor and the product scope.

A buyer can size and cost the whole order before speaking to anyone, and the vendor volunteers the part that usually costs people money. A live calculator converts sequence length, mailboxes per domain and monthly contact volume into the domains and mailbox slots actually required, with per unit prices attached to each and both billing frequencies shown side by side.

The minimum purchase is stated openly rather than discovered at checkout, the add on carries a published rate, a consulting engagement is priced at a stated figure, and the vendor confirms no contract, cancellation at any time and invoicing. The disclosure that stands out runs against the vendor's own revenue: it states that unused mailbox slots are still charged and tells a buyer to size the order exactly to avoid paying for capacity they will not use.

Held below the top band on arithmetic. The questions section describes the annual discount as two months free while the calculator's own default figures compute a fifth off, an error in the buyer's favour but still the page disagreeing with itself, and the domain line reads as charged once and as an annual figure in the same block.

The two assets a customer builds here are both genuinely theirs, and the vendor says so in plain terms. On domains it states that a customer has full control, the same as if the domain had been purchased from another registrar, including editing records directly, so the domains are owned rather than rented and the reputation built on them travels.

On mailboxes the portability is architectural rather than promised: these are ordinary mailboxes reached by standard credentials, so they already work with any sending tool and moving sequencing platforms does not touch them. Around that sit no contract, cancellation at any time, and slots that allow mailboxes to be deleted and recreated freely. It stops below the top band on the one thing the vendor actually holds.

Nothing published describes exporting hosted mail content, and nothing states what happens to stored correspondence after cancellation or how long a departing customer has to retrieve it. Ask for the mail export route and the retention window after an account closes.

Sending discipline published as numbers rather than as advice, on the product where it decides everything. The vendor states a recommended ceiling of thirty messages per mailbox per day with a maximum of one hundred, and two to three mailboxes per domain, and builds those figures into the calculator so the quoted order reflects them.

Authentication is handled by default across every domain, with the sender policy, signing and reporting records written automatically at setup, which is the control receiving providers actually test against. A dedicated deliverability section sits alongside, and the architecture is disclosed honestly as a shared pool rather than dressed up.

The comparative guidance against the dedicated sibling is candid to the point of being commercially awkward, telling a buyer that neither is inherently better and that high complaint senders belong here. Held below the top band because those figures are recommended rather than enforced, which is the line the highest graded records in this lane cross, and because no delivery rate, placement rate or blacklist incidence is published for the pool.

The floor of the commercial model defines the buyer more clearly than any positioning page would. A minimum of ten mailbox slots, a calculator built to size hundreds of domains and a per mailbox cost argued against the mainstream mail platforms together describe a team running outbound at volume, not an individual and not a company sending occasionally. That is a coherent and honestly signalled segment. What is not published is everything around it.

No industry, region, company size or role is addressed anywhere reached, there are no segment pages of the kind most vendors carry, and the only geography implied is that a sibling product is positioned as offering addresses in one particular country, which says nothing about this one. Domain pricing is quoted for a single top level domain with no list of others or their rates, so a buyer needing country specific domains cannot cost the order. Ask which top level domains are available, at what prices, and in which countries sending addresses sit.