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 →
Launch a tool
Tip: press 1–8 to open one- 1Kubernetes HelperGenerate / validate Deployment, Service, Ingress YAML.
- 2Docker Compose HelperGenerate / validate compose.yaml with healthchecks.
- 3Dockerfile LinterCheck for unpinned images, root containers, large COPYs.
- 4Cron BuilderBuild cron expressions with guided UI and previews.
- 5.env ConverterConvert between .env, .properties, JSON, bash export.
- 6YAML ValidatorSyntax errors with line/col, multi-doc support.
- 7JSON ↔ YAMLConvert API responses and configs locally between JSON and YAML.
- 8Compare EnvironmentsMulti-mode env diff: .env, ConfigMap, YAML, JSON, headers.
Run a workflow right here
Runs locally — nothing is uploadedYAML Config Secret Scan
Convert a Docker Compose / Kubernetes / GitHub Actions YAML to JSON and flag secret-like values.
json-yaml → secrets-scannerConfig: YAML to JSON
Convert YAML config (Docker Compose, Kubernetes, GitHub Actions) into JSON.
json-yamlTrack a checklist
Progress is saved on this deviceDaily tasks, guides & FAQ
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
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. Everything runs 100% in your browser — no analytics scripts, no cookies, no third-party requests. We count anonymous visits at the CDN edge only. That means you can validate and inspect config safely without it leaving your machine.
FAQ
Are my manifests or config files uploaded?
No. Everything runs 100% in your browser — no analytics scripts, no cookies, no third-party requests. We count anonymous visits at the CDN edge only. 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