FOR MAIL THAT SHOULD COME FROM YOU
Send from your own mail. Keep your own record.
Point your workspace at your company's mail relay. The password stays in your own vault, your apps send through your relay, and each send can land in your own record.
New to OpenX? Key terms →
ONE SEND · YOUR INFRASTRUCTURE
- Relay
- Your company's own SMTP relay
- Password
- In your Key Vault, by reference
- Test
- Sign in to the relay first; a failure shows the reply code
- Record
- Each send in your Provenance, when it is on
- Rights
- Sending is its own right, held by workspace owners
Your relay. Your vault. Your record.
FROM RELAY TO RECORD
Mail your apps send, on the record.
Send through your own relay
Mail goes out through your company's SMTP relay, not a shared sender.
The password stays in your vault
It goes to the Key Vault in your own landing zone, which Communications needs. The workspace keeps only a reference.
Test before you trust it
Test signing in to the stored relay, and see the server's reply code if it fails. Then send yourself a test email.
Sends on the record
With Provenance on, each send that reaches the relay is written to your own hash-chained record, with a hash of the message and how many it went to, never the recipients' addresses, the subject or the body.
People hold the keys
Sending needs its own right, which owners hold. For an account a person has already connected, an AI can propose only its name, description and sender display name. The relay and its password are a person's steps.
Your apps and jobs send too
Apps and jobs on your workspace send through the same relay, and what a job sends carries its own identity.
IF YOUR DOMAIN IS NOT GOING TO A THIRD PARTY
For teams that send mail they have to stand behind.
IT teams
Keep your domain's mail on your own relay, and never paste its password into a SaaS form.
Quality and compliance teams
Show what was sent and when, from a record you hold, kept for as long as your Provenance retention says.
App builders on OpenX
Let your app send mail without wiring up a mail API and its keys.
NEXT TO MAIL AND NOTIFICATION SERVICES
Sending next to the data, not in another product.
Mail and notification services send well and keep their own logs, for as long as your plan allows. OpenX puts sending next to your data, identities, record and AI, so a reading, a correction or a subscription can lead to a send from the same workspace.
- Your own relay for sending, and your own record for what was sent.
- The same rights and AI-proposal model as every other capability.
- Send through the relay your IT team already runs and trusts.
WHERE A SEND STARTS
From an event to an inbox.
Your app sends the welcome mail
- 01A customer completes checkout for one of your plans.
- 02Your app sends the welcome mail through your relay.
- 03The send lands in your record.
AI-assisted, human-held
- 01A person connects the relay and its password, once.
- 02An agent connected over MCP proposes the sender display name and description.
- 03A person tests it before the first send.
Find it later
- 01Someone asks whether a notice went out, and when.
- 02You look in your own Provenance.
- 03The send is there, with its time and a hash of the message.
WHERE MAIL IS A RECORD
Sends that matter after they are sent.
LIFE SCIENCES
FDA's data-integrity guidance treats an email that authorises batch release as a CGMP record. Provenance records when each send happened, with a hash of the message; the message itself stays in your mail system.
MANUFACTURING
Shift and downtime notices sent through the plant's own relay.
BUILDINGS AND INDUSTRIAL
Notices to operators and tenants, sent from your own domain.
COMING NEXT
Sending is the start. Here is what follows.
COMING
Mailboxes
Connect a Microsoft 365 or Gmail mailbox directly.
COMING
Email Watch
A canvas node that reads incoming mail and turns it into data.
COMING
Communications Log
Who was sent what, which version they acknowledged, and who is out of date.
Your relay, your vault, your record.
Set up sending in the workspace your apps and data already live in.
MORE OF OPENX
AI governance →
Over MCP, AI proposes and a person accepts. Only a person deploys.
OpenX MCP Server →
A few tools let any MCP-capable AI read your workspace and propose changes to it.
API Manager →
Your workspace is already an API. Decide who may call it and what each caller reaches.
Warm queries →
Save a question over live data and serve the answer to dashboards, apps and AI.
Provenance →
A record you can prove, kept in your own cloud, with corrections and signatures.
Your cloud →
Connect your Azure, build the landing zone, and the rest of OpenX runs inside it.
Databases →
A Cosmos DB store in your subscription, with a governed API for each container.
App Identity →
Your own sign-in directory, identities for your jobs, and access in one window.
Licenses →
Sell what you build on your own Stripe, and turn a subscription into a plan's rights.
IoT →
IoT Hub and Data Explorer in your Azure, feeding queries, APIs and AI.
App building →
Data, sign-in, access, an API and billing: your app's backend, already there.