Deterministic authority
Authorization is a security decision, not a model-generated permission.
Drelvan · Developer Beta · $0
Security at the
moment of action.
Drelvan is a vendor-neutral execution-security substrate that connects identity, authorization, execution authority, native enforcement, provenance and evidence.
DRELVAN / EXECUTION PATHLOCAL / ENFORCED
UNTRUSTED INTENT
IDENTITY · POLICY · AUTHORIZATION
EXECUTION AUTHORITY · NATIVE ENFORCEMENT
ALLOWAUTHORIZED EFFECT
DENYCONTAINED EFFECT
effect·provenance·receipt·revocation
01 / DRELVAN
Make authorization reach the real effect.
Modern software can launch processes, invoke tools, access resources, communicate over networks and change state. Drelvan is designed to make those transitions explicit, authorized and enforceable.
The security primitive remains local and authoritative. Management, governance and scale can sit above it without becoming the fundamental authority for protected local effects.
Native enforcement
Execution authority is bound to the host platform and its enforcement mechanisms.
Verifiable lineage
Execution can carry provenance, evidence and tamper-evident receipts.
Cloud-independent core
Cloud and management layers do not replace the local security authority.
02 / ARCHITECTURE
One security lineage from intent to outcome.
Drelvan keeps the security relationship intact from an untrusted request through authorization, native execution, real effect, evidence and response.
01UNTRUSTED INTENT → IDENTITY → POLICYunderstand the requested action
↓
02AUTHORIZATION → SECURITY INVARIANTSestablish permitted authority
↓
03EXECUTION AUTHORITY → NATIVE BINDING → OS ENFORCEMENTmake authority real
↓
04REAL EFFECT → OBSERVATION → OUTCOMErecord what actually happened
↓
05PROVENANCE → EVIDENCE → RECEIPT → AUDITmake the security history verifiable
↓
06CONTINUOUS RE-EVALUATION → CONTAINMENT / REVOCATIONrespond when authority changes
03 / DEVELOPER BETA
Real security.
Real workloads.
Drelvan is currently available as a $0 Developer Beta. The focus is real protected execution: installation, workload compatibility, policy behavior, evidence and receipts, diagnostics, recovery, performance and security feedback.
$ drelvan init
$ drelvan doctor
$ drelvan approve
$ drelvan protect ./your-program
protected execution path activeCurrent platform posture
Windows x86_64SUPPORTED
Linux x86_64SUPPORTED
macOS native enforcementNOT CLAIMED
Independent assessmentNOT YET
Public claims are intentionally limited to documented engineering evidence and the current beta scope.
04 / TRUST
Internally verified.
Not externally certified.
The current release has internal engineering validation across documented security, enforcement, adversarial, reliability, performance and supply-chain work. That validation is not represented as an independent audit, penetration test or external certification.
✓Developer Beta is the current public release posture.
✓Security claims remain bounded by documented evidence.
✓Local security does not depend on cloud authorization.
—Independent security assessment has not yet been performed.
—External security certification has not been issued.
Security disclosureSuspected Drelvan vulnerabilities should be reported privately before public disclosure.
DRELVAN
Build software that can
prove what it was allowed to do.
Explore Drelvan and follow the execution-security layer as it evolves.
Developer Beta →