Get started
Two things from you. Eight steps from us.
Getting started means handing over a domain and telling us which tool you send with. Everything after that — the Workspace order, the admin account, MX, SPF and DMARC, Google's ownership check, DKIM and a sending credential — runs without you in the loop.
This page is the whole shape of it: what to have ready, what runs, what you hold at the end, what it costs, and what happens on the one step that is genuinely slow.
At a glance
hello@infrabox.io
01before you begin
What you need
Have these ready.
Nothing else is required up front. There is no Workspace signup form to fill in and no Admin Console to learn — the admin account is created and held on the platform side so the rest can run unattended.
A domain to send from
The tool you already send with
A rough mailbox count
02what runs
The pipeline
The eight steps, and how long each usually takes.
These are the same steps and the same typical durations the provisioning screen shows while it works. They run in this order, and each has to finish before the next begins.
- 01~15 min
Workspace order
The Workspace order for your domain is placed and confirmed.
- 02~15 min
Admin account
The admin account that owns this domain's mailboxes is created.
- 03~30 min
Activation
Google confirms the new account is live and in good standing.
- 04~20 min
Workspace & DNS
MX, SPF and DMARC records are published for the domain.
- 05~5 hr
Domain verification
Google is asked to confirm you own the domain. Google sets the pace here.
- 06~30 min
DKIM signing
A DKIM key is generated, published to DNS and switched on.
- 07~20 min
Sending credential
A working sending credential is minted and verified against Gmail.
- 08~5 min
Renewal
The renewal schedule is set so the mailbox keeps running.
03what you get
At the end
Working mailboxes, and a credential that has been tested.
Not a provisioning ticket and not a checklist. The credential step calls Google with the credential rather than issuing it and hoping, so a mailbox that is marked ready has already been proved against Google.
Google Workspace mailboxes on your domain
Real Workspace accounts, not forwarders or aliases. Your domain is attached as a secondary domain on a Workspace, and the mailboxes live on it.
An SMTP credential verified against Google
Minted for the mailbox and checked by actually calling Google with it. There is no app password to store and no 2-step verification prompt to work around.
Authentication already published
MX, SPF and DMARC written with the values Google expects, and a DKIM key generated, published to DNS and switched on for the domain. What those records do.
A renewal schedule
The final step puts the mailbox on its renewal schedule, so it does not quietly lapse in the middle of a campaign.
04connect it
Your sequencer
Point the tool you already use at the relay.
Mailboxes are reached over one SMTP relay, so a sending tool is set up the way it always is — host, port, username, password — and the relay hands the message to Google.
Relay settings
- Set the tool's From address to the mailbox address exactly — Google refuses a mismatch, and that is not something the relay can paper over.
- The daily cap runs from midnight UTC to midnight UTC, and only successful sends count against it.
- Transient failures come back as 4xx on purpose, so your tool retries a mailbox instead of writing the address off as dead.
- Nothing changes in the campaign itself — only the sending account it points at.
05what it costs
Pricing
Two line items.
A monthly price per mailbox, and the domain once a year if we register it for you. Checkout quotes the final domain price, because the registrar's own price is what it is built on.
Mailboxes
$3.79per mailbox / month
Charged per mailbox, however many domains they are spread across.
Domains, if we register them
from $8.00per year, by TLD
Registration is priced per TLD — .shop is the cheapest at $2.00 — plus a flat $6.00 markup, or $10.00 on a domain already 12+ months old. Bring your own domain and this line is zero.
06when it is slow
Waiting and failure
One step waits on Google. It keeps asking rather than giving up.
Domain verification is the long pole, and slowness there is normal rather than a symptom of something broken. Nameserver delegation and DNS propagation are outside anyone's control, so that step is built to retry for hours.
What you will see
The pipeline sits on domain verification while it waits. The steps behind it stay done, nothing is rolled back, and the steps after it pick up the moment Google confirms.
If something genuinely fails
An unfulfillable order is caught by the first step in a second, rather than halfway through a Google setup. Anything that stops later is ours to chase — email us and we will tell you which step it is on and what it is waiting for.
Before you commit
How it works walks through each of the 8 steps in full, deliverability covers what the published records actually do and where we stop making claims, and the FAQ is where the "not yet" answers live.
Next step
Tell us the domain and the mailbox count.
One email is enough to start: the domain you want to send from or would like registered, roughly how many mailboxes, and the tool you send with. We come back with the real total and what the pipeline will be waiting on.