Corporatelive motion
R
Morgan ValeVP, Client TrustNorthstar Advisory
Server-side email signatures
Email signatures, applied in transit.
Every message your people send — from Outlook, Gmail, a phone, a shared mailbox — leaves with the right signature. Nothing installed, nothing to paste, and your mail platform still does the delivering.
Microsoft 365, Google Workspace, or any SMTP platform. Connected by one administrator in about twenty minutes — Microsoft guide, Google guide, generic SMTP.
0installs, add-ins or paste-in steps
~1 sadded in transit, then straight back to your platform
SPF · DKIM · DMARCpass, signed as your own domain
Signature showcases
One template. Every device. No paste-in instructions.
Signatures are rendered on the server from your directory data, so a sales rep on a phone and an executive in Outlook send the same brand — banners, disclaimers and alias-aware identity included.
Corporatelive motion
R
Morgan ValeVP, Client TrustNorthstar Advisory
Saleslive motion
R
Rina ChoEnterprise Account LeadBrightline Systems
Executivelive motion
R
Elena MarquezChief Operating OfficerRedwood Global
Multi-brandlive motion
R
Kai BennettRegional DirectorAtlas Group
Applied in transit
The signature is added after send, in about a second, and the message is handed straight back to your platform for delivery. Deliverability and reputation stay yours.
Built from your directory
Names, titles, departments, phones and aliases sync from Microsoft Entra or Google Workspace. Nobody types their own signature, so nobody gets it wrong.
Campaigns without the paste
Run a time-boxed banner under every signature — an event, a launch, a notice — with click counts, and have it come down on a date.
Marketing Core Analytics
Messages stamped, active seats and banner clicks, day by day — counts, not surveillance: no pixels, no recipient tracking, nothing read on the device.
Salesforce, both directions
Titles and phone numbers sync from Salesforce user records into signatures, and banner campaigns report their clicks back as Salesforce campaigns.
Single sign-on
SAML 2.0 with Okta, Microsoft Entra ID or Google. Your staff open the portal with the login they already have; access follows your directory.
How it works
Send. Stamp. Deliver.
Send
A user sends mail from any client. Your platform routes only outbound messages to RubySig — a connector in Microsoft 365, a routing rule in Google Workspace.
Stamp
RubySig looks the sender up in your directory, renders their signature, and DKIM-signs the message as your domain.
Deliver
The message goes back to your platform, which delivers it from its own addresses. Recipients see Microsoft or Google — with SPF, DKIM and DMARC all passing.
What RubySig does Microsoft 365 setup Google Workspace setup