Explore Resources
Many tools for developers have similar inputs but can be categorised by what they do with that input. This page provides an overview of how our tools at Yoryantra can be used for formatting, parsing, validating, transforming, analysing, generating, comparing or checking inputs. We also explain when you will need to go beyond the browser.
Browse by Topic
Discover practical guides on DevOps, encoding, JSON, security and SEO. Including explanations, examples and tools from Yoryantra to assist you with common tasks, understanding and troubleshooting.
Developer Workflows
Know when to use a parser, formatter, builder, converter and request debugger.
Read the guide →DevOps Resources
Read and understand Docker, Kubernetes, environment, cron, DNS and CI config files.
Read the guide →Encoding Guides
Understand the differences between bytes, unicode, base64, percent encoding, entities and url safe versions.
Read the guide →JSON & Data Guides
Understand how to parse, validate, compare, query and convert data to keep the correct meaning.
Read the guide →Security Guides
Understand the difference between decoding, verifying, hashing and authenticating, along with the difference between generated headers and actual security measures.
Read the guide →SEO Resources
Debug your crawl, index, canonical, redirect, hreflang, sitemap and search snippet signals.
Read the guide →What do different tools do?
There are often small differences in the name of the tools which can have a big impact on what they actually do.
Inspection vs validation
Inspection will expose the structure. Validation will answer a very specific question about whether it is valid according to a syntax, schema or documented rules.
Encoding vs securing
Encoding will change the format of the data so it can fit into another context. However it will not provide any secrecy, authenticity or trust.
Generation vs verification
A generator can create something that looks valid. A verifier will check that a value already exists meets a specific rule or cryptographic requirement.
Static vs runtime
By pasting in text and having a local config you can catch lots of errors. However there is still runtime state when dealing with HTTP, DNS, containers, clusters and browsers.
Use Cases
If your goal is to determine if text is valid JSON, use a validator. If your goal is to determine if valid JSON conforms to an API contract, use a schema validator. If your goal is to determine what has changed between two payloads, use a diff. By using one in place of another you may get a technically accurate result but to the wrong question.
Be aware of the limitations of tools. Whilst some tools will work purely on the text/bytes you provide others will rely on browser APIs or external data. You can’t guarantee that a configuration will work in deployment by checking it is valid. You can’t guarantee that an SEO tag will be indexed or shown by a search engine by generating it.
Return the results to the system that actually makes the decision. Your API, runtime, browser, container engine, cluster, DNS provider, application security policy or search platform. Yoryantra is best used as a focused inspection and preparation tool.
Prefer to browse directly?
If you know what area you're looking for use our category pages. If you know the exact tool you want use our full tools page.