Keep your CI green.
Tell GreenCI what your app is supposed to do, in plain English. It writes the Playwright tests, runs them, fixes the flaky ones, and opens a PR — even if you have zero tests today.
Free plan · No credit card · The tests live in your repo, not ours
Sound familiar?
Your app has paying customers, real traffic — and zero E2E tests. Every deploy is a small act of faith.
The tests you do have fail randomly, so everyone just hits re-run and stops trusting red.
Writing Playwright specs is the chore that loses to the roadmap. Every sprint.
Day one: describe your app. Get a test suite back.
No tests yet? You don't need any. Write down your critical flows the way you'd explain them to a new hire. GreenCI reads your real pages, writes a spec for each journey, runs them against your app, and opens a PR with the ones that pass. You review it like any other PR.
- uses: samarrahTech/greenci-action@v1
with:
api-key: ${{ secrets.GREENCI_API_KEY }}
mode: bootstrap
journeys: |
Sign in with email and password at /login
Search for a product and open a listing
Add to cart and reach the checkout stepRun it once from the Actions tab. Ten minutes later there's a PR with your starter suite.
Every PR after: it maintains itself
Once the starter suite is in, GreenCI rides along on every pull request so coverage grows with your app instead of falling behind it.
You open a PR
GreenCI reads the diff and figures out what actually changed for users.
It writes the tests
New Playwright specs for new flows, updates for changed ones.
Green tests land in your branch
It runs them first. Only passing tests get committed — with a report on the PR.
Set up in 30 seconds.
# .github/workflows/greenci.yml
name: GreenCI
on: [pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: samarrahTech/greenci-action@v1
with:
api-key: ${{ secrets.GREENCI_API_KEY }}
base-url: http://localhost:3000We ran it on this exact page.
The site you're reading is tested by GreenCI. We typed five plain-English journeys into a workflow file, ran it once, and merged the PR it opened — five Playwright specs, four of them self-healed before they ever reached us. They now gate every deploy of this page.
🌱 Foundational E2E suite generated by GreenCI
This PR contains the verified-passing starter suite for your critical journeys. Review it like any code: the tests are plain Playwright and fully yours.
Everything you need
Start From Zero
No tests? Describe your flows in plain English and get a passing starter suite as a PR.
Honest Self-Healing
When a test breaks, it gets fixed. When your app breaks, you get told — we never heal over a real bug.
Lives In Your PRs
Tests are generated, run, and committed inside the pull request. No separate tool to check.
Cypress Migration
Point it at your Cypress suite and get Playwright back, TODO-marked where it needs a human.
Plain Playwright
Everything it writes is standard Playwright in your repo. Cancel anytime and keep every test.
Free for OSS
Open source repos get GreenCI free. Forever isn't a promise we make lightly — it's in writing.
Your code stays yours.
We built GreenCI with security-first principles. Your source code is never stored, shared, or used to train models.
Zero Code Storage
Code is analyzed in memory and discarded. Nothing is persisted beyond your test files.
Self-Hosted (Roadmap)
Coming soon: run GreenCI entirely on your infrastructure so code never leaves your network.
Minimal Permissions
Read-only code access. Write access only to test files. No secrets, no env vars.
SOC 2 Roadmap
Compliance certification in progress. Enterprise audit reports available on request.
Bring your own LLM.
Use your own Anthropic or OpenAI API key — the action calls your provider directly from your CI runner, and your code never touches GreenCI's servers. Bedrock, Azure OpenAI, and Ollama are on the roadmap.
Anthropic
Available now
OpenAI
Available now
AWS Bedrock
Roadmap
Ollama
Roadmap
GreenCI provides the intelligence — prompt engineering, test frameworks, and self-healing logic. You control the AI. On the hosted plan, your code is processed transiently and never stored or used for training. In BYO-LLM mode it goes straight from your runner to your provider.
Built by engineers, for engineers.
We built GreenCI because we were tired of debugging flaky tests at 11pm. Here's why teams trust us.
Years of Testing Experience
Our team has built and maintained E2E suites at scale across multiple industries.
Vendor Lock-In
Generated tests are plain Playwright committed to your repo. Leave anytime and keep every test.
Open Source Runner
The Playwright test runner is fully open source. Audit every line that touches your code.
Before & after
Before GreenCI
After GreenCI
Simple pricing
The free plan is live today. Paid plans open soon — early adopters keep generous limits.
Free
$0
- ✓50 test generations/mo
- ✓Bootstrap + PR modes
- ✓Self-healing included
- ✓Community support
Starter
$39/mo
- ✓500 test generations/mo
- ✓PR integration
- ✓Self-healing included
- ✓Community support
Team
$149/mo
- ✓2,000 test generations/mo
- ✓PR integration
- ✓Self-healing included
- ✓Priority support
Business
$449/mo
- ✓10,000 test generations/mo
- ✓PR integration
- ✓Self-healing included
- ✓Priority support
Enterprise
$999/mo
- ✓Unlimited generations
- ✓Dedicated support
- ✓Custom SLA
Frequently asked questions
On the hosted plan, the GreenCI action sends your PR diff and existing test files to the GreenCI API, where they are processed transiently by our LLM provider to generate tests — never stored and never used to train models. Or use Bring Your Own LLM (Anthropic or OpenAI key): the action calls your provider directly from your CI runner and your code never touches GreenCI's servers.
That's exactly what bootstrap mode is for. Write down your critical flows in plain English — 'sign in', 'add to cart', 'reach checkout' — and run the action once. GreenCI reads your real pages, writes a spec per flow, runs them against your app, and opens a PR with the ones that pass. Most teams go from nothing to a reviewed starter suite in an afternoon.
Anything Playwright can drive in a browser — React, Next.js, Vue, Rails, Django, a 15-year-old server-rendered app, doesn't matter. GreenCI grounds its selectors in your actual rendered HTML, so it doesn't care how the HTML got there.
Yes. GreenCI intelligently scopes test generation to the packages affected by your PR changes.
Absolutely. Tests are added as commits to your PR branch. Review them like any other code change. Nothing merges without your approval.
With ChatGPT, you are the pipeline: gather the context, paste it in, copy the code out, run it, paste the failures back, fix, commit — and remember to do it all again next PR. GreenCI is that loop running by itself. It reads your real pages, writes the tests, runs them against your app, heals what broke, tells you when the failure is a real bug, and commits only what passes — on every PR, including the ones nobody was thinking about tests for. ChatGPT can write you a test. GreenCI keeps your CI green.
Every test has to actually pass against your app before it's committed — we run them, we don't just write them. And when a test fails because your app is genuinely broken, GreenCI says so on the PR instead of quietly rewriting the test until it passes. A healed test that hides a real bug is worse than a failing one; that principle is built into the product.
Your first green suite is one PR away.
Sign in with GitHub, grab an API key, describe your flows. That's the whole setup.
Start free with GitHub →Not ready yet? We ship fast — leave your email and we'll tell you when the big stuff lands. No drip campaigns, promise.
Be the first to join the waitlist