ABOUT QEVRA
Useful access.
Without the handoff.
Qevra has two distinct paths: Gateway mediates credential use for people and agents; Access administers external memberships for existing Human Principals.
THE PROBLEM
Standing credentials travel too far.
Agents, contractors, and CI jobs need to do work. Passing a reusable key to every actor makes each task a long-lived security exception.
GATEWAY
Grant the use. Keep the value.
An Entitlement and Access Lease bound the caller’s authority. The Gateway admits the request, injects the stored value, and keeps a private record.
ACCESS
Authorise the membership. Observe removal.
Access uses a fixed-deadline Provider Assignment and a separate worker. GitHub team membership is the first proof; live provider changes remain subject to acceptance gates.
Give your next task
the right kind of access.
Show us a protected API call or a time-bounded human membership. We’ll map the right Qevra boundary.