See who’s off-brand in ninety seconds.
Ascripto reads the signatures your employees are actually sending, shows you every one that has drifted from your brand, and fixes them in one click. Google Workspace and Microsoft 365. No seat minimums.
Every signature tool enforces at creation. None of them look back.
You define a template, deploy it, and consider the job done. Six months later nobody can tell you how many employees are still running the old logo, how many are missing the legal disclaimer, or how many list a job title they were promoted out of last year.
The same APIs that write a signature can read it back. Ascripto starts there: sign in with Google, connect your directory and allow signature access, and within ninety seconds you get the number:
31 of your 47 employees have off-brand signatures. 12 use the previous logo. 6 have no disclaimer. 9 have an outdated job title.
That audit is free, permanently. Deploying and holding the fix is what we charge for: from €1 or $1 a seat a month.
Built for the platform that needs it most
Google Workspace has the weakest native signature controls of any major mail platform: one footer per organisational unit, no directory fields, no HTML (an image only by public URL), and appended below whatever the user already set — which is where double signatures come from. It also has the cleanest API for fixing them, writing signatures as a server-side property that reaches web and mobile with nothing installed.
Microsoft 365 is the harder case, and getting harder. Exchange Web Services is being disabled in phases from October 2026 to April 2027, and Microsoft Graph has never supported signature management. We cover it with an opt-in outbound relay, built on mail infrastructure we have run for a decade.
| Google Workspace | Microsoft 365 | |
|---|---|---|
| Setup | Minutes: connect the directory, allow signature access | One outbound connector |
| Mail routing change | None | Outbound only, MX untouched |
| Reaches mobile | Yes | Yes |
| A directory change in the signature | Within a couple of minutes | Within 15 minutes |
| Anything installed | No | No |
| Drift audit | Yes | Not yet; the relay signs every message regardless |
Your own servers, in the region you choose
Ascripto is built from self-contained deployments: each one has its own servers, database and storage, and the mail relay is a part it can run or leave out. For an organisation that needs it, we run a deployment on dedicated virtual servers of its own, in whichever Azure region its data has to stay in — with the Microsoft 365 relay, or without it.
Nobody else’s signatures, people or mail share it. Write to hello@ascripto.com and we will work out the details with you.
No seat minimums, and we mean the small end
Most tools in this category price out the companies that need them most — ten-seat minimums, or a monthly base fee before the first user. A twelve-person firm with a compliance requirement is told it is too small to matter.
Client-side deployment has near-zero marginal cost per user, so there is no seat minimum: you pay for the people whose signatures we delivered that month, not for ten seats you do not have. The smallest bill is €9 or $9 a month, which covers a team of four as well as one of nine. The audit stays free at any size. Pricing has the whole list.
What we are honest about
- Client-side deployment is not enforcement. On Google Workspace we write the same field the user can edit. Someone can revert it that afternoon. The difference is that we will tell you when they do — which is the point of the audit.
- A relay is a dependency in your mail path. If we have an outage, you cannot send email. That is a serious commitment and we would rather you started on the client-side channel and moved to the relay deliberately.
- Microsoft 365 has no audit yet. Microsoft offers no way for an app to read the signature someone set in Outlook, so for Microsoft 365 we sign at the relay and see nothing else. An Outlook add-in that reads them is next.