Skip to main content

For teams shipping human- and AI-written code

Pushgate

Your rules.
Before the push.

Make your team’s evidence requirements a condition of accepting a Git push. Give developers and agents a clear reason when a required check is missing.

One repository to start. The same requirements for every contributor.

CHANGE → GATE DECISIONIllustrative example
payments-apiCommit a71f3c2 · Block mode
Build evidence✓ This commit
Scan evidence✓ This commit
Test evidence— Missing
Push refused

Supply the required test evidence, then retry.

Change the evidence. See the decision.

Check the push.

“The tests passed” should come with evidence.

An agent’s summary is a claim. Pushgate checks supplied evidence against the repository’s assigned policy before accepting a push through the gate. Your requirements determine what the change must demonstrate.

Make requirements count

Require the configured build, test, and scan evidence at the Git boundary.

Explain the refusal

Give the developer or agent a reason to act on when evidence does not satisfy the policy.

Grow beyond one gate

Manage connected repository gates and their requirements through the TestifySec platform.

Experimental · Vulnerability detection

See which vulnerable dependencies you actually ship.

Turn it on, and each push with a traced CI/lock build gets an answer on its push card. Each affected dependency says where it was: compiled into your binary, run only by your toolchain, or not placed when the evidence can’t tell. Advisory only. It never blocks a push.

In the binary

Compiled into what the build produced. This is what your customers run, so it goes first.

Toolchain

Your build ran it, and it is not in the output. It can still matter. It is rarely first.

Not placed

When the evidence can’t settle it, the card says so and treats it as possibly shipped. A guess never reads as clean.

  • Placement covers Go, C (static and dynamic), npm, PyPI and crates.io.
  • Filter the push list to what matters: critical or known exploited, in the binary.
  • A push with no traced build says “not checked.” It is never counted as clean.
  • New advisories reach your checks in about 11 minutes.
  • Ask from the command line too: jctl get vulns --image <digest>.
  • Coming next: download the SBOM of a push’s build.
How vulnerability detection works

See the workflow

From missing evidence to a delivered push

Record the required evidence, push through the gate, and confirm delivery for the same commit.

How it works

A clear path from change to decision.

  1. 01

    Connect a repository

    Route its pushes through Pushgate and configure repository permissions to prevent unauthorized bypasses.

  2. 02

    Set the requirements

    Assign the policy that defines the evidence this repository requires. CI/lock captures the checks.

  3. 03

    Check the push

    The gate uses the platform’s policy decision to allow or refuse the push. Inspect the reason and supply missing evidence before retrying.

Follow the product guide

Trust you can explain

Check the evidence. Understand its limits.

A passing decision means the supplied evidence met the configured requirements. It does not prove the code is free of bugs. Trusted evidence producers and repository permissions are part of the trust boundary.

Understand the trust boundary

Before you start

Clear answers.

Go deeper in the docs
How is Pushgate different from the platform?

Pushgate is the checkpoint for Git pushes. The platform manages multiple gates, their policies, identities, and evidence, and connects technical results to controls.

Does this replace code review or CI?

Keep your reviews, tests, and build tools. Pushgate adds an evidence requirement to pushes routed through the gate; it does not replace the checks your team chooses.

Can an agent fabricate evidence?

A signature alone cannot make a false claim true. Your policy must trust an appropriate evidence producer and execution boundary. The trust architecture explains what is checked and what remains an assumption.

Your next step

Put a gate in front of your next push.

Start with one repository and the checks your team already uses.

Set up your first gate