Birdor Platform Overview

Birdor is growing from a collection of calm, focused tools into a developer-first toolkit + API platform. This page gives you a high-level view of the platform — how Tools, APIs, and the Developer Console work together, and where the platform is heading.

If you just want to browse individual tools, jump to the tool docs overview →

The Three Pillars: Tools, APIs, Console

Birdor is built around three tightly connected layers:

Pillar 1

Tools — browser utilities

Small, focused tools that run entirely in your browser: JWT debugger, Base64 utilities, JSON diff, URL parser, timestamp converter, UUID/NanoID, hash utilities, and more.

No sign-in required, no ads, no tracking — just calm utilities that solve real problems.

Explore tools →

Pillar 2

APIs — capability hub

The same capabilities used in tools are exposed as simple, stable APIs. Your backend can hash payloads, decode JWTs, diff JSON, parse cron expressions, and more — all via HTTP.

APIs are designed to be boring in the best way: predictable, well-documented, and easy to integrate.

API reference will live under /docs/platform/api.

Pillar 3

Developer Console — control plane

A calm dashboard where you manage projects, environments, API keys, usage, logs, and billing. Console is the control plane for everything you run on Birdor.

It's intentionally minimal: just enough surface area to keep you in control, without turning into a complex cloud console.

Learn about the Developer Console →

How the Platform Fits Together

At a high level, Birdor's architecture is simple on purpose:

// Birds-eye view

Your browser
  └─ Birdor Tools (UI-only, mostly client-side)
       └─ optional: calls your backend or Birdor APIs

Your backend
  └─ Talks to Birdor APIs (Hash, JWT, JSON diff, cron, etc.)
       └─ Authenticated via API keys from the Console

Birdor Console
  └─ Manages projects, environments, keys, usage, logs, billing
       └─ Gives you a single place to understand "what's going on"

The goal is to keep Birdor small, composable, and easy to reason about. You can use Tools without touching APIs, or use APIs without ever opening a tool again — but the best experience comes when you connect all three.

Roadmap: From Tools to Platform

Birdor's platform roadmap is intentionally incremental. The platform will grow in layers, instead of trying to launch a huge surface area all at once.

Phase 1 · Foundation

Core tools (JWT, Base64, JSON, URL, time)
Initial APIs for key capabilities
Console v1: projects, environments, API keys
Basic usage & logs

Phase 2 · Services

Secrets management
Webhook delivery & retries
Richer logs & soft alerts
Team access & roles

Phase 3 · Ecosystem

Birdor Academy & interactive guides
Templates & snippets
Tools / API marketplace
Lightweight edge functions (optional)

Who the Platform Is For

Birdor is designed first for individual developers and small teams:

Indie hackers shipping small products
Backend & API engineers who want clean building blocks
Frontend engineers who need quick, honest tools
Curious developers learning JWTs, hashing, timestamps, and more

Larger teams and companies are welcome too — but the platform is intentionally not enterprise-first. The primary goal is to stay friendly, understandable, and calm.

What You Can Expect from Birdor

No ads, no intrusive banners, no dark patterns.
A meaningful free tier, not just a demo checkbox.
Clear, honest docs about what we store and how we behave.
A product that aims to reduce friction instead of adding more.

If you want a more narrative take on the long-term vision, you can also read the Birdor Platform Vision.

Ready to see how this shows up in the product? Open the Developer Console →