Aether · Strikes Request a strike →
Aether · Direct Funded Strikes

Fund one outcome. Get it shipped against an exact commit — and proven.

A strike is a bounded engagement for a single defined result. Aether builds it, Predator adversarially reviews it, and you get a receipt pinned to the delivery SHA — real exit codes, residual risk disclosed. No retainers. No vague “it’s secure.”

Request a strike → How it works
Fixed scope. Deposit-gated. Exact-SHA receipt. Predator review.
Delivered personally by Brandon Barrante, founder of Aether AI — the team behind Predator, Protocol-C, and the Aether stack.
Predator delivery receipt ✓ VERIFIED
target_repositoryacme/checkout-api target_shae7b41c9…a0f2 declared_surfaceauth · rbac · billing routes_executed7 passed / violated7 / 0 errors0
token-forgery ✓ idor ✓ price-tamper ✓ scope-escalation ✓
limitations: verified against the declared routes and the exact delivery commit only. Not a certification of general security.
// example receipt
The ladder

Pick the outcome. We quote a bounded scope + deposit.

Each strike is one defined result with acceptance tests written before work starts. Prices are starting deposits; final scope is fixed in writing.

01

Repo / CI / deploy rescue

Broken build, red pipeline, failed release — back to green with tests pinned.

Reserve — $350 deposit →
02

API / auth / RBAC / billing gate

Close an access-control, capability, or billing hole with a reproducible before/after.

Reserve — $750 deposit →
03

AI-agent / browser workflow

Ship a bounded agent or browser automation that completes the task, observably.

Reserve — $1,000 deposit →
04

Authorized app-sec / agent-authority review

Source-first review of a declared surface, with an adversarial Predator pass and a scoped receipt.

Reserve — $1,000 deposit →
05

Focused backend / product buildout

One well-defined feature or service, built and verified against an acceptance harness.

Reserve — $1,500 deposit →
How a strike works

Six steps from scope to collected payment.

STEP 1

Scope freeze

Outcome, exclusions, acceptance tests, and the exact base commit — pinned in writing.

STEP 2

Deposit

You get a payment link. Work begins the moment the deposit clears.

STEP 3

Build

A bounded team maps the repo and builds against a failing acceptance harness.

STEP 4

Predator review

An independent adversarial pass tries to break the change against the declared routes.

STEP 5

Delivery receipt

Exact base/delivery SHA, commands, exit codes, tests, Predator verdict, limitations, rollback.

STEP 6

Collect

You accept against the tests you approved. Balance settles on acceptance.

Every delivery includes
Exact base + delivery SHAsReproduce the before and after, byte-for-byte.
Acceptance harnessTests you approved, passing on the exact head.
Adversarial reviewPredator tries to break it, then confirms the fix.
Real exit codesActual commands and outputs, not screenshots.
Residual-risk disclosureWhat was not covered, stated plainly.
Rollback instructionsA clean path back if you need it.
Request a strike

Tell us the outcome. You’ll get a bounded scope + deposit link back.

No commitment yet. This is a scoping request, not a payment.
Fixed scope. Acceptance tests are agreed before any deposit.
Proof, not vibes. Every strike ships with a Predator receipt.
Authorized work only We take on work on systems you own or are explicitly authorized to change. No denial-of-service, no credential or account attacks, and no testing of third-party systems you don’t control. Requests outside that line are declined.

Requests go to [email protected]. Reserve a slot with a deposit above, or request a scoping call first — either way, scope and acceptance tests are agreed before any work starts. Prefer a public rail? GitHub Sponsors is available for backing the work openly.

Request received.

You’ll get a reply within one business day with a bounded scope, acceptance tests, and a deposit link. Nothing is charged until you approve the scope.