About
Who is behind Fromenance
Fromenance is a communication provenance platform built and operated by Many Software Enterprises LLC, a Delaware company. It exists because the customer's question, "did my bank actually send this?", was unanswered by every control in the stack, and the institution is the only party that can answer it authoritatively.
The problem we picked
Financial institutions, insurers, and utilities are impersonated every week. Their customers receive messages that look authentic and come from lookalike domains, free mail accounts, compromised infrastructure, and phishing kits with the logo copied in. SPF, DKIM, and DMARC authenticate a domain. Gateways and classifiers estimate a probability. Brand protection vendors find infrastructure on a lag. None of them talk to the customer holding the phone.
The customer wants one thing: a yes or a no from the institution itself. The institution can give that answer because it knows what it sent. Nobody had built the infrastructure to make that knowledge usable in seconds, on the institution's own domain, without a human in the loop. That is Fromenance.
The thesis
Written before a line of code, and unchanged since.
01
Verification is the wedge
It solves the immediate problem: fewer calls, fewer takeovers, less analyst time, and customers who keep trusting real mail.
02
Threat intelligence is the second product
Every failed verification is an impersonation sample delivered by the person it targeted. That is a signal no crawler has.
03
The communication provenance graph is the moat
Authoritative records of what institutions sent, joined to victim submitted lures, accumulated over years. The feature can be copied; the dataset cannot.
The people
Fromenance is built by George Rios, whose background is in enterprise software and insurtech, and is operated byMany Software Enterprises LLC, the company through which he builds and runs software products. The team is small on purpose: the product is infrastructure, the buyers are institutions, and the sale is a conversation with the person who owns impersonation.
We write the way we build: direct, specific, no gloss. If a page on this site makes a claim, it is a claim the product makes in its tests.
How we work with institutions
- Complementary, never a replacement. Keep DMARC at reject, keep your gateway, keep your takedown vendor. Fromenance sits above them and feeds them.
- Invisible to the customer. Everything customer facing lives on the institution's domain and in its branding. The Fromenance name appears only in the admin app and docs.
- Security first, then pilots. The data handling story, the DPA, and the subprocessor list were finished before the first pitch.
- Gated roadmap. Intelligence is built after a tenant is paying for verification. The network is built after an analyst confirms a campaign from real submissions.
Run a 60 to 90 day pilot on one communication stream.
Fraud alerts or transaction alerts are the best first stream. You get a written report of verification volume, verdict distribution, campaigns discovered, and intelligence yield.