Skip to content
DEDataEngUtils

DataEngUtils for Backend Engineers

Backend Engineers spend their time on the server side: debugging tokens, encoding payloads, formatting API responses, testing regex and generating mock data. Each of those traditionally means a web tool that asks you to paste sensitive values into someone else's page. DataEngUtils runs the same utilities in your browser on a client-side engine, so credentials, tokens and production responses never leave your machine. This page groups the tools that map to a backend engineer's daily workflows.

Tools for backend engineers

Workflow: Debug tokens and connection strings

Inspect JWTs and split database connection strings without exposing credentials to a third party.

  1. 1. Decode a JWT

    Paste the token from an authorization header into JWT Debugger — decoded locally.

  2. 2. Split a connection string

    Use Connection String Parser to break a database or Redis URI into host, port, database and parameters.

  3. 3. Inspect opaque payloads

    Use Base64 Encode / Decode to check encoded values you see in logs or headers.

Workflow: Validate API responses

Format JSON, validate it against a schema and diff two responses when behaviour changes.

  1. 1. Format the response

    Paste a raw response from curl or Postman into JSON Format / Validate.

  2. 2. Validate the shape

    Use JSON Schema Validator to enforce the response contract.

  3. 3. Diff two responses

    Use Text Diff Checker to pinpoint what changed between versions.

Workflow: Generate fixtures and mock data

Create realistic test rows and mock SQL inserts for local development and staging.

  1. 1. Generate test rows

    Use Test Data Generator to produce mock rows as JSON or CSV from a field spec.

  2. 2. Produce mock SQL

    Use Mock SQL Data to turn a CREATE TABLE into INSERT statements with realistic values.

  3. 3. Seed identifiers

    Use UUID Generator and Hash Generator for stable test IDs and checksums.

Frequently asked questions

Is the JWT Debugger safe for production tokens?
Yes. Tokens are decoded entirely in your browser; nothing is sent over the network. That is a meaningful difference from web-based debuggers that transmit tokens to a server.
Can I generate mock data at volume?
Yes. Test Data Generator and Mock SQL Data produce batches of rows from a field spec or a CREATE TABLE, entirely offline.
Does it handle large payloads?
The encoding tools handle large text payloads, and the file tools use a Rust engine compiled to WebAssembly for structured files up to 1.5 GB.