Infraforge

Server infrastructure with no model anywhere in it, and no claim that there is one. Across the pricing page, the calculator, the add on list and the questions section, everything described is deterministic: registering domains, writing authentication records, provisioning mailboxes on dedicated servers, allocating sending addresses, aggregating a mailbox view and maintaining the hosting. Nothing generates, scores, infers or recommends.

The removal test barely engages because there is nothing to remove, and no marketed claim exists that could fail it. The only signal pointing the other way is the address the product sits at and the family it belongs to, whose navigation promotes a separate agent product rather than any capability of this one. Graded in the middle of the band as the convention for a competent product making no such claim rather than as a penalty. A buyer wanting model driven work is looking at a different product in this family.

Provisioning automation with a stated spending bound and one route that widens it. Setup runs unattended: domains registered, authentication records written across them, mailboxes created on allocated servers. Nothing sends afterwards, because sending happens in whichever sequencing tool the customer connects, so there is no autonomous outreach to contain.

The commercial bound is the slot count and the vendor is 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. What widens the surface is that an application interface is included in every subscription rather than sold separately, so an automated client can provision mailboxes, and dedicated sending addresses are separately billable at a substantial monthly rate. Nothing published states what limits, approvals or role restrictions apply to programmatic provisioning. Ask what an automated client can create through the interface and who can authorise it.

No model layer exists to disclose and the machine facing surface that does exist belongs to this product rather than a sibling. Nothing on these pages describes generation, inference, scoring or routing, so no provider, family or version could be named and no explainability question arises. 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 running and that is not what was found.

The programmatic surface is named as this product's own interface and listed as included with every subscription, which is a clearer attribution than the sibling infrastructure product manages, though no reference document, specification or endpoint list was reached on either pass, so what it exposes is unestablished. Ask whether any automated decisioning applies to provisioning, throttling, suspension or address allocation, and if so on what basis it operates.

One well sourced testimonial, two thin ones, and no operating figure on a product sold on operational quality. The strongest is properly attributed, naming the individual, his current company and his previous senior role at a named research firm, and it is also the emptiest in substance: deliverability and impact described as unmatched, with no measurement behind the superlative.

The other two carry a first name, an initial and a job title with no employer, and one of the same partial names appears on a sibling product's page. A case study section and a deliverability section both exist. What is absent is the evidence this product is best placed to produce.

Dedicated servers and dedicated sending addresses generate delivery rates, placement rates, uptime figures and blacklist incidence as a matter of routine, and none of it is published for a product whose entire premise is that private infrastructure performs better. Ask for placement and delivery rates on dedicated addresses, with the period stated.

Authentication handled by default, volume published as figures, and a resale chain nobody accounts for. Every domain is configured automatically with the sender policy, signing and reporting records that receiving providers test against, and the vendor publishes recommended volume as numbers rather than as advice.

The dedicated architecture also improves the abuse position relative to a shared pool, because a sender's complaints land on their own addresses rather than on strangers' reputations. What is absent is any acceptable use position, anti spam policy or complaint threshold on any page reached.

That gap matters most in the white label programme, where an agency resells this infrastructure under its own brand: the party actually pressing send is the reseller's client, two steps from the operator, with no direct relationship and no reason to have seen any terms the operator sets. Ask what acceptable use terms bind an end sender reached through a reseller, and who is accountable when they are breached.

Own instruments published, over the deepest data position this vendor holds. Terms, a privacy policy and a data processing agreement each sit at this product's own addresses rather than being routed to a sibling, which is good hygiene. None was retrieved on this pass and none is characterised here either way.

What the product pages do establish is the extent of what is held: this is the mail host, so every outbound message and every reply written back by a prospect rests on infrastructure the vendor operates, meaning the personal data at stake includes correspondence from people who never chose this vendor.

One add on concentrates that further, offering a real time view of all mail across every account in a workspace from a single place, which is convenient for an agency and collapses the separation between client accounts into one surface. Ask how long hosted mail is retained, who can read it, and what access controls sit behind the unified view.

No corpus to license, and two origin questions the product raises directly. There is no contact database, no enrichment and nothing brokered, so the usual chain of sources and lawful bases does not apply. What does sit in scope is where the assets sold have been before.

Domains are sold at a per unit rate and nothing anywhere states whether they are freshly registered or previously used, which matters because a cold outreach buyer inherits whatever reputation a domain already carries and no amount of correct authentication repairs a poisoned one.

Sharper still is the pre warmed mailbox option, sold on the promise of sending from day one, where the value is precisely that a history already exists: nothing published states who generated that history, against which counterparties, over what period, or whether the mailbox has been held by anyone else before. Ask whether domains are newly registered and what history a pre warmed mailbox carries and who created it.

Nothing here runs on a platform belonging to someone else. There is no browser extension, no professional network automation, no third party account access and no borrowed interface: the vendor registers domains, operates dedicated servers, allocates its own sending addresses and hosts the mailboxes, so a customer's exposure runs to this vendor rather than through an intermediary who could withdraw permission at any time.

The dedicated model tightens that further than the shared pool sibling, because sending addresses are allocated to one customer rather than shared, so reputation consequences do not travel between unrelated parties. That architecture is what this axis rewards, and it separates this record from two products in the same family that sit at the floor for automating a professional network.

It stops below the top band because the mail still lands at the major receiving providers whose bulk sender requirements govern what arrives, and no conformance position of the vendor's own is stated anywhere against them.

Group level governance titles, and the largest stewardship question in this family left open. 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 entire disclosure. The question this product raises is simpler and bigger.

As the mail host it holds the full body of a customer's outbound correspondence and every reply written back, and the unified inbox option aggregates all of it across a workspace into one view. Nothing published states whether that content is read, scanned, analysed, aggregated across accounts, or used to improve anything, including the message generation sold by the sibling platform under the same ownership. Ask for a written commitment that hosted mail content is neither analysed nor used to train or tune any product in this family.

The product neither composes nor sends, and two of the things it sells bear on what a recipient can establish. Most of what this axis records cannot arise here: no message is written, no sender identity is invented and no outreach is initiated, since all of that happens in whichever sequencing tool the customer connects, so the grade sits in the middle of the band with that scope stated rather than at the floor. Two features are in scope.

Domain masking is sold as an add on at a published rate and the vendor describes its purpose as secure redirection that masks the domain so a customer can present a branded site without revealing their primary domain. And the white label programme means the infrastructure a message arrives from carries an agency's brand rather than the operator's. The vendor is open about both, and nothing addresses what a recipient can determine about who is actually contacting them. Ask what a recipient can discover about the registrant behind a masked domain.

An application interface named as this product's own and included in every subscription rather than gated or sold as an upgrade, which is unusual at this price point and is the clearest integration statement in this family. Around it the portability is architectural: the mailboxes are ordinary ones reached by standard credentials so they already work with any sequencing tool, and the vendor states domain control is identical to holding the domain at any other registrar including editing records directly.

The family also documents a command line tool and an interface for external assistant clients through which infrastructure can be provisioned programmatically. A white label programme and separate workspaces extend the surface for agencies running many client accounts.

It stops below the top band because no reference document, specification, endpoint list or authentication guide for the named interface was reached on either pass, so a buyer is told the interface is included without being able to see what it does before purchasing.

Single tenancy is the product rather than an enterprise upgrade, and it is priced openly. The vendor states that sending runs on dedicated servers rather than a shared pool, sells dedicated sending addresses as a per unit add on at a published monthly rate, and separates client accounts into distinct workspaces. That is a real isolation model a buyer can specify and cost before purchase, not a claim of privacy, and it is the strongest deployment position in this family by some distance.

It is held below the top band by a gap that is conspicuous given the positioning. Nowhere on any page reached is there a hosting country, a server region, a location for the dedicated addresses, a residency election or a cross border transfer mechanism, so a buyer can purchase private infrastructure holding their correspondence without establishing which jurisdiction it sits in. The shared trust portal lists fifteen named subprocessors with no statement of which products they cover. Ask where the dedicated servers and addresses are located, and whether a region can be chosen.

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 to the portal, so the vendor publishes the assertion on this surface, which is the distinction separating this from a subsidiary that claims 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, 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 reachable through a named request process.

Held below the top band because the portal publishes no documents at all, names no auditor, carries the point in time attestation rather than the period type, and states no scope identifying which products fall inside it. Note that the dedicated server model is graded as a deployment property rather than credited here. Ask for the report, its auditor and the product scope.

Five separately metered items each carry a published rate, and the annual claim survives arithmetic here where the sibling's does not. A live calculator converts sequence length, mailboxes per domain and monthly contact volume into the domains and slots actually required, with both billing frequencies shown together, and at the rendered default the yearly figure sits within a rounding of exactly two months off the quarterly one, so the discount described matches the discount offered.

Every add on is priced rather than described: dedicated sending addresses per address per month, the unified inbox per workspace at two frequencies, and domain masking per domain. The minimum purchase is stated openly and the vendor discloses against its own revenue that unused slots are still charged and that a buyer should size the order exactly. No contract, cancellation at any time and invoicing are all confirmed. Two things hold it below the top band.

The domain line reads as charged once and as an annual figure within the same block, so whether a recurring cost recurs is ambiguous. And the white label programme, a real purchase path, carries no figure at all.

Both assets a customer accumulates are genuinely theirs and the vendor says so plainly. Domains carry full control, stated as identical to holding them at any other registrar including direct record editing, so the sending reputation built on them travels with the customer rather than expiring with the subscription. Mailboxes are ordinary ones reached by standard credentials, so they already work with any sequencing tool and changing sending platform does not touch them.

An application interface is included, which gives a technical route to retrieve configuration. 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 thing the vendor actually holds.

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

The architecture puts reputation where the sender can control it, and the operating figures are published rather than described. Sending runs on dedicated servers with dedicated addresses available per unit, so a customer's reputation is not entangled with strangers' behaviour, which is the structural weakness of the shared alternative and is the strongest position available in this family.

Volume guidance is given as numbers, thirty messages per mailbox per day recommended with a hundred as the ceiling and two to three mailboxes per domain, and those figures drive the calculator so the quoted order reflects them. Authentication records are written automatically across every domain at setup. A dedicated deliverability section sits alongside, and pre warmed mailboxes are offered for senders who cannot wait out a ramp.

Held below the top band because the figures are recommended rather than enforced, which is the line the highest graded records in this lane cross, because no placement rate, delivery rate or blacklist incidence is published, and because the vendor's own guidance concedes this architecture suits only senders who keep to practice.

One segment is addressed concretely and everything around it is unstated. The agency and reseller motion is real rather than asserted: a white label programme has its own page and lets an agency resell the infrastructure under its own brand, separate workspaces keep client accounts apart, and the unified inbox is priced per workspace, which is a coherent set of features built for one identified buyer.

The commercial floor points the same way, with a ten slot minimum, a per mailbox rate above the shared sibling and sending addresses at a substantial monthly rate, describing a team running outbound at volume rather than an individual. Beyond that nothing is published.

No industry, company size, region or role is addressed on any page reached, no country is named for servers or sending addresses, and domain pricing is quoted for a single top level domain with no others listed or costed, so a buyer needing country specific domains cannot size the order. Ask which top level domains are available at what rates and in which countries infrastructure sits.