Groundcrew docs
Groundcrew connects to the infrastructure you already run, maps it, deploys your apps, and investigates incidents. It reads freely with scoped access and changes nothing without an approval from your team.
Quick start
Full guideSign in
With GitHub or an emailed link. You get a workspace of your own.
Connect
AWS with a read-only role, GitHub with the app, Vercel or Kubernetes with a token.
Discover
Groundcrew maps your resources and how they connect.
Deploy and fix
Approve deploy plans and incident fixes before anything changes.
Guides
Connect
What each connection can see and do, how to create it, and how to remove it.
Use Groundcrew
The map, deploys from a repository to a live URL, incidents, and who hears about them.
Workspaces
Members and roles, how approvals work, the activity log, limits, and deleting data.
Reference
The full permission model, and answers to the questions people ask most.
Four rules Groundcrew keeps
- It reads with scoped access and never reads secret values or your data.
- Nothing changes your infrastructure until an owner or approver approves the exact plan.
- Fixes go through pull requests on your repositories. It never pushes to your default branch or merges.
- A fix is only called done after Groundcrew checks the signals that showed the problem.