Perslis early access
We are admitting a small group of technical teams with real systems, difficult constraints, and the discipline to test a verification-first runtime properly.
Every application is reviewed by a person.
We prioritize systems with measurable outcomes.
Permissions expand only after evidence.
What we are looking for
The beta is not a waitlist for spectators. It is a working partnership with teams prepared to define a real outcome, operate inside clear boundaries, and tell us where the runtime succeeds or fails.
Access review
Before access is enabled, Perslis reviews who you are, whether you are authorized to use the target systems, and how the pilot will be contained. We do not ask for passwords, private keys, government ID numbers, or confidential source material in this application.
This is a private product-security and access review. It is not a government security clearance and Perslis does not issue government clearances.
We verify professional identity, organizational affiliation, and a credible public or referred footprint.
We confirm that the applicant owns, operates, or has explicit permission to test every system in scope.
We classify data sensitivity, integration points, requested actions, deployment model, and potential blast radius.
We agree on allowlisted paths, tools, commands, credentials, retention, and the sandbox boundary before access.
The pilot begins with the smallest useful scope. Capabilities expand only when logs and verified outcomes support it.
Access may be paused or revoked if identity, scope, authorization, behavior, or risk materially changes.
Beta application
Specificity wins. Tell us what the system does, what is currently impossible or expensive, who owns it, and how we would know the pilot worked.
Applications open