Built it with Antigravity? Let's make sure it's safe to deploy.
Antigravity moves you fast through Google Cloud's surface area. That surface includes IAM roles, service accounts, and Vertex endpoints, all easy to over-scope when you're iterating. We review the permissions and endpoints your code and config define. A full cloud review is part of a Deep dive.
What we look for first
- Service accounts with broader IAM than they need
- Vertex API keys reachable from the client
- Cloud Functions deployed without auth
- Storage buckets defaulting to public read
Illustrative examples. Yours might be cleaner. Or worse.
The Antigravity mistakes we look for.
Four issues we check in every Antigravity-built app, each with the change to make. If any of these sound familiar, you already know why this exists.
Over-scoped service accounts
A service account granted Editor when Storage Object User would do is easy to miss.
Suggested change: Grant each service account only the roles its job needs.
Vertex keys in the bundle
Vertex API keys belong on the server, but one can take a detour through the client during prototyping.
Suggested change: Call Vertex from the server and rotate the exposed key.
Unauthenticated Cloud Functions
Cloud Functions deployed with --allow-unauthenticated are great for demos and terrible for production.
Suggested change: Require authentication on every function that touches data.
Buckets less private than they look
GCS bucket ACLs are deceptively easy to mis-set.
Suggested change: Turn on uniform access and grant reads only through IAM.
How a review works.
Try the free key-leak scan first if you like. When you’re ready for the full review, it goes like this.
You share your code.
Pay once, then send a GitHub link, a public repository URL, or a ZIP of your project.
Day 0
We review it.
We run AI-assisted security checks on your source, review the results by hand, and record what was and was not covered.
Within 5 working days
You fix what matters.
You get a prioritised report in plain English. On request, we send the fixes as a draft pull request or patch. You review, test and merge.
When you’re ready
One price for one project.
Pay once for a review of a single repository. If your stack is bigger than that, we scope it with you first.
Launch scan
PilotOne app, one repo, reviewed by a person.
- High-risk issues that get apps exploited at launch
- API keys, dependencies, config and AI-prompt checks
- Fixes as a draft pull request or patch, on request
- Reviewed by a person, delivered within 5 working days
- Full refund if we cannot deliver a usable report
- A shareable report for investors, teammates or yourself
Scope: one web app or API in a single repository (typical MVP size). Stacks: Node, TypeScript, React, Next.js, Python and most modern frameworks.
$299
One-off, per project. No subscription.
Start with a free lightweight preview, then buy a one-off review of one project. AI-assisted checks are reviewed by a person, and you get a prioritised report in plain English within 5 working days. Fixes can be sent as a draft pull request or patch on request. Review and test any change before you use it.
Payment is handled by Polar.
Deep dive
Custom, scoped together
For several codebases, real infrastructure or a growing team. We review services, environments, cloud, networking and CI/CD, and send a fixed proposal before any work starts.
Talk to usSide by side
| Feature | Launch scan | Deep dive |
|---|---|---|
| Repositories | One | Several |
| Turnaround | Within 5 working days | 1 to 2 weeks |
| Plain-English report | Included | Included |
| Corrected ZIP or draft pull request | Included | Included |
| Cloud and CI/CD review | Not included | Included |
| Optional follow-up reviews | Not included | Included |
| Founder Q&A call | Not included | Included |
Ship it reviewed.
Book the review now, or leave your email and a person will reply within one working day. No commitment and no jargon.