Post an RFP

Name the software you want to replace, check the features you use, and state what you pay. Sellers bid against that list with a price and a match percent.

Posting more than one tool, or using an AI agent? Post them all at once from one JSON paste.

Fill this in now, no account needed. When you post, you create a free account and the RFP goes up. You can post anonymously. Log in if you already have one.

Let an AI fill this in for you

Instead of checking features by hand, copy this prompt into Claude, ChatGPT, Gemini or any AI agent that can see your account. It works out which features you actually use, then hands back an answer that fills this form in.

then paste it into Claude, ChatGPT or your own agent

Goal: check which of the 17 GitHub Actions features below this account actually uses, then return one JSON object.

If you are posting RFPs for several tools, stop and use /rfps/bulk on the same site instead. It posts every tool from one JSON paste.

You have access to this account (through an open session, an admin export, or an API). Look at real usage: active automations, records in the last 90 days, seat counts, sent volume. Do not guess.

For every feature listed, set "confidence" to exactly one of these three values:
- "used": you found direct evidence this account uses it (a count, a list of active items, a log entry).
- "maybe": the feature is enabled or reachable but you could not confirm real use.
- "unused": you found no evidence, or the account plan does not include it.

Rules:
- Do not mark a feature "used" without a piece of evidence you can name in the "evidence" field (a number, a date, an item name). If you cannot name one, use "maybe" or "unused" instead.
- Do not skip a feature. Every slug below needs one entry in "features".
- Fill "stats" with whatever whole-account numbers you can find (seats, contacts, records). Omit a key you cannot find rather than guessing a number.
- Put one line per notable finding in "notes" (plain text, no markdown).
- Report only figures and feature usage. Do NOT copy contract text, an order form, an invoice, or any wording marked confidential into your answer. The result is published on a public page.

Return ONLY the JSON object below, filled in. No markdown fence, no commentary before or after it.

Output shape:
```json
{
  "v": 1,
  "vendor": "github-actions",
  "scannedAt": "<ISO 8601 timestamp of right now>",
  "features": [
    {
      "slug": "<feature-slug>",
      "confidence": "used | maybe | unused",
      "evidence": "<short evidence string, or omit this key if none>"
    }
  ],
  "stats": {
    "<statName>": "<number>"
  },
  "notes": [
    "<short free-text line>"
  ]
}
```

Worked example, for a feature slug "email-drip-campaigns" where the account runs 12 active sequences:
```json
{
  "slug": "email-drip-campaigns",
  "confidence": "used",
  "evidence": "12 active sequences"
}
```

The GitHub Actions feature list, grouped, follows. Each entry gives the exact slug to use in your output.

## Pipelines
- pipeline-as-code - Pipeline as code: Defines build and deploy pipelines in a file stored in the repository.
- parallel-jobs - Parallel jobs: Runs several jobs at the same time to shorten a pipeline.
- build-matrix - Build matrix: Runs one job across many versions, platforms or configurations.
- pipeline-triggers - Pipeline triggers: Starts pipelines on pushes, pull requests, tags, schedules or API calls.

## Runners & Compute
- hosted-runners - Hosted runners: Runs jobs on vendor-managed Linux, Windows or macOS machines.
- self-hosted-runners - Self-hosted runners: Runs jobs on machines that the customer manages.
- docker-builds - Docker builds: Builds container images and runs jobs inside containers.
- dependency-caching - Dependency caching: Caches dependencies between runs to speed up builds.

## Testing & Artifacts
- test-reporting - Test reporting: Collects test results and shows failures for each run.
- test-splitting - Test splitting: Spreads a test suite across parallel jobs by timing data.
- build-artifacts - Build artifacts: Stores files that a job produces for later download or deploy.

## Deployment & Security
- deployment-environments - Deployment environments: Tracks deploys to staging and production environments.
- manual-approvals - Manual approvals: Pauses a pipeline until a person approves the next step.
- secrets-management - Secrets management: Stores credentials and injects them into jobs at run time.
- audit-logs - Audit logs: Records who changed pipelines, settings and secrets.

## Platform-Specific
- marketplace-actions - Marketplace actions: Reuses community actions as steps in a workflow.
- larger-runners - Larger runners: Runs jobs on bigger hosted machines with more CPU and memory.

1. Copy the prompt.
2. Paste it into Claude, ChatGPT, Gemini or any agent with access to your data.
3. Paste what it gives you back into the box below. You get a link that fills in this whole form.

1Which vendor do you want to replace?

CI/CD

GitHub Actions

CI/CD

3Spend, usage, and details

Everything here is public.

Title *

Description

What you need the replacement to do, timelines, constraints. Sellers read this before they bid.

Current annual spend *

US dollars per year.

Seats

Licensed users. Optional.

Renewal date

When the current contract renews. Optional.

Usage statsOptional. Numbers that size the deal: contacts, emails per month, storage.

Post anonymouslyYour name, company and contact details stay off the public listing. The spend figure, the vendor and the feature list are still public, because that is what sellers bid against. You still see every bid, and you contact the sellers you like.

Posting makes the RFP public and open to bids right away. You can edit it or close it later. Posting is subject to the Terms.

Post an RFP

Let an AI fill this in for you

1Which vendor do you want to replace?

2Which GitHub Actions features do you use?

3Spend, usage, and details