Open source · pre-release · on GitHub

The ops crew
you didn’t hire.

From a GitHub repository to a hardened production deployment on your own cloud, keeping the infrastructure code.

terminal — habit-tracker
1$ npx opscrew scan
2◆ Scanning the repository
3✓ Wrote opscrew/SECURITY_SCAN.md and .opscrew/scan.json.
4OpsCrew scan of habit-tracker: 2 critical, 2 high, 1 medium, 0 low, 0 info
5 CRITICAL Committed .env file with 3 values .env:1
6 CRITICAL Supabase service-role key in client code src/lib/admin.ts:4
7 MEDIUM .env files are not in .gitignore .gitignore
8Full report: opscrew/SECURITY_SCAN.md
9Next:
  • 8Agents in one crew
  • SHA-256Each plan approved by hash
  • FreeTo scan your repo, no AI

capabilities

Hardened from day one

Not just a server — the whole path to production.

Plans before every change

Agents that read your repository

OpsCrew reads how your app is built: frameworks, services and environment variables. It asks only what it cannot tell, such as traffic and region.

Features

From Repo to Hardened Production

From reading your repository to checking the live site — agents that handle the DevOps work.

Pull Requests First

Code changes arrive as pull requests, with the branch and diff, ready for your review.

Deeper Security Audits

Lynis, ssh-audit and testssl.sh give a second, independent opinion, from pinned versions, for free.

Secure by Default, Rechecked

OpsCrew hardens every server it creates and checks it again whenever you run opscrew secure.

Plain Files You Keep

Everything OpsCrew writes is a plain file in your repository, yours to keep.

Language Support

Node.js, Python, Go, Java, Ruby, Rust and more, each with a fitting builder.

Agents

Meet Your Ops Crew

Specialized agents that work together on every step of shipping your app, from reading your repo to checking the live site.

How it works

From Repo to Production in Approved Steps

Read the app, approve the plan, then deploy and check. Nothing changes without approval.

  1. Run it in your app's repository. The agents read how the app is built and ask only what they cannot tell.

opscrew status

The web process (app)PostgreSQL (db)Proxy: Caddy
  • analyzeok
  • interviewok
  • adaptnot run

Why OpsCrew

Three Ways OpsCrew Keeps You in Control

OpsCrew handles the repetitive operations work, so you and your team can focus on the app.

  • Image scan with Trivy (security.imageScan)
  • Rolling deploys (deploy.strategy)
  • Dependabot updates (.github/dependabot.yml)
  • Keep the newest 10 images (cicd.imageRetention)

Works with

Works with the tools you use

OpsCrew uses the accounts and tools you already have, and leaves everything it sets up in them, as plain files.

  • Hetzner CloudServers on your own account, created from an approved OpenTofu plan
  • DigitalOceanDroplets on your own account, planned with OpenTofu or Terraform
  • PortainerDeploy into the Portainer you already run, through its API
  • CloudflareDNS, TLS and origin protection, applied as plans you approve
  • GitHubPull requests, deploy secrets and Actions workflows for every merge
  • Claude CodeWorks as a plugin with an MCP server for every step

Pricing

Free Core, Hosting Planned

Free, open-source CLI and plugin; AI on your own key, no markup. Hosting is planned.

  • Pro

    Planned

    $9/month

    Includes:

    3 projects, then $3 each

    Scheduled drift and security checks

    Uptime, spend and domain alerts

    Credential vault

    Deploy history and rollback

    Follow on GitHub
  • Agency / Enterprise

    Planned

    Custom

    Everything in Team, plus:

    Single sign-on (SSO)

    White-label for client work

    Self-hosted option

    SLA

    AI on your own key, no markup

    Follow on GitHub

Get started

Read the docs, then follow along on GitHub.

OpsCrew is not on npm yet. Run it from a clone today, or wait for the release.

Read the Docs →