VRP PRIVATE EVALUATION — AUTHORIZED APPLICATION
RESTRICTED ACCESS NOTICE
This form is not a public application form.
It is the second stage of a controlled private qualification process.
Completing or submitting this form without prior written authorization from the VRP Program will provide no access, no priority, no reservation of engineering capacity, and no entitlement to review.
Unauthorized submissions may be discarded without acknowledgement or further correspondence.
If you have not received explicit written authorization to use this form, stop here.
The first step is to contact:
jumpingvpn@proton.me
Use the email subject:
VRP PRIVATE EVALUATION REQUEST — [LEGAL COMPANY NAME]
────────────────────────────
PUBLIC INTAKE STATUS
The previously announced public intake window has been closed early.
The former deadline of 15 August 2026 no longer represents an active public application period.
Effective immediately:
open public applications are closed;
direct submission through this form is not permitted;
future evaluation begins through email-based pre-qualification;
every organization must pass identity, technical, operational, security, and commercial screening;
access to this form requires explicit written authorization;
no public reopening date is currently scheduled;
no organization is guaranteed consideration or acceptance;
engineering capacity is not reserved by sending an email, answering the questionnaire, or submitting this form.
This change applies globally and is not based on geography.
Organizations from any country or region may be considered, but no country, company, industry, or market receives automatic priority.
────────────────────────────
CURRENT STATUS
PUBLIC_PILOT_INTAKE=CLOSED_EARLY
OPEN_FORM_SUBMISSION=DISABLED
INITIAL_CONTACT=EMAIL_REQUIRED
PRE_QUALIFICATION=MANDATORY
TALLY_ACCESS=WRITTEN_AUTHORIZATION_ONLY
UNAUTHORIZED_SUBMISSION=NO_REVIEW
AUTOMATIC_ACCEPTANCE=NO
ENGINEERING_CAPACITY_RESERVED=NO
FUTURE_ACCESS=PRIVATE_AND_SELECTIVE
PUBLIC_REOPENING_DATE=NOT_SCHEDULED
PROTECTED_RUNTIME_PUBLICLY_AVAILABLE=NO
PROTOCOL_DEVELOPMENT=ACTIVE
────────────────────────────
REQUIRED ACCESS PROCESS
STAGE 1 — INITIAL EMAIL REQUEST
Before completing this form, contact:
jumpingvpn@proton.me
Your initial email must include:
legal company name;
official company website;
country of registration;
full name of the representative;
position and department;
corporate email address;
LinkedIn profile;
explanation of your authority to represent the organization;
concise description of the intended VRP evaluation;
reason your organization is requesting access;
expected technical and commercial timeline.
Emails containing only general expressions of interest will not be sufficient.
Messages such as “we would like to know more,” “please send information,” or “we are interested in collaboration” do not establish technical or commercial readiness.
Do not send credentials, private keys, production secrets, regulated data, customer information, proprietary source code, or sensitive infrastructure diagrams during the initial contact stage.
────────────────────────────
STAGE 2 — PRE-QUALIFICATION QUESTIONNAIRE
If the organization and representative can be reasonably verified, you may receive the VRP Pilot Pre-Qualification Questionnaire.
Every question must be answered clearly and completely.
Generic, promotional, speculative, inconsistent, unverifiable, or low-effort responses will not proceed.
The questionnaire contains the following sections.
1. Company Information
Provide:
legal company name;
company website;
country of registration;
year founded;
approximate number of employees;
primary industry;
relevant subsidiaries or operating entities;
primary geographical markets.
2. Identity Verification
Provide:
full name;
position;
department;
LinkedIn profile;
corporate email address;
explanation of your authority to represent the organization;
identity of the executive, technical, or commercial sponsor;
verifiable evidence connecting you to the organization.
Public email services may require additional verification.
3. Technical Background
Describe the current infrastructure, including all applicable environments:
public cloud;
private cloud;
on-premises infrastructure;
hybrid infrastructure;
edge environments;
private backbone;
data centres;
mobile or satellite environments;
laboratory or research infrastructure;
custom networking systems.
Identify relevant cloud providers, operating systems, network boundaries, orchestration platforms, and existing continuity mechanisms.
4. Current Operational Challenges
Describe the actual problem your organization is attempting to solve.
Include real examples whenever possible:
session interruption;
transport-path failure;
NAT rebinding;
endpoint mobility;
failover behaviour;
recovery delay;
replay risk;
authority transition;
split-brain conditions;
evidence or audit limitations;
unreliable reconnection behaviour;
dependence on a single transport path.
Abstract statements without a concrete operational scenario may be insufficient.
5. Why VRP?
Explain:
how you discovered VRP;
which public materials you reviewed;
why VRP is relevant to your organization;
which specific capability attracted your attention;
why existing technologies do not fully address the stated problem;
what you expect VRP to demonstrate.
6. Intended Evaluation
State exactly what you intend to validate.
Possible areas include:
session continuity;
transport-independent session identity;
migration safety;
NAT rebinding;
blackout recovery;
admission control;
replay protection;
authority progression;
evidence generation;
security boundaries;
runtime resilience;
failure handling;
deterministic recovery;
integration behaviour.
Each selected capability must be connected to a defined evaluation scenario.
7. Existing Technologies
Identify technologies currently deployed or being evaluated, including where applicable:
TCP;
UDP;
QUIC;
TLS;
WireGuard;
IPsec;
MPTCP;
SD-WAN;
service mesh;
overlay networking;
proprietary failover systems;
custom transport or session-management systems.
Explain why the existing architecture is considered insufficient for the intended use case.
8. Evaluation Environment
Specify where the evaluation would occur:
production;
pre-production;
laboratory;
isolated testbed;
simulation;
research environment;
private cloud;
public cloud;
edge deployment;
multi-region infrastructure.
Describe isolation boundaries, network control, observability, rollback capability, and permitted failure injection.
9. Expected Scale
Provide realistic estimates for:
number of endpoints;
concurrent sessions;
geographic regions;
network paths;
expected traffic profile;
session duration;
mobility or path-change frequency;
availability requirements;
recovery objectives;
evidence volume.
10. Technical Team
State:
number of participating engineers;
names or roles of technical leads;
architecture responsibilities;
networking responsibilities;
security responsibilities;
platform or infrastructure responsibilities;
expected time commitment;
internal escalation path.
11. Security Expectations
Describe:
security requirements;
threat model;
compliance requirements;
audit requirements;
data-handling restrictions;
network segmentation requirements;
key-management expectations;
logging and evidence requirements;
operational constraints;
incident-response requirements;
restrictions on external components.
12. Success Criteria
Define measurable success and failure criteria.
Explain:
what must be demonstrated;
which metrics will be collected;
which invariants must remain true;
which failures must be tolerated;
which events must be rejected;
what evidence must be produced;
who will validate the result;
what conditions would cause the Pilot to be rejected.
“System works” is not an acceptable success criterion.
13. Timeline
Provide:
requested start date;
required completion date;
internal decision deadline;
procurement timeline;
security-review timeline;
legal-review timeline;
availability of the technical team;
known dependencies.
Requested dates do not reserve capacity.
14. Internal Commitment
Confirm whether engineering resources will remain allocated throughout the evaluation.
State:
expected weekly allocation;
responsible technical owner;
responsible executive sponsor;
availability for technical review;
ability to reproduce failures;
ability to provide requested evidence;
ability to complete agreed milestones.
15. Confidentiality
Confirm whether the organization can operate under confidentiality where required.
Identify:
NDA requirements;
legal entity that would sign;
authorized signatory;
restrictions affecting technical disclosure;
restrictions affecting evidence exchange;
expected legal-review duration.
16. Decision Process
Identify all parties involved in the final decision:
engineering;
architecture;
networking;
security;
compliance;
legal;
procurement;
management;
executive board;
other stakeholders.
Explain who has final technical authority and who has final commercial authority.
17. Public Communication
If the evaluation succeeds, state whether the organization would consider:
a joint technical validation;
an anonymized case study;
a public case study;
an engineering report;
a verified reference;
no public communication.
The answer does not automatically affect acceptance, but expectations must be explicit.
18. Additional Information
Provide any other information relevant to the review, including:
strategic deployment considerations;
integration dependencies;
regulatory constraints;
previous evaluation attempts;
known architectural risks;
reasons the request should receive limited engineering capacity.
19. Additional Review
The initial questionnaire may not be sufficient.
Follow-up questions may be issued when:
information is incomplete;
claims cannot be verified;
technical scope is unclear;
infrastructure readiness is uncertain;
the proposed environment creates security concerns;
authority to represent the organization is unclear;
commercial readiness has not been demonstrated;
answers are inconsistent with publicly available information.
All follow-up questions must be answered with the same level of accuracy and detail.
Failure to provide clear, consistent, and verifiable information may end the review.
────────────────────────────
STAGE 3 — DISCRETIONARY REVIEW
Completion of the questionnaire does not guarantee access to this form.
The review may include:
company verification;
representative verification;
technical relevance assessment;
infrastructure-readiness assessment;
security review;
operational-risk assessment;
engineering-capacity review;
strategic-fit assessment;
preliminary commercial-readiness review;
clarification interviews;
additional written questions.
There is no guaranteed response time.
The absence of an immediate response does not mean approval, reservation, or acceptance.
The review may be paused or terminated without progressing to the next stage.
────────────────────────────
STAGE 4 — WRITTEN AUTHORIZATION
If the pre-qualification review is successful, you may receive:
explicit written authorization;
the authorized corporate email address;
an application reference;
instructions for completing this form;
any participant-specific questions;
submission requirements;
an authorization validity period, where applicable.
Authorization is:
organization-specific;
representative-specific;
non-transferable;
revocable;
limited to the stated evaluation;
not evidence of Pilot acceptance.
Do not forward an authorization or private form link to another person, company, subsidiary, partner, or adviser without written permission.
────────────────────────────
FORM SUBMISSION REQUIREMENTS
To submit this form, you must provide:
issued application reference;
legal company name;
authorized representative name;
authorized corporate email;
confirmation that pre-qualification was completed;
confirmation that written authorization was received;
confirmation that submitted information remains accurate;
acceptance of the review conditions;
acknowledgement that capacity is not reserved;
acknowledgement that submission does not guarantee acceptance.
A submission that cannot be matched to an issued authorization may be rejected automatically.
────────────────────────────
UNAUTHORIZED SUBMISSIONS
Submitting this form without written authorization will not:
create an application;
enter the organization into a queue;
reserve Pilot capacity;
initiate technical review;
initiate commercial negotiations;
grant access to VRP;
grant access to the Protected Runtime;
establish confidentiality;
create an obligation to respond;
preserve any previous public-intake conditions.
Unauthorized submissions may be deleted without acknowledgement.
Repeated attempts to bypass the qualification process may result in future requests being declined.
────────────────────────────
WHO MAY BE CONSIDERED
Private evaluation may be relevant to:
network infrastructure vendors;
telecommunications companies;
systems integrators;
critical infrastructure operators;
enterprise networking teams;
cloud and edge infrastructure providers;
satellite and mobility platform operators;
data-centre operators;
regulated infrastructure providers;
research organisations with a defined engineering objective;
organisations prepared to allocate technical, security, legal, and commercial resources.
Company size alone does not guarantee priority.
Brand recognition alone does not guarantee access.
Technical relevance, readiness, verification, and the ability to produce meaningful evaluation evidence are more important than general expressions of interest.
────────────────────────────
ACCEPTANCE STANDARD
Priority may be given to organizations demonstrating:
a clearly defined operational problem;
a technically relevant evaluation environment;
measurable success criteria;
realistic deployment intent;
identifiable technical ownership;
allocated engineering resources;
security-review capability;
legal and commercial readiness;
willingness to perform evidence-based validation;
ability to satisfy identity and authority verification;
long-term integration potential.
Requests may be declined when they are:
incomplete;
generic;
speculative;
unverifiable;
primarily promotional;
unrelated to VRP’s engineering objectives;
unsupported by internal resources;
submitted without organizational authority;
dependent on unrestricted access to protected intellectual property;
incompatible with available engineering capacity.
A decision to decline does not require a detailed explanation.
────────────────────────────
ENGINEERING CAPACITY
VRP evaluation capacity is a finite engineering resource.
Availability depends on:
Protected Runtime development priorities;
active evaluation workload;
integration complexity;
security review;
evidence processing;
support requirements;
testing and release schedules;
participant responsiveness;
operational risk;
strategic relevance.
No capacity is reserved until all required reviews are complete and explicit written acceptance has been issued.
Pre-qualification, authorization to use this form, or form submission does not reserve capacity.
────────────────────────────
COMMERCIAL AND CONTRACTUAL BOUNDARY
Technical pre-qualification is not a commercial offer.
Commercial terms, licensing, scheduling, deployment boundaries, support scope, acceptance criteria, termination conditions, payment structure, refund conditions, intellectual-property boundaries, and confidentiality obligations are addressed separately.
No commercial relationship exists until the required agreements have been reviewed and signed by the relevant parties.
Past public statements, previous form conditions, preliminary discussions, or access to public repositories do not create a contractual entitlement.
────────────────────────────
PROTECTED RUNTIME AND INTELLECTUAL PROPERTY
The Protected Runtime is not included in public repositories.
Submitting an inquiry, answering the questionnaire, receiving authorization, or completing this form does not grant:
source-code access;
access to protected runtime internals;
ownership of VRP;
rights to proprietary mechanisms;
unrestricted reverse-engineering rights;
production deployment rights;
redistribution rights;
licensing rights;
exclusivity.
Any permitted access is defined only through participant-specific written agreements.
────────────────────────────
FINAL ACKNOWLEDGEMENT
Before submitting, confirm that you understand:
this is not a public application form;
prior written authorization is mandatory;
unauthorized submission provides no benefit or priority;
questionnaire completion does not guarantee authorization;
authorization does not guarantee acceptance;
submission does not reserve capacity;
additional questions may be required;
review timing is not guaranteed;
incomplete or unverifiable information may be declined;
Protected Runtime access is not provided by this form;
final decisions remain solely at the discretion of the VRP Program;
only explicit written confirmation establishes acceptance.
────────────────────────────
FINAL STATUS
PUBLIC_APPLICATIONS=CLOSED
FIRST_CONTACT=jumpingvpn@proton.me
PRE_QUALIFICATION_QUESTIONNAIRE=REQUIRED
WRITTEN_AUTHORIZATION_BEFORE_TALLY=REQUIRED
DIRECT_TALLY_SUBMISSION=NO_EFFECT
UNAUTHORIZED_SUBMISSION=NO_QUEUE_NO_REVIEW_NO_CAPACITY
FOLLOW_UP_REVIEW=MAY_BE_REQUIRED
AUTOMATIC_ACCEPTANCE=NO
GUARANTEED_RESPONSE_TIME=NO
GEOGRAPHIC_RESTRICTION=NONE
PROTECTED_RUNTIME_PUBLICLY_AVAILABLE=NO
FUTURE_EVALUATIONS=PRIVATE_SELECTIVE_DISCRETIONARY
ENGINEERING_DEVELOPMENT=ACTIVE