Open a channel.

Tell us what you're protecting. We'll come back with a scoped proposal — what's fair game, what proof looks like, and when the swarm starts.

01 — Start an engagement

Scope a test.

Drop your work email in the card below (or write to us directly) with a sentence about your estate — domains, apps, or cloud accounts. We reply within one business day with:

  • A proposed scope and rules of engagement in writing
  • What "proven" will mean for your environment
  • Timeline, pricing model, and the operator on point

engagements@yegg.io — new business
ops@yegg.io — existing engagements & kill-switch
press@yegg.io — media & speaking

Authorized testing only. We will ask you to prove control of in-scope assets before any agent touches them.

02 — Response times
new business

1 business day

Scoped proposal with rules of engagement and a named operator.

active engagement

15 minutes

Kill-switch and scope-change requests during live testing, 24/7.

researchers

72 hours

Disclosure reports to security@yegg.io — see our safe harbor.

03 — Prefer the console?

Try the shell.

Press ~ anywhere on this site, or type yegg, to open the ops console — help lists commands, scan your-domain.com runs a simulated recon pass.

Open the console →