Spam filtering your customers can see.
Make spam filtering a feature of your form service without building a filter. One platform key, a managed key for every customer form, and verdicts with reasons you show in your own interface.
Spam is the feature request that arrives as a complaint.
Every form service hears the same three. spamex answers each one inside your product, so the answer is a feature, not a support reply.
Filtered before delivery, with the reason on each one. The pitch never reaches the inbox; the customer sees it was caught and why.
No. Nothing changes on the form and nothing loads on the page. Their visitors keep submitting; the bots stop arriving.
The reason is written under the message in plain words, and a Not spam button delivers it and teaches the filter. The customer fixes it without you.
One key per customer form. Nothing leaks between them.
When a customer creates a form, one call creates its key. Each key carries its own settings, allowance, usage and memory of what that customer marked legitimate. A correction on one form never changes another customer's verdicts, and no single customer can blacklist a sender for everyone.
- Create, rotate and revoke keys from your own admin
- Per-form site description, language and honeypot field your customers can edit
- Per-form allowances if you sell tiers
- Usage rolled up per form for your billing
Four sentences you can put on your own pricing page.
Filtering happens after submission, on your side. Visitors never see it.
Plain wording you can show as-is, and a one-click way to overrule it.
Nothing readable is kept unless the customer opts in. Sender details are hashed. A data-processing agreement is included.
If spamex is slow or unreachable, submissions are delivered as normal.
Priced per check, so it scales with your customers.
Both platform plans include the platform API, the usage roll-up and a data-processing agreement. Volumes in between or above come as a private deployment in your region on the Dedicated plan; above five million, or when procurement needs a conversation, we price per thousand and invoice.
All plans →Questions platforms ask
How do customers' forms stay separate?+
Each customer form gets its own key with its own settings, allowance, usage and memory of what that customer marked legitimate. A correction on one form never changes another customer's verdicts, and a sender one customer flags is not blacklisted for everyone.
Can we try it on real traffic before committing?+
Yes. Run it in fast mode on a staging copy of your ingest path, or shadow it in production and only log the verdicts. A demo call runs spamex on a sample of your own submissions so you see the verdicts and reasons before any code changes.
Our customers write in many languages.+
So do their spammers. Submissions are read the same way in English, German, Spanish, French, Japanese and a dozen more; a per-form language setting only sharpens one signal.
Some customers cannot send data to a third party.+
spamex is available self-hosted inside your own infrastructure as an enterprise arrangement, with the same platform API, updates and support.
See it on your own submissions.
A demo call runs spamex on a sample of your traffic, with the reasons explained, and comes with an evaluation key for your staging environment.