skeg (n.) the fin that keeps a hull tracking straight

The AI wrote it.
Now prove it’s right.

Your agents ship code faster than anyone can review it. Skeg gives that code a spec to answer to, a review before you push, and a gate it must pass — without changing your IDE, your agent or your model.

Install in 2 minutes Read the docs

any IDE · any agent · any model · self-hosted · free for teams up to five

$ skeg review
comparing 14 files against specs/guest-checkout.md

in scope       guest session, payment intent, tests
out of scope   adds a redis dependency (not in the spec)
risk           card number logged at handler.ts:88
not evidenced  "declines show a retry" — no test

Install

One command. Undoable.

A single binary, no runtime, no account. Run it in any repo you already have.

$ curl -fsSL https://skeg.dev/install.sh | sh

$ cd your-repo && skeg try

You getspecs, gates, agent rules, a PR template and a security scan of your code and git history

Nothing to sign up forno gateway, no login, no data leaves your machine

Changed your mindskeg undo removes exactly what it added

Private beta. Both installers are live and verify every download against signed checksums; the public binaries publish with the first tagged release. Until then, request access and we send you the build and set you up the same day. Full matrix, including air-gapped and from-source, in the docs.

Why

Nothing is broken. Everything is unaccounted for.

None of this is the agent's fault. It did what you asked, at a speed the process around it was never built for.

“Is this what we asked for?”

No spec existed, so nobody can say. Scope creep arrives as a 900-line PR nobody wants to review.

What went out in that prompt?

A key, a customer record, a production connection string. Nobody was watching the wire.

The agent ran `rm -rf`

And you found out afterwards. Agents run commands and call tools; a gateway sees none of it.

How it works

One loop your agents run inside

Skeg wraps the tools you already use. Not a new IDE, not another agent, not another gateway.

Every change answers to a spec

One page with acceptance criteria. skeg review gives the CI verdict before you push; skeg pr does the paperwork. Your agent reads the same spec.

Governed on the wire and on the machine

Secrets stripped before they leave, approved models, per-seat budgets. Plus hooks that stop destructive commands and reads of .env.

Context that outlives the chat

Architecture, decisions and past incidents as markdown in the repo — read by your agent and by the next engineer.

Full quickstart, the admin app and team setup →

Pricing

Free, and not on a clock.

There is no payment system yet, deliberately. Small teams stay free permanently; design partners get everything free for twelve months and help set the price.

Free forever

Up to five builders. No card, no expiry, no seat audit.

Design partners

Ten teams. The whole product free for twelve months, hands-on setup, a call every fortnight.

Later

A platform fee plus seats for builders. Reviewers free. Never per PR, per prompt or per commit.

Open core

Built in the open, with its own gates

Skeg is Apache-2.0 with no CLA — you keep your copyright. Every change here goes through Skeg's own spec, size cap, security scan and review, so if the tool is irritating, contributors feel it before customers do.

Start with a stack pack

Go, Rust, Ruby, PHP, Elixir, Swift. One folder: lint, test, build, CI job, agent rules. No Go code required, and immediately useful to someone.

Or a redaction pattern

Found something the gate lets through? Add the pattern and its canary case, and a release-blocking test protects everyone from then on.

Your PR is low-risk

136 regression checks and an 81-step end-to-end suite, plus an audit that fails the build if this website ever claims something the binary cannot do.

Standard library only, no third-party Go dependencies, and no vendor model default — a CI guard enforces both. What gets merged, and what gets pushed back →

Feedback

Tell us what to fix

One command, from the terminal where the annoyance happened. It shows you exactly what would be sent before anything goes, and it never includes your code, paths or prompts.

$ skeg feedback bug "pr guessed the wrong ticket"
$ skeg feedback suggestion "let me skip the size cap"

Or in writing

Request access

Tell us your team size, which agents you use, and what you would want working in the first week. We reply within one business day.

Open the form hello@skeg.dev

Questions

Do I have to change my IDE, agent or model?

No. Any IDE, any coding agent, and any OpenAI- or Anthropic-style endpoint — hosted, in your cloud, or a model you run yourself.

Can Skeg see our code or prompts?

No. Everything runs in your network. We receive nothing, so we cannot lose it or train on it. Detail, including what is not done yet, on the trust page.

We already have an AI gateway. Does Skeg replace it?

No, it works with yours. Skeg adds the spec and PR gates, the endpoint hooks that see what agents do, and the knowledge base.

Is there a UI?

Yes, for whoever runs the platform: an eight-screen admin app you run locally, plus dashboards in your own network. Developers stay in the terminal. How to run it.

Is there an installer package or .msi?

No, deliberately. Skeg is one executable on your PATH; an .msi would add an uninstall entry, possibly ask for administrator rights, and give you nothing copying a file does not. Windows developers get PowerShell, Scoop or WinGet.

Why “Skeg”?

A skeg is the fin aft of the keel. It keeps a heavy hull tracking straight instead of wandering off the line it was pointed at.

The AI wrote it.Now prove it’s right.