aioflare

Known Beta Limitations

Current status: Beta phase

aioflare is currently available in beta. This page highlights important limitations and considerations so you can use the platform with clear expectations. aioflare is built as a productivity layer on top of Cloudflare designed to simplify multi-account and multi-zone management. While powerful, certain features and behaviors are intentionally limited during the beta phase.

1. Beta Stability & Evolving Features

aioflare is under active development. Features, limits, and system behavior may evolve based on user feedback, technical constraints, and performance considerations. Some functionality may be adjusted, restricted, or removed as the platform continues to improve.

2. Bulk Operations & Queue Processing

Bulk operations in aioflare are processed through a queue system with two execution modes:

  • •Server-Side Processing — Runs independently on the server and continues even if your browser is closed. Recommended for large-scale or long-running operations.
  • •Browser-Based Processing — Runs within your active browser session. Closing the tab or losing the session may pause or stop the operation. Keep the tab open until completion when using this mode.

3. Advanced Settings & Risk Awareness

Certain settings exposed in aioflare directly impact website availability, security behavior, and request handling.

Misconfiguration may result in:

  • •Website downtime
  • •Redirect loops
  • •Blocked visitors or APIs
  • •Broken functionality

These settings are intended for advanced users. Only modify them if you understand Cloudflare behavior and your origin infrastructure. aioflare does not validate whether a configuration is safe for your specific setup.

4. Data Encryption & Account Recovery

aioflare secures sensitive data using server-side encryption (AES-256-GCM), with a unique encryption key per user.

  • •All sensitive fields are encrypted at rest
  • •Encryption is managed server-side
  • •No user-managed encryption password is required

Account recovery depends solely on account authentication not encryption keys. Users are responsible for maintaining the security of their account credentials.

5. Cloudflare API Dependencies

aioflare operates on top of Cloudflare’s official APIs. As a result:

  • •API rate limits apply
  • •Temporary API issues may impact functionality
  • •Some features may not be fully supported
  • •API limitations cannot be bypassed

6. API Key & Token Usage

aioflare supports both API Tokens and Global API Keys.

  • •API Tokens (Recommended) — Scoped, more secure
  • •Global API Keys — Full access, higher risk

Warnings are shown when using Global API Keys, but credential security remains the user’s responsibility.

7. Analytics Data Limitations

Analytics data in aioflare is fetched directly from Cloudflare and is not permanently stored.

  • •Data availability depends on Cloudflare
  • •Minor delays or discrepancies may occur
  • •Historical data may be limited
  • •Data is not modified or processed

8. Not a Cloudflare Replacement

aioflare is not a replacement for the Cloudflare dashboard. Some features may be unavailable, read-only, or intentionally limited. The platform focuses on:

  • •Productivity
  • •Bulk operations
  • •Multi-account management

not full feature parity.

9. Responsibility & Usage

All actions performed through aioflare use your Cloudflare credentials and permissions. Changes made via aioflare have the same effect as changes made directly in Cloudflare. Always review and understand the impact of your actions especially when performing bulk operations.

10. Feedback & Improvements

Feedback plays a key role in shaping aioflare. If you encounter issues, unclear behavior, or limitations affecting your workflow, please submit feedback through the application.