private alpha · applications open
Get credit for work you can actually show.
Vreko helps AI-heavy engineers and builders assemble inspectable evidence for specific claims about work they actually did. You review it, correct it, and decide whether anyone sees it. The Alpha is a small, curated cohort testing whether that evidence makes your claims easier to evaluate.
About 30–45 minutes for the first pass once you are invited. That is a planning estimate, not a measurement.
- What is Vreko?
- Evidence for AI-assisted professional work. Vreko takes a specific claim about your work, gathers evidence from sources with different authority, and records what that evidence establishes, what it does not, and what is still unknown. The result is a private Passport. It is not a résumé builder, and it does not score or rank you.
- Why was I sent here?
- Someone thought your AI-assisted work might be worth showing with evidence. Being referred gives them nothing: no access to your sources, your Passport, or anything you have not approved.
- What do I get?
- A private Passport of specific claims about your work, each with its evidence, its state, and what it does not establish. When you choose, one view of it for one recipient and one purpose, which you preview before you approve.
- What can a recruiter or evaluator see?
- Only a view you approved for them. They can inspect its evidence and ask the Passport questions; answers come from that view alone. They do not see your private Passport, your sources, evidence you excluded, or how much you excluded.
- Can I inspect and correct what Vreko derives?
- Yes. Under the Alpha contract you can accept a claim, edit it (the original stays in history), dispute evidence or attribution, exclude evidence from one view, or drop a claim. A correction does not rewrite the source record, and it does not silently change a view you already approved.
before we ask for a source
We name the question first. Then you decide.
Vreko never starts with “connect everything.” Each source request names the claim it could help with and what that source can and cannot establish.
example
What we're trying to establish
“Led the migration of the billing service to a message queue.”
Why this source can help
Repository history may establish implementation and review activity: which changes landed under your account, who reviewed them, and when.
What it cannot establish by itself
Business impact, intent, or sole authorship. Changes under your account can include agent-written code, and a merged change says nothing about its effect.
Then you choose whether to authorize that source, for that claim.
what stays private
Your Passport starts private and stays that way until you approve a view.
Signing in, connecting a source, keeping evidence, and sharing a view are separate actions. Disconnecting a source and revoking a shared view are separate controls.
- Your private Passport and every claim you have not shared.
- Evidence you did not include in a view, and how much there is.
- Your provider credentials and source accounts.
- All of the above from a recruiter who referred you. Referral grants no access.
how the alpha step works
Seven steps, and nothing leaves until step six.
- step 1
Apply
A short screener about the AI-assisted work you do.
- step 2
Invitation
Applications are reviewed. Onboarding is curated and guided.
- step 3
Sign in
Signing in to Vreko does not connect a source or share anything.
- step 4
Name a claim, then authorize a source
See what Vreko is trying to establish and why a source could help, then authorize only that source.
- step 5
Review and correct
Inspect each claim's evidence and state. Accept, edit, dispute, exclude, or drop.
- step 6
Preview and approve one view
Choose a recipient and a purpose, see exactly what they will receive, and approve it or don't.
- step 7
Change or revoke access
Whenever you choose.
what happens next
Apply with the short screener.
Applications are reviewed. If the Alpha is a fit, we contact you to arrange onboarding. There is no install to run first and nothing to buy.
Apply to the Alpha →The Alpha contract is what the Alpha is testing. Which of its controls run in code, are recorded as metadata, or are operated by hand is under independent review before the Alpha opens.
what exists · what is being tested · what is not built
Nothing moves left without evidence.
current
- Receipts have been produced, in recorded runs, from real AI-assisted work on more than one execution host, through one shared emitter, without duplicate provider credentials.
- In those runs each receipt records who authored a change and whether a verifier other than the author was observed. When none was, the receipt says NOT OBSERVED.
- A private Alpha. Applications open, onboarding curated, no public install.
testing
- A Passport that holds evidence and is not published. It is the object under test in the Alpha; no hosted Passport is live today.
- Ask the Passport, answering only from a view the operator approved.
- Whether a hiring reader can read a Passport view in under a minute and name what is still unknown.
- Whether people grant a narrow permission when they see the exact claim it serves and exactly what would leave.
- Whether a small Alpha cohort completes the loop without founder help.
not built
- Public profiles, search, or any recruiter directory.
- Certificates, achievements, scores, rankings, or Vreko acting as an authority on anyone's ability.
- Matching, a job board, or a marketplace.
- Automatic planning of what evidence to gather next. Today that is a person's judgement.