REQUEST ACCESS invite-only

How do I request access?

The public pages tell the story of AEGIS. The Install guide and the Auspex Beta are shared only with invited operators — real security tooling deserves a real hand-off, not an anonymous download.

STATUS

Still a prototype — in active development

AEGIS is an early-stage prototype under active development. Features land, move, and change often, and rough edges come with the territory — it isn't a finished product yet.

That's exactly why access is invite-only and kept to a small, trusted group for now: it lets the project grow up alongside people who understand they're working with something still taking shape. If that's you, the request below is how you get in.

WHAT’S GATED

Request Access

Public

The story

Intro, Origin, the Stack, and Digital Orukami — read freely, share the link.

Request Invite

Install guide

The from-GitHub install (repo access + configs). Granted to invited operators.

Request Invite

Auspex Beta

The RF sight in beta — hands-on, still evolving. By invite while it stabilizes.

ACCESS

Requesting Access to AEGIS Process

The repository is private — no public downloads. Access is granted per person, not per link: the URL alone never grants pull or clone rights. Here's what an application needs.

HOW IT WORKS

From request to access

STEP 01

Submit

Send the request form with your details and acknowledgment.

STEP 02

Reviewed

Vetted by hand in a small cohort — cold, unreferred requests get extra scrutiny.

STEP 03

You get an email

Either way, you hear back — approved or denied. No silent drops.

STEP 04

Access opens

On approval, the repo becomes available at your tier — Read-only or Clone / pull.

PROVIDE

What you'll provide

Six things go in your request — build the form around these, and don't skip one.

Step 01
GitHub
A GitHub username with real history — prior activity/repos, not an account made the same day.
Step 02
Email
An email tied to a verifiable institution — school (.edu), employer, or organization matching your affiliation.
Step 03
Profile
LinkedIn or an equivalent professional profile corroborating your name, school/employer, and background.
Step 04
Reason
What you intend to do with it — research, ECHO Club membership, evaluation, or contribution.
Step 05
Referral
How you found AEGIS — who vouched for you, or what introduced you. Cold requests get extra scrutiny.
Step 06
Prior work
Optional but preferred — a repo, portfolio, or security project showing you're a practitioner.
ACKNOWLEDGE

What you'll acknowledge

Three things you'll confirm with the checkboxes in the request form below:

The three acknowledgments

Each is a required checkbox on the form — your ticks come back to us as your confirmation.

Scope
AEGIS / Deep_Root is defensive security tooling only — no offensive use, and no redistribution outside the granted invite.
License
Use is governed by the repository's LICENSE — currently all rights reserved (source-available, invite-only). Access is not a right to relicense, resell, or redistribute.
Revocation
Access can be revoked at any time, without notice or justification owed. Local clones made before revocation are your responsibility.
TIERS

Access tiers

Tier · Read-only

Observer

View the code — cannot clone, pull, or download. The default for most first-time requests.

Tier · Clone / pull

Contributor

Clone and pull access, with a path to Write later. For ECHO Club core members, vetted researchers, and active collaborators.

FORM

Request Form for AEGIS

Fill out according to the request process. Thank you for your interest in AEGIS.

About you
Your request
Access tier requested
Acknowledgments — all required
every field you complete cracks the shell

Prefer email? Reach out directly at github.com.pyramid640@passmail.com.