Antigravity apps, checked against your rules
Your teams build in Google Antigravity, where agents write, run and test the code. NEKOD checks those apps against your own rules and shows the evidence.
When the rules pass, the app goes to an approver and the decision stays on record.
Book a DemoWhy Antigravity apps need your rules
In Antigravity, agents work across the editor, the terminal and the browser. A domain expert can describe a tool and get a running app back, without waiting on a backlog.
An agent can add a key, open a storage bucket or install a package in the same run. NEKOD checks the app against your rules. Data stays read-only by default, and the builder gets a fix prompt to hand back to the agent.
Stacks Antigravity projects often use
TypeScript / Python
Full-stack languages
React / Next.js / Angular
Frontend frameworks
Firebase / Cloud SQL
Database & auth
GitHub repos
Connect read-only
Node / FastAPI
API backends
Google Cloud / Vercel
Deployment targets
Google Antigravity in your company
- What it is
- An agent-first development environment from Google. Agents write, run and test code across the editor, terminal and browser.
- Who builds with it
- Technical users who describe a tool and let agents build and run it.
- What gets built
- Internal tools and small apps, often with a Google Cloud or Firebase backend.
- Where it lives
- A Git repository, usually with Google Cloud services behind it.
Why use Google Antigravity with NEKOD
Google Antigravity gives your teams
- Agents that write, run and test the app in one run
- A working app from a description
- Work across the editor, terminal and browser
NEKOD gives your company
- Your written rules checked on the result, with the evidence
- A check on what an agent added in the same run: keys, storage and packages
- An owner, a risk level and a recorded approval for each app
How NEKOD works with Google Antigravity
- 01
Connect the repository
Connect the repository the app lives in, read-only. Data stays read-only by default.
- 02
Check against your rules
NEKOD checks the app against your rules, including anything an agent added in the same run.
- 03
Fix with the agent
The builder gets a plain-language finding and a fix prompt to hand back to the agent.
- 04
Approve with a record
When the rules pass, the app goes to the right approver. The decision and the evidence behind it stay on record.
What We Check
Checks against your rules, with fix prompts for the agent
Agent-made changes
Antigravity agents plan, edit several files and run commands on their own. We check what changed across the repository, not just the file you looked at.
Secrets & API keys
Hard-coded tokens, keys in config or test files, and credentials an agent pasted in while it set up a service.
Auth, data & access
Route guards, database rules and session handling an agent added or changed, and the customer data each one exposes.
Infrastructure & dependencies
Storage buckets, cloud configs and packages the agent created or installed, with known vulnerabilities and open access flagged.
A check against your rules, and a fix in the tool your team already uses.
Critical · Security
Agent-created storage bucket allows public read access
Fixed · Security
Agent-created storage bucket allows public read access
Prioritized fix list
Every finding comes with its severity, a plain-English explanation and what to fix next. The builder pastes the fix prompt back into Antigravity.
Applications
- Approved
Supplier onboarding
Owner: Procurement
- Fixes needed
Expense checker
Owner: Finance
- In review
Shift planner
Owner: Operations
Approved by Risk
Supplier onboarding · all checks passed · evidence attached
Approval on record
Approvers see every application with its owner and status. Each decision is recorded with the evidence behind it.
The line that failed
Agent-created storage bucket allows public read access in infra/storage.tf:22
Uploaded files can be opened by anyone with the link
The agent set up file storage that is open to the internet. Make the bucket private and serve files through signed links.
Plain language
Every issue comes with a plain-English title, why it matters, and what to fix, so approvers can follow it too.
Critical · Security
Uploaded files can be opened by anyone with the link
The agent set up file storage that is open to the internet. Make the bucket private and serve files through signed links.
Report assessment
Each check leaves a record: the findings that matter, and a fix prompt in plain language.
Frequently Asked Questions
No. Your teams keep building in Antigravity. NEKOD checks those apps against your own rules, shows the evidence, and records the approval.
NEKOD checks the app against your written policy and names what failed. Antigravity agents edit code, run commands and set up services, so that includes secrets, access rules, and the infrastructure the agent created.
No. NEKOD reads repositories through a GitHub App, and you choose which repositories to share. Access is read-only. NEKOD does not change the code when it checks an app.
The builder gets a plain-language finding and a fix prompt to give back to the agent. After the fix, NEKOD checks the app again. When the rules pass, an approver records the decision.
Book a demo to start a pilot. A pilot starts with one team and about five apps. NEKOD connects to the repositories, checks each app against your rules, and shows the portfolio.
Start with the Antigravity apps your teams already build
NEKOD checks each app against your rules and records the approval.