Docs navigationBrowse tools →
Start with browser tools. Pro has no paid delivery today; API and Console documentation describes development capabilities, not guaranteed hosted access. Implemented interfaces and development screens do not imply public production availability, paid access or a completed payment integration. Confirm access with Birdor before connecting an application.
Docs · Platform
Birdor Platform Overview
Map
The Three Pillars: Tools, APIs, Console
System
How the Platform Fits Together
(// Birds-eye view)
Your browser
└─ Birdor Tools (UI-only, mostly client-side)
└─ optional: calls your backend or Birdor APIs
Your backend
└─ Talks to supported Birdor APIs
└─ Authenticated via API keys from the Console
Birdor Console
└─ Manages projects, environments, keys, usage, logs, and plan state
└─ Gives you a single place to understand "what's going on"Phases
Roadmap: From Tools to Platform
Phase 1 · Foundation
- Core tools (JWT, Base64, JSON, URL, time)
- Initial hosted APIs for supported workflows
- Console early access: workspaces, projects, API keys, tasks, and billing state
- Basic usage, logs, and plan guidance
Phase 2 · Services
- Broader automation coverage
- Richer logs and clearer billing state
- Shared workspace access and predefined roles
- Additional hosted API capability families
Phase 3 · Ecosystem
- Birdor Academy & interactive guides
- Templates & snippets
- Tools / API marketplace
- Optional ecosystem extensions once the core platform is stable
Audience
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.
Promise
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.
A narrow, explicit rollout instead of broad promises that outpace the product.
If you want a more narrative take on the long-term vision, you can also read the Birdor Platform Vision.
Ready to decide whether the platform layer fits your workflow? Start with plan boundaries and the early-access shape first, then enter the Console when you actually need workspace state, keys, and request visibility.