Verification tells you a credential is real, current and issued by someone you trust. It does not tell you whether this person, right now, in this context, is allowed to do the thing they are trying to do. That second question is eligibility.
Eligibility is what KeyFlux exists to answer. Every product we build is shaped around the same question: is this actor allowed to do this thing, right now, given the conditions? It is the question your business actually cares about, and it is the one everybody leaves to a pile of application code nobody wants to own.
Inside Verifiable Credential Core, Resolve is the engine that answers it.
Request a demoResolve
From verified to decided
You define the rule once. Resolve evaluates it over the verified attributes in the credential that was presented, and returns a decision with the reasoning attached.
Not a score. Not a probability. A determination, evaluated deterministically, that you can act on and defend to a regulator.
Express eligibility as policy: age, jurisdiction, licence status, authority level, employment, accreditation, whatever the rule actually is.
Run the policy over verified credential attributes at the moment of the decision, not at the moment of onboarding.
Every determination carries the inputs, the policy version and the outcome. When someone asks why, there is an answer.
The same policy runs across every channel that asks the same question. App, branch, call centre, partner, agent.
Is this customer eligible to open this product?
Does this approver hold the authority for a payment this size?
Is this person old enough to buy this, without me learning anything else about them?
Is this practitioner currently registered to perform this procedure?
Does this contractor have a current right to work and the licence this site requires?
Different questions. One eligibility engine inside Core.
Resolve is a capability of Verifiable Credential Core. It evaluates eligibility over a credential that has been presented and verified, so it lives with the engine that issues and verifies those credentials rather than floating above everything we make.
Today you do not buy Resolve on its own, and you do not buy Core without it. Whether it ever stands alone is a question we will answer with customers rather than on a roadmap slide.
Governments, national PKI and national identity services, issuing mDL and eID at population scale.
Banks, telcos, insurers and credit bureaus, taking a government-issued identity and deriving a credential for their own purposes.
Optional capability is priced as a module. Resolve never is, because it is the product. The rest of Core is what makes it possible to ask the question.
Explore Verifiable Credential CorePeople and organisations are not the only actors that need permission. An agent that opens a pull request, a workload that reaches into production, a piece of software that moves money. Each one raises a question with exactly the same shape. Is this agent, this action, this request eligible right now, given the conditions?
That is REMIT, and it is the other half of what KeyFlux does. Eligibility for non-human actors.
Evaluates eligibility over a credential that has been presented.
The inputs are verified attributes about a person or an organisation. The failure mode is admitting someone who does not qualify.
Evaluates eligibility over an action that has been proposed.
The inputs are the conditions around the request. The failure mode is letting a machine do something nobody authorised.
Different inputs, different failure modes, different code. That is deliberate, not an accident of history. A credential check and a machine authorisation break in ways that have almost nothing in common, and collapsing them into one engine would make both of them worse at the job they exist to do.
What the two share is the discipline. Express the rule once, evaluate it at the moment of the decision, and return a determination you can explain afterwards. Same discipline, two surfaces, on purpose.
Explore REMITCredentials. Governments are issuing them, standards bodies are converging, and verification will be a feature of everything within a few years. The same is happening on the machine side. Giving a workload an identity is becoming table stakes.
The decision made over the top. Whether a holder qualifies. Whether an agent is allowed to act. That is specific to your rules, your regulator and your liability, and it does not arrive in a standard.
Eligibility is where that lives.
Resolve answers it for the people and organisations that present a credential. REMIT answers it for the machines that propose an action. That layer is the company.
We will walk through a rule expressed once, evaluated over verified attributes, and explained end to end.
Request a demo