Validate, format and generate Kubernetes, Kafka, Terraform and Redis config.
Free browser-based tools for the config files cloud work runs on: Kubernetes YAML, Kafka and Redis settings, Terraform, Docker and Compose, MCP servers, IAM and S3 policies, ARNs, CIDR blocks and cron. Paste a file, get the exact line that is wrong and why, in plain language. Everything runs in this tab: no account, no upload, nothing stored.
Browse every tool on one page , or pick a platform below.
Kubernetes
View allObservability
Kafka
View allTerraform
View allCI and automation
Postgres
Docker
View allRedis
View allMCP
View allAI infrastructure
View allEmail and DNS
View allWeb security
AWS
View allAzure
View allGoogle Cloud
View allData formats
View allEncode & decode
View allCryptography
View allIdentifiers
Networking & scheduling
View allCost & compliance
Nothing is uploaded
Parsing and every rule run as JavaScript in this tab. There is no request carrying your input, no storage, and nothing to delete afterwards. Turn off your network and the tools still work.
No account, no email
No sign-up wall, no gated export, no "enter your work email to see your results". Copy the report or download it and go.
Generators check themselves
Every generator feeds its output back through the matching validator on this site and reports the result. Safe defaults are demonstrated in front of you rather than claimed.
From the blog
All postsMCP error -32000 is not in the MCP specification
What -32000 Connection closed actually is, why it is an SDK code rather than a protocol one, why a single print statement causes most of them, and an ordered way to diagnose it instead of restarting the client again.
18 August 2026 MCPMCP structured output is a contract, and most servers keep half of it
outputSchema, structuredContent and the backwards-compatibility rule nobody implements. What the specification actually requires, why isError is not a protocol error, and how to make a tool result a program can rely on.
18 August 2026 MCPYour agent trusts the tool description, and that is the whole attack
MCP tool poisoning explained: which fields of a tool definition reach the model, why reading the description is not a review, why readOnlyHint proves nothing, and what actually reduces the risk once servers are already connected.
18 August 2026 MCPYour MCP tools eat the context before any work starts
Tool definitions are a fixed cost on every request, not a one-off. Why agents degrade instead of failing when you connect too many servers, what the token arithmetic actually looks like, and the four ways to cut it.
18 August 2026Where these come from
Every rule here comes from a specification, an upstream source or a published test vector rather than from received wisdom: Kafka's own generated ConfigDef data, the Avro and protobuf specifications, Kubernetes' deprecated API migration guide, RFC checksum vectors. Where a fact could not be checked against something external, the page says so rather than letting a confident tone imply it was. That distinction is the whole point: a tool reads a file, and a file describes what you meant to build rather than what is actually running.