Frequently asked questions

No. Infrabox holds a pool of Google Workspace accounts. Your domain is added to one of them as a secondary domain, and your mailboxes are created inside it. You never see a Workspace signup form, never get a Workspace bill, and never hold the admin password — the platform holds it so the provisioning steps can run without you.

The practical consequence worth understanding: your mailboxes live in an account Infrabox controls, not one you control. That is what makes unattended provisioning possible, and it is also the honest reason the “what if I leave” question below has the answer it does.

Yes. You can connect a domain you already own rather than buying a new one. The requirement is that its DNS be pointed at the zone Infrabox manages, because every step after that — MX, SPF, DMARC, the Google verification token, the DKIM key — works by writing records into that zone. A domain whose DNS you want to keep elsewhere is not a good fit for this.

Two line items. $3.79 per Google Workspace mailbox per month, and the domain registration, which is priced per TLD. There is no separate provisioning fee, no onboarding fee and no per-record DNS billing. The breakdown, including how domain pricing varies with the age of the domain, is on the pricing page.

Roughly 7 hours end to end in the typical case. That is an estimate, not a promise, and it is dominated by one step: waiting for Google to confirm it can see the domain-verification record.

That wait is paced by DNS propagation and by Google’s own checking schedule. Nobody — not Infrabox, not you, not a support ticket — makes it go faster. The per-step breakdown is on how it works, and the dashboard shows the same numbers live while a mailbox provisions.

The pipeline distinguishes two kinds of failure, and the distinction is the useful part. A transient failure — Google rate-limiting, a network timeout, a slow propagation — retries on its own. A permanent failure marks the mailbox failed and stops, rather than pushing on into a half-configured state that looks alive and cannot send.

What happens next is the part worth being straight about: there is no automatic replacement, refund or credit today. A permanently failed mailbox is re-run by an operator. The intended commitment — free replacement of a non-functional mailbox within a defined window — is drafted in section 6 of the deliverability SLA, which is written for a tier Infrabox does not currently sell.

DKIM is the one step that still depends on driving Google’s Admin Console rather than calling an API, because Google exposes no API for it. It is therefore the step most likely to need attention.

A mailbox without DKIM can still send. What it loses is a signing identity: DMARC then has only SPF to align against, and SPF does not survive forwarding. That is a description of what breaks, not a percentage — see the authentication guide for what each record actually proves.

Google can suspend a mailbox, or an entire Workspace account, for its own reasons and on its own schedule. There is no appeal process Infrabox controls and no vendor can promise you otherwise.

What the platform does do is check account standing before configuring anything, so a suspended account fails at the start of the pipeline rather than five steps in. Workspace accounts in the pool are also deliberately kept well below Google’s ceiling on domains per account, so that a suspension affects a bounded set of domains rather than everything at once.

Yes. The Terms of Service, Privacy Policy, Refund Policy and Acceptable Use Policy are published, and each is written from how the system actually behaves rather than from a template — including the parts that are awkward to admit, like administrative access to mailboxes and the fact that transfer-out is not built. A deliverability SLA also exists, but it describes a Guaranteed Placement tier that is not currently sold, and says so.

The legal index lists all five with their status. If something in there needs settling before you can buy, say so on the get started page.