Skip to content
Gated

GitHub private preview

Your agent asks. You decide.

Review one explicitly routed GitHub branch request at an existing commit (a saved repository version), approve it when policy requires, and verify the result. Direct credentials can bypass Gated.

Private preview · non-critical GitHub pilot

Check preview access See the GitHub workflow

The supported pilot

Review. Approve. Execute. Verify.

Create one uniquely named branch at an exact existing commit in a selected non-critical repository.

  1. 01

    Review

    Inspect the repository, new branch name and exact commit.

  2. 02

    Approve

    Authorize this request with a passkey when policy requires it. Approval does not start execution.

  3. 03

    Execute

    Explicitly request execution through the scoped GitHub App path.

  4. 04

    Verify

    Inspect the receipt and independent branch/commit readback. Reconcile an uncertain result before retrying.

Before your first run

  • A non-critical GitHub repository you administer, with an existing commit.
  • A configured coding agent using Gated’s scoped credential, rather than direct GitHub tools.
  • A passkey for sensitive setup and human approval. Branch creation may trigger repository workflows.
Full requirements and limits
Explore the broader policy model

Illustrative only. Deployment and database workflows are outside the GitHub pilot.

Illustrative policy decision · sample data

Choose a request

Agentrelease-agent
Actiondeploy
Resourceapi-service
Environmentproduction

Matched policy

Production deployments require a release owner

Decision

Approval required

Reason

Production changes need a specific human authorization.

Enforcement consequence

The action waits at the gate for a release owner.

The broader problem · conceptual

Tool access isn’t permission for every action.

A repository credential, deployment tool, or database connection often permits more than the agent should do. Gated is designed to make the intended boundary explicit.

Repository access

May include

Read an issue

But not automatically

Delete a protected branch

Deployment access

May include

Deploy to staging

But not automatically

Promote to production

Database access

May include

Inspect schema

But not automatically

Delete production data

Broader platform model · conceptual

Define the rules. Make the decisions clear.

Gated is intended to evaluate who is asking, what they want to do, where they want to do it, and which policy applies—before a trusted integration enforces the result.

Identityrelease-agent
Requested actiondeploy api-service
Policy evaluation
DecisionRequire approval
Trusted enforcementdeployment integration

Policy

Rules determine allow, deny, or require approval from request context.

Approval

A specific human authorization for a specific sensitive action.

Decision record

The request context, matched policy, outcome, and reason.

Supported scope

Start with GitHub.

GitHub: Private preview. Create one uniquely named branch at an exact existing commit in an explicitly selected pilot repository. Review each client’s scope in the integration catalog; explicit routing does not intercept other agent actions.

Review GitHub pilot requirements
Integration scope and roadmap

Planned integrations (Ollama, NVIDIA NIM, Vercel, AWS, PostgreSQL) are unavailable for pilot use. Adapter foundations are not verified live-provider support.

View current scope and availability

Developer experience

Put permissions where actions happen.

A conceptual request carries identity, action, resource, and environment. The response explains the policy result and reason; a separate trusted path enforces it.

Explore the developer model
Illustrative request / decision flow
request
  identity     release-agent
  action       deploy
  resource     api-service
  environment  production

decision
  result       REQUIRE_APPROVAL
  reason       Production release owner required

This is conceptual sample data—not a published API or SDK.

Security approach

Clear boundaries. Explicit control.

The intended model separates a policy decision from execution. Control depends on a trusted, scoped path that can enforce the result.

Read the security approach

Scoped authority

Limit the authority available to each controlled path.

Decision clarity

Record what was requested, which rule matched, and why.

Coverage limits

Actions outside a trusted enforcement path remain outside Gated’s control.

Practical resources

Prepare one workflow you can explain.

Check whether the GitHub pilot fits your needs, review one branch request, and decide what evidence you will inspect afterward.

Plan your first pilot →

Follow the requirements and access steps for a non-critical repository.

Review the exact branch request →

Use the repository, branch and full existing commit as your review fields.

Handle an uncertain result →

Reconcile the execution record and provider state before retrying.

Browse guides and worksheets

Preview updates

Follow what comes next.

Join the waitlist for updates. This does not apply for access or reserve a Founding place.

Private-preview updates · Joining does not grant immediate access

By submitting, you acknowledge the privacy notice.