One team, three products
GateTest gates it.
Gluecron hosts it.
Vapron runs it.
Three independent products. One team behind them. Each one solves a different piece of the "running real software in production without losing sleep" problem — and they're designed to be useful on their own or together. We use these every day, so you can use them every day.
- 01GateTest gates it
121 modules on every push. Failing scans block the merge; paid tiers open the fix PR.
- 02Gluecron hosts it
A git host built around Claude — repos, branches, PRs and webhooks the way an agent expects them.
- 03Vapron runs it
Scheduled jobs and background work at the edge, with zero infrastructure to manage.
The products
Use whichever solves your problem
GateTest
AI writes fast. GateTest keeps it honest.
QA + security audit for your codebase OR your live website. 121 modules covering security, performance, accessibility, SEO, supply chain, AI safety. Pay per scan, not per seat.
- Free preview shows your top 3 issues
- Pay-per-scan from $29 — no subscription required
- Same engine scans your code AND your live URL
- Plain-language report you can hand to anyone
Gluecron
The git host built around Claude.
A git host designed from day one for the era when most of the code is being written by AI agents. Programmatic webhook API, agent-friendly auth, Claude-aware tooling. The platform GateTest itself runs on.
- Repos, branches, PRs — done the way Claude expects them
- Programmatic webhook registration via REST (no clicking through UIs)
- PAT auth that just works for agents
- No code-AI-training opt-in question because there's no opt-in
Vapron
AI-native. Edge-first. Zero ops.
Scheduled jobs, background tasks, and event-driven work that runs at the edge with zero infrastructure to manage. Designed for the agent era — describe what you want done; Vapron runs it.
- Edge-first runtime — close to your users, close to your data
- Zero infra to provision, zero on-call rotation
- AI-native by design — Claude understands your jobs
- Pay only when work actually runs
Why three products instead of one big one
We could have built one mega-product. We didn't, because no real customer wants a mega-product. They want the tool that solves the problem they have right now — and they want to be able to drop it for a different tool tomorrow without unsubscribing from anything.
So we built three small products that share a philosophy but not a billing surface. Use GateTest without ever signing up for Gluecron. Use Vapron without ever touching GateTest. Or use all three. The choice stays yours.
The shared philosophy: pay-per-use where it works, no-subscription-pressure, and brutally honest about what each tool DOES and DOESN'T do.
How they fit together (if you use more than one)
- Code on Gluecron, audited by GateTest: push triggers a scan; failing scans block the merge. Same gate story as a GitHub repo, but on a git host that Claude actually understands.
- Scheduled jobs on Vapron, audited by GateTest: the cron / background work that powers your product gets the same QA treatment as your request-path code. GateTest scans the job definition; Vapron runs it at the edge.
- All three: code on Gluecron, gated by GateTest at push-time, scheduled jobs running on Vapron. End-to-end coverage with three independent tools, three independent bills, three independent failure modes.