Catch store rejections
before you submit.
Vera reads your codebase, flags App Store and Google Play policy issues — including the semantic ones a linter can't see — explains each finding against the guideline it comes from, and opens a pull request to fix it.
Private beta. Onboarding in small cohorts.
Findings
Run a scan to audit this repo against 217 store checks.
01 / The problem
Store policy is checked after you submit.
Apple and Google review against hundreds of guidelines that change throughout the year — reporting flows for user content, payment rules, account deletion, data-safety declarations. Most teams first learn a rule exists from the rejection notice, then fix, resubmit, and wait for another review.
Today
- Guidelines read manually, from memory, per release
- Issues surface in the rejection notice, after review
- Each fix costs a resubmission and another wait
- Policy changes tracked by hand, if at all
With Vera
- Policy issues surface in your code, before submission
- Each finding cites the guideline it comes from
- Fixes arrive as pull requests you review
- Rules stay current as the stores update them
02 / The swarm
Hundreds of small agents. One verdict.
Every scan dispatches a swarm of specialized policy agents across your codebase — each one holds a single store rule and checks it against what your app actually does. Semantic rules included: if you have user content, an agent is looking for the report flow.
217 agents dispatched per scan idle
03 / How it works
Connect once. Checked on every commit.
Four steps. Read-only until you accept a fix.
- 01 Connect Link your GitHub repo. Read-only.
- 02 Scan Vera learns what your app is — and what’s wrong.
- 03 Ask & fix Understand every issue. Patch it with a PR.
- 04 Stay guarded Every commit. Every policy update.
Connect
Your repo. Two minutes.
Connect a GitHub repository and grant read access. Vera never trains on your code and never merges without you.
Scan
Reading the whole project · modeling what the app does
Not a checklist. Vera understands you’re a social app with payments — then applies the rules that follow from that.
Ask & fix
Stay guarded
✓ Safe to submit
Vera watches every push and every store policy change. The next rejection never makes it to Cupertino.
04 / What Vera does
It reads your app like a reviewer would.
Then it reports each policy issue it finds — with the guideline it comes from.
05 / Ask Vera
Every finding,
explained.
Ask why a rule applies to your app, what specifically is missing, or how to fix it. Each answer cites the guideline and points at your code.
06 / Fix
From finding to pull request.
Vera writes the fix. You review it. You ship.
Finding
No way to report user content
Guideline 1.2 · Sources/Feed/PostView.swift
✓ Patched — builds clean, checks pass
Agent
Sources/Feed/PostView.swift
Menu {+ Button("Report post", systemImage: "flag") {+ showReportSheet = true+ } Button("Share") }
Pull request
Add report flow #142
✓ checks passed
07 / Always on
Stays current as
the rules change.
Apple and Google update policy throughout the year. Vera re-checks every commit against the latest rules and flags anything new.
Toggle the violation, then push.
08 / Private beta
Get in line — or get in first.
Join the waitlist free, or reserve early access for $10 and get Vera before everyone else.
Get in line, get updates
- Early-access invite when your spot opens
- Launch updates & behind-the-scenes
- Access when general beta opens
- Standard pricing at launch
Bought early access? Paste the code from Stripe here.
Reserved: you get Vera first at launch
- Early access at launch — you’re in before the waitlist hears about it
- Founding price locked forever — 50% off any future plan, for life
- Direct Slack/Discord line to the founders
- Your name in the CLI credits vera --founders
- Covered by a full, no-questions refund policy
After checkout, Stripe gives you a code — enter it when you join the waitlist.
09 / FAQ
Questions, answered.
Does Vera guarantee my app gets approved?
No tool can promise a human reviewer will say yes. What Vera addresses is the preventable category: published rules you didn’t know applied to your app. If it’s in the guidelines and visible in your code, Vera finds it, explains it, and helps you fix it before you submit.
What happens to my code?
Vera connects with read-only GitHub scopes. Your code is indexed and embedded for analysis inside an isolated environment, never used to train models, and deleted if you disconnect. Auto-fix writes go through pull requests you review — Vera never pushes to your branches directly.
Which frameworks are supported?
Native Swift/SwiftUI and Kotlin/Compose, plus React Native, Expo, and Flutter at launch. If your app builds for the App Store or Google Play, Vera can audit it.
How is this different from a linter or a checklist?
Linters match patterns; checklists match memory. Most rejections are semantic — "your app has user-generated content, so it needs a reporting flow" isn't a regex. Vera's agents understand what your app does, then apply the rules that follow from that. It also stays current: when Apple or Google change policy, your next run already knows.
What does the $10 early access actually get me?
You pay on Stripe, get an early access code, then join the waitlist with that code. You’re in at launch before the waitlist hears about it. Founding price locked forever — 50% off any future plan, for life. Direct Slack/Discord line to the founders, your name in the CLI credits (vera --founders), and a full no-questions refund if you change your mind.
When does access open?
Early-access members get Vera first at launch. Waitlist members get in when general beta opens, in order. Both lists get launch updates and behind-the-scenes notes in the meantime.