Birdor

Docs

Browse tool docs →

Docs · Platform

Developer Console

The Birdor Developer Console is the control plane for your projects, environments, and API usage. It gives you a calm overview of what's running on Birdor — and a simple way to manage keys, logs, and plans without heavy ceremony.

For a higher-level view of the whole platform, see the platform overview →

Console Structure

The Console is organized into a small set of focused sections:

  • Dashboard — high-level usage and health.
  • Projects — group your usage by app or service.
  • Environments — split dev, staging, and production.
  • API Keys — create, rotate, and revoke keys.
  • Usage & Logs — inspect requests and errors.
  • Billing & Plans — manage your subscription.
  • Team — invite collaborators and set roles.
  • Workspace Settings — naming, regions, preferences.

The goal is to keep the Console predictable and calm: fewer screens, fewer toggles, and a single place to answer "what is going on with our usage?".

Access & Authentication

You access the Console via /console. Authentication is handled via your Birdor account, and each account is associated with one or more workspaces.

  • A workspace is where settings, projects, and billing live.
  • Within a workspace, you can create multiple projects to separate usage.
  • You can invite teammates to your workspace (roles are coming in a later iteration).

Exact authentication mechanisms and SSO options will be documented here as they become available.

Dashboard

The Dashboard is the first screen you see after signing in. It's designed to answer a few simple questions at a glance:

  • Are my APIs healthy right now?
  • How much of my monthly quota have I used?
  • Which tools and projects are most active?
  • Have there been any important recent events?

Usage overview

A small graph of recent requests and errors. It helps you see spikes, drops, or unusual patterns over the last 24h–30d.

Top tools & projects

A ranked list of the tools and projects consuming the most requests, so you know where your quota is going.

Recent activity

API key changes, plan updates, and notable usage events appear here, so you don't have to dig through logs.

Projects & Environments

Projects are a way to group usage logically — per application, microservice, or customer. Each project can have multiple environments, such as:

  • development
  • staging / preview
  • production

This lets you keep keys, logs, and usage isolated per environment while still seeing an aggregated view at the workspace level.

Future iterations may add per-environment alerts, rate limits, and more fine-grained settings.

API Keys & Secrets

API keys are how your backend authenticates with Birdor APIs. In the Console, you can:

  • Create keys scoped to a specific project and environment.
  • Give keys human-readable names (e.g. "prod backend").
  • Revoke keys instantly if they're no longer needed.
  • See when a key was last used.

In a future update, the Console will also include a Secrets section to store environment variables and configuration values securely, alongside your API keys.

Usage & Logs

The Usage & Logs section is where you inspect how your applications are talking to Birdor.

  • Filter by project, environment, tool, status code, or time range.
  • See request counts and error rates over time.
  • Drill into individual log entries for debugging.

In early versions, this focuses on simple, structured logs. Over time, it may grow into a richer log and alerting layer (still with a calm design).

Billing & Plans

The Billing section shows your current plan, usage against quota, and upcoming invoices. The philosophy is the same as elsewhere in Birdor:

  • Pricing should be transparent and boring.
  • The free tier should be genuinely useful.
  • Upgrades and cancellations should never be hidden behind email forms.

Team & Access Control

You can invite teammates into your workspace so they can view usage, manage keys, and help with debugging. Early versions of the Team section are simple:

  • Invite by email.
  • Basic member vs. owner roles.

As the platform grows, more fine-grained roles (e.g. billing-only, read-only) may be added, always with an emphasis on clarity over complexity.

Getting Started with the Console

A typical first-time path through the Console looks like this:

  1. Sign in to Birdor and open the Developer Console.
  2. Create your first project (for your app or service).
  3. Add a production and development environment.
  4. Generate an API key for each environment.
  5. Integrate the appropriate Birdor APIs into your backend, using those keys.
  6. Watch usage and logs populate in the Console dashboard.

From there, you can explore additional tools, enable more APIs, and invite teammates as needed — at your own pace.

Design Goals

The Console is intentionally not a busy enterprise control center. It's a quiet companion for your work — a place to check on things, adjust a few dials, and then get back to building.

As Birdor grows, this page will stay up to date with new sections, screenshots, and API references — but the underlying promise remains the same: calm, developer-first infrastructure.