Isolated sending stream for each project you run, test, or ship — own auth, specs, observability, and automation. Nothing shared with unrelated traffic.
Every message is DKIM-signed before it leaves. Motorical system mail uses KMS-encrypted keys; your own domains are signed from per-domain keys held in the database, with CNAME delegation so you never paste a key into DNS.
Continuous IP reputation and rate governance keeps your sending healthy automatically.
Adding Motorical to a domain that already sends via Google Workspace, M365, or another provider? We detect and merge with your existing SPF record instead of overwriting it.
Queue status, throughput, and delivery logs — not vanity metrics.
Spin up a sender for that project — SMTP credentials or an HTTP API key in seconds.
Pick password, API key, OAuth, or mTLS; verify SPF/DKIM with coexistence checks.
Logs, webhooks, and rates scoped to that Motor Block — then send via SMTP or HTTP.
What is a Motor Block?
A Motorical SMTP Motor Block is an isolated sending stream for one project (app, staging env, tenant, or experiment): its own domain, auth method, API keys, SMTP credentials, rates, logs, webhooks, and automation — so projects never share credentials or observability. Give each Motor Block its own sending domain and reputation stays separate too; blocks that share a domain share that domain's reputation.
Will this break my existing email setup?
No. If your domain's apex already has SPF from another provider (Google Workspace, M365, etc.), Motorical detects it and offers to merge rather than replace it.