Developer tools for DevOps and SRE
Validate manifests, build schedules and inspect config without uploading infrastructure files — everything runs locally in your browser.
Run the YAML Config Secret Scan workflow → Browse DevOps tools →
Common daily tasks
- Validate a Kubernetes manifest
- Check a Docker Compose file for risky settings
- Lint a Dockerfile for best practices
- Build/verify a cron schedule across platforms
- Convert and compare .env files
- Scan a config for hard-coded secrets
Recommended workflows
- YAML Config Secret Scan — convert a Compose/K8s YAML to JSON and flag secret-like values.
- YAML to JSON — convert a YAML config to JSON for diffing/validation.
Top tools for DevOps and SRE
Kubernetes Manifest Helper
Validate and inspect Kubernetes YAML manifests locally before applying them.
Validate a manifest →Docker Compose Helper
Check Docker Compose files for risky settings and common configuration issues.
Check a Compose file →Dockerfile Linter
Lint a Dockerfile against best practices to catch layer order and security issues.
Lint a Dockerfile →Cron Builder
Build and analyze cron expressions for Unix, Quartz, GitHub Actions, AWS and Kubernetes.
Build a cron expression →Browse all DevOps & config tools →
Why browser-local matters for DevOps and SRE
Infrastructure manifests and config files often contain environment variables, service account keys and other secrets. Your pasted tool data is processed locally in your browser and is not uploaded for tool processing. That means you can validate and inspect config safely without it leaving your machine.
FAQ
Are my manifests or config files uploaded?
No. Your pasted tool data is processed locally in your browser and is not uploaded for tool processing, so Kubernetes manifests, Compose files and .env contents stay on your machine.
Can I check a cron expression's next run times?
Yes. The Cron Builder/Analyzer shows the next run times in your timezone and supports Unix, Quartz, GitHub Actions, AWS EventBridge and Kubernetes formats. Note that AWS EventBridge and GitHub Actions run in UTC, so convert local times before saving.
How do I find hard-coded secrets in a YAML config?
Run the YAML Config Secret Scan workflow: it converts the YAML to JSON and flags secret-like environment values.
Can I convert a .env file to JSON or YAML?
Yes. The .env Converter translates between .env, JSON, YAML and properties formats locally.
Related
- Security engineers — scan secrets, sanitize logs, verify signatures.
- Data / QA engineers — compare exports and clean datasets.
- DevOps & config tools — the full tool set.
- AWS EventBridge cron expression format