VegaSec / Founding Pilots

Founding pilots: one target, one written review, evidence and limits.

VegaSec keeps private reviews, repository checks, agent permission maps, and remediation memos as the evidence layer. A founding pilot is a bounded written engagement and not a live sales call: you submit one target with rough context, a reviewer checks public sources, and the memo states what was found, what was not, and what to fix.

Written intake onlyNo live call requiredNo wallet custodyEvidence and limitsPrivate by default

The pilot offer

What a founding pilot receives

A written evidence memo

One bounded review of one target: what was checked, the evidence found, severity and confidence for each finding, what stayed unknown, and a remediation checklist.

Price

By quote after written triage. Quotes start at $100 and follow the ranges published on the pricing page. Continuous Watch, the monitoring entry, is the one package buyable today at $49.

Duration

One engagement with one delivery, not a subscription. Continuous Watch covers one billing period and does not renew on its own.

What we ask in return

Structured feedback on the memo, permission to cite the engagement in the founding pilot record, and an optional testimonial. Publishing your name is your call and is agreed in writing before anything becomes public.

Available today

Continuous Watch

$49 · one billing period

Change alerts for one contract or repository, delivered to e-mail or Telegram, with a signed history link. Charged once for a single billing period, and it does not renew on its own.

See the package on pricing

Two ways in: buy monitoring now, or send a target for a quote.

Written review by quote

Quotes start at $100

Send the target and the context. The quote follows the ranges published on the pricing page and is confirmed before any work starts.

Open written intake

Review lanes

Four lanes, one evidence standard.

Pick the lane that matches the target. Every lane uses the same written intake and the same standard: bounded scope, named sources, stated limits.

Serious review lane

Private Audit Desk

By quote after triage

For teams that need a deeper contract, repository, launch, or diligence memo before buyers, partners, or agents act.

Submit the target and the context privately. VegaSec separates public scan signals from reviewer-checked findings, evidence notes, and decision history.

  • Contracts, repositories, launch surfaces, and buyer diligence.
  • Nothing goes public unless the agreed scope includes a public artifact.
  • Output stays on evidence, severity, confidence, limits, and the remediation path.
Reserve Private Audit

Crypto launch intake

Trench Desk

By quote after triage

For launch teams that need a concise buyer-facing risk memo before distribution.

Submit a token, a DexScreener pair, an explorer URL, or a public launch surface. VegaSec turns public signals into a written evidence memo and a remediation checklist.

  • Public scan stays no-login, and the private review stays account-protected until delivery.
  • Written handoff only, so rough notes and translated context are fine.
  • The memo separates public signal checks from reviewer notes.
Reserve Trench Desk

AI workflow and automation review

Agent Trust Pilot

By quote after triage

For teams wiring agents, workflow automations, API keys, or operator tools.

Submit a public GitHub repository or a documented workflow. VegaSec maps permissions, data exposure, operator gates, and ALLOW / REVIEW / BLOCK decision points.

  • Built for the point where humans and agents both need a trust decision.
  • Focuses on permission scope, logs, secret handling, and escalation paths.
  • Written intake only, so English fluency is not required.
Reserve Agent Trust

Bounty policy review

Bounty Trust Desk

By quote after triage

For communities that want creator and bounty tasks tied to evidence, references, or remediation without weakening review credibility.

VegaSec reviews bounty language and task design so the campaign asks for useful proof instead of hidden promotion, buying instructions, fake attestations, or unsafe stunts.

  • Allowed: evidence collection, references, issue reproduction, remediation tasks.
  • Blocked: buying instructions, undisclosed promotion, fake attestations, dangerous stunts.
  • Deliverable is a policy-checked task sheet, review labels, and a risk note.
Reserve Bounty Desk

After the click

What happens after you submit

  1. 1 · The written intake opens with the review lane preselected. Paste the target, add rough context, and send it.
  2. 2 · You get a reservation id on screen. Save it for follow-up.
  3. 3 · A reviewer reads the intake and answers over the contact you provided, with the scope and the quote if a quote applies.
  4. 4 · After agreement, work starts and the written memo is delivered as a shareable artifact.
  5. 5 · Optional and separate: Continuous Watch adds change alerts, and a re-scan follows once you ship the remediation.

Operator guardrails

Written intake does not mean loose claims.

The intake is public and asynchronous, while the language stays strict: bounded review, evidence, unknowns, and limits. No endorsement language and no promotional shortcuts.

Review lanes stay separate from bounty campaigns: bounty work never changes a finding or a Trust Index score.
Public scans stay no-login and show bounded public signals only. Private reviews stay account-protected before full evidence delivery.
No financial advice, no token promotion, and no claim that a project is endorsed.
No live English call required: submit written context, translated notes, screenshots, or a public repository.
No wallet custody, no seed phrases, no browser secret sharing, and no buying instructions.
Every pilot stays bounded: evidence gathered, unknowns listed, limits stated, next actions scoped.

Ready for written intake

Paste the target. Add rough context. VegaSec handles the written review path.

The intake accepts token targets, public GitHub repositories, and documented agent workflows without authentication. Rough notes, a bullet list, or translated context are fine, and the reviewer normalizes them later.

Open written intake