Dashboard

Manage projects, assets, pipelines, and team members in the PichaFlow Dashboard.

The PichaFlow Dashboard is your central command center for managing Projects, assets, API keys, and edge-native image processing pipelines.

Projects & Teams

PichaFlow organizes resources into Projects. A Project is an isolated container with its own dedicated database and unique namespace. All projects share a single global storage bucket, with each project's assets namespaced by its unique identifier.

Managing Projects

You can switch between projects using the Project Switcher in the top navigation. All projects under your account share your account-level billing plan (e.g., a Pro subscription covers all your projects). Each project tracks its own usage quota independently, and usage is pooled across all projects against your account's total limit.

Team Collaboration

Invite teammates to your project via the Team tab.

  • Owner: Full control and billing responsibility.
  • Admin: Can manage assets, pipelines, and keys.
  • Member: Can upload and manage assets.
  • Viewer: Read-only access to analytics and media.

Sending Invitations

When you invite a new member, they will receive an email with a secure link.

!IMPORTANTInvitations are time-limited. For security purposes, all invitations expire 48 hours after being sent. If a link expires, you will need to revoke the old invitation and send a new one.


Media Management

The Media tab allows you to upload, organize, and inspect your assets for the active project.

Uploading Assets

You can upload images directly via the web interface or using our SDK and API. Every uploaded asset is stored in Cloudflare R2 within your project's isolated storage bucket.

Organizing with Directories

PichaFlow supports directory-based organization for your media assets. You can create folders (e.g., products/hero/, blog/thumbnails/) to keep your library structured as it grows.

Creating Directories

Click the "New Folder" button in the Media Gallery to create a directory at your current location. Directories can be nested to any depth.

Uploading Into Directories

When you navigate into a directory, clicking "Upload New Asset" will automatically place the new image into that folder. You can also specify a directory when uploading via the SDK or HTTP API.

Browsing

Use the breadcrumb navigation at the top of the gallery to move between folders. Folders appear before images in both Grid and List views.

URL Permanence: Once an asset is uploaded, its directory path becomes part of its permanent delivery URL. You cannot move or rename assets between directories after upload — doing so would break any live links. Choose your directory structure carefully before uploading.

Supported Operations

ActionSupportedNotes
Upload into a directorySet at upload time via Dashboard, SDK, or API
Browse & navigate foldersBreadcrumb UI with Grid/List views
Create empty directoryVia "New Folder" button
Delete empty directoryDirectory must be empty first
Move assets between directoriesWould break live delivery URLs
Rename directoriesWould break live delivery URLs

AI Alt-Text

When an image is uploaded, PichaFlow automatically generates descriptive alt-text for SEO and accessibility. You can manually override these descriptions in the asset details view.


WASM Pipelines (Architect)

Pipelines are the core of PichaFlow's performance advantage. They allow you to define a sequence of image transformations that run at the Edge using WebAssembly.

Creating a Pipeline

Navigate to the Pipelines tab and click "Build New Pipeline".

  1. Define Steps: Add transformations like resize, grayscale, blur, or brightness.
  2. Stacking: Operations are executed in the order you define them.
  3. Presets: Once saved, your pipeline is deployed to the global edge network as a "preset" for your specific project.

Using a Preset

To apply a pipeline to an image, append the preset parameter to its delivery URL: https://cdn.pichaflow.com/asset-id.jpg?preset=hero-banner


API Keys & Security

Manage your project access tokens in the API Keys tab.

  • Public Keys: Used for client-side uploads (restricted by domain).
  • Secret Keys: Used for server-side management and deletions. Never expose these in client-side code.

API Key Quotas

Each individual project is allowed up to 3 API key pairs to cleanly isolate Development, Staging, and Production environments (Hobby tier is capped at 2 keys/project for a 1 Dev + 1 Prod setup).

Across your entire account tier, key limits scale as follows:

  • Hobby Plan: 2 API key pairs (1 Project max).
  • Pro Plan: Up to 15 total API key pairs across projects (Max 3 keys per project across 5 Projects).
  • Scale Plan: Up to 60 total API key pairs across projects (Max 3 keys per project across 20 Projects).
  • Business Plan: Up to 300 total API key pairs across projects (Max 3 keys per project across 100 Projects).

To prevent other websites from embedding your images and draining your bandwidth/transformation limits, PichaFlow allows you to specify Allowed Domains. Only domains in this list will be permitted to fetch your assets.

Strict Referer Blocking

By default, PichaFlow allows requests that have no Referer header (e.g., <img> tags on sites with strict privacy settings, or direct programmatic downloads via cURL).

If you want absolute certainty that no automated scrapers can fetch your images by spoofing an empty Referer, you can enable Strict Referer Blocking in your General Settings.

!WARNINGHeadless Breakage: Enabling Strict Referer Blocking drops all requests without a Referer header. This breaks direct cURL scripts, programmatic API downloads, privacy-conscious browsers (e.g. Brave in strict mode), and sites using <meta name="referrer" content="no-referrer">. Only enable this if your images are exclusively loaded by modern browsers on your specific allowed domains.


Security & Audit Logs

For Business and Enterprise accounts, PichaFlow maintains a comprehensive, tamper-proof Audit Log of all mutations made within your project.

This includes:

  • API Key generation and revocation.
  • Project setting modifications (e.g., AI Shield sensitivity).
  • Media and directory deletions.
  • Team member invitations and role changes.

!IMPORTANTData Retention Policy: To balance security visibility with data privacy, all audit logs are retained for exactly 90 days. PichaFlow employs a daily automated cleanup process that permanently deletes any audit log entries older than 90 days. This cannot be overridden.


Custom Domains

Whitelabel your project's delivery network by connecting your own domain (e.g., images.yourbrand.com). PichaFlow handles SSL certificate generation and global routing automatically.


Usage & Billing

Track your bandwidth consumption, transformation counts, and storage usage for each project in real-time.

  • Bandwidth: Total data delivered via the PichaFlow CDN for this project.
  • Transformations: Number of unique image processing requests.
  • Plan Limits: Usage is measured against your project's specific tier (Hobby, Pro, or Scale).

Overage Strategies

PichaFlow offers flexible management for when your project exceeds its monthly transformation quota. You can configure these settings in the Billing section of your Project Settings.

StrategyBehaviorBest For
Soft CapService stops once you hit your limit + a tiered grace buffer (10-20%).Fixed budgets.
Metered Top-upSeamlessly keep scaling for $1.00 per 1,000 additional transforms.High-growth apps.
Auto-ScaleAutomatically upgrade to the next tier for the best unit economics.Professional workflows.

!TIPGrace Capacity: Every project includes a built-in safety buffer above its hard limit: 10% for Hobby, 15% for Pro, and 20% for Scale accounts. This ensures unexpected spikes don't immediately disrupt your service.