Skip to content
Docs navigationBrowse tools →

Docs

Developer tools documentation

Clear, honest documentation for Birdor's browser-first developer tools, what they do, how they work internally, and common usage patterns. All tools run fully client-side and never send data to servers.

Tool documentation

Guides for each Birdor tool, JSON, JWT, URLs, encoding, hashing, IDs, and more. Search by name, behavior, or keywords.

Tool

Browsing 18 records

Search items...

03

Simulate single-user feature flag targeting, rollout bucketing, and rule traces locally before changing production traffic.

feature-flagrolloutexperimentsbucketing

04

Animate consistent hashing ring placement and adding a node, compare key migration with and without virtual nodes, and compare ring, bounded-load, rendezvous, jump and Maglev hashing on balance, hot keys and key movement.

consistent-hashinghash-ringshardingdistributed-systems

09

Generate and decode ULID, KSUID, CUID2, Snowflake, ObjectId, and namespace-derived UUID v3/v5 — plus a side-by-side comparison of sortability, length, embedded time, index-friendliness, and privacy risk across every id format.

ulidksuidcuid2snowflake

11

Compute MD5, SHA-1/2/3, Keccak, BLAKE, CRC32, HMAC and Argon2 / bcrypt / scrypt password hashes for text or files of any size, with side-by-side results and hash comparison.

hashshamd5sha3

13

Mask emails, phone numbers, IPs, JWTs, database connection strings, and API keys in text or JSON before sharing logs or asking an AI.

desensitizemaskredactprivacy

14

Convert curl commands to Python, JavaScript, TypeScript, Go, PHP, Ruby, Java, and Rust code — or turn a fetch/axios/requests snippet back into curl. Handles multipart file uploads, auth, and quoting edge cases locally in your browser.

curlpythonjavascripttypescript

15

Validate, lint, canonicalize, diff, and preview Swagger/OpenAPI specs, or export them to Markdown, JSON Schema, and Zod — without leaving your browser.

swaggeropenapiapidocs

How these tools work internally

A quick overview of the architecture and design philosophy behind Birdor's browser-first tools.
01

100% client-side:

tools run in your browser and never upload data.

02

Privacy-first:

no analytics, logging, or storage unless explicitly chosen by the user.

03

Performance-oriented:

heavy operations optimized, including JSON parsing, Base64, and cryptographic hashing.

04

Deterministic UI:

predictable, consistent results, even for malformed input.

05

Minimalist design:

clean, distraction-free interfaces meant for real developer workflows.

When to move from tools into the platform layer

Birdor keeps one-off work free and browser-first. Move further only when the same workflow becomes something you repeat, save, or run from your own systems.

The next step is not to open the console immediately. Start by reading how the platform layer works, then compare plans, and only move into Pro or Console surfaces when you need supported repeatable workflows, scoped API keys, or request visibility.

Related

  1. 01Browse all toolsGuides for each Birdor tool, JSON, JWT, URLs, encoding, hashing, IDs, and more. Search by name, behavior, or keywords.
  2. 02See recent updatesBirdor keeps one-off work free and browser-first. Move further only when the same workflow becomes something you repeat, save, or run from your own systems.
  3. 03Back to documentation homeA quick overview of the architecture and design philosophy behind Birdor's browser-first tools.