Private repositories. Analyse a private repo, or keep the whole run out of the public showcase.
Verified deployments for Zerops
Analyze a public GitHub or GitLab repository, generate Zerops configuration, deploy it in an isolated environment, and verify that it actually boots.
Used for this run only — never stored, discarded when the run settles. BYOK runs skip the shared token budget. Currently supported: OpenAI, Groq, OpenRouter, or any OpenAI-compatible endpoint — more coming.
A public GitHub or GitLab URL. Nothing is cloned until it passes admission checks.
A rules engine reads manifests and answers first: deployable, needs changes, or not deployable — with evidence.
Built from official Zerops recipes and checked against platform rules. Not deployable yet? You get the exact fix prompt — or an AI-drafted patch.
Deploy to a throwaway project, or into your own Zerops account.
Probe every route the code declares; on failure, diagnose from logs, repair with a visible diff, retry. Every step lands in a replayable timeline.
Steps 1–3 always run and provision nothing, so the configuration arrives in seconds. Steps 4–5 are opt-in — deploying costs time and credits, so it happens only when you press the button.
No source code leaves the worker. A rules engine extracts facts with evidence from manifests and configuration files — the model reasons over facts, not your source code.
check_circle Every fact cites a filename
Generated configuration isn't enough. On request, Zeroth deploys it to a real Zerops project and watches it boot before calling anything verified.
check_circle A failed deployment is reported as failed
Public runs, with whatever result they actually got.
No verified deployments yet
Run your first repository analysis to see it appear here.
Analyze a repository| Repository | Status | Action |
|---|