Questions & Answers.

Sign in with Google, connect your Cloudflare account (OAuth or API token), and click "Create Load Balancer." Pick a strategy, add your origin servers, and deploy. The whole process takes about 90 seconds.

Workers Scripts: Edit (deploy and manage Workers), Zone: Read (list your domains), DNS: Edit (create records for IP-based origins), Account Analytics: Read (show request metrics), Workers Routes: Read (detect hostname conflicts, optional but recommended).

Yes. OAuth is the recommended method. Click "Connect with Cloudflare" and you will be redirected to Cloudflare to authorize EdgeBalancer. No need to manually create tokens or copy IDs.

Yes. You need a domain on Cloudflare. EdgeBalancer deploys Workers to your Cloudflare zones, so you must own the domain you want to load-balance.

Cloudflare Load Balancing is a DNS-based solution ($5/balancer + per-query fees). EdgeBalancer deploys as a Worker script, giving you request-level control with no per-query costs. You pay only for Worker requests (100k/day free, then $0.30/M).

Your load balancers keep running. Once deployed, the Worker script lives in your Cloudflare account. EdgeBalancer is only the control plane for creating and updating configs — the data plane runs independently on Cloudflare's edge.

Updates use Cloudflare Worker Versions and Deployments. When you change a config, we create a new version, deploy it, and keep the previous version as a rollback target. Old inactive versions are pruned automatically.

Yes. All Worker scripts are visible in your Cloudflare dashboard under Workers & Pages. The code is generated from strategy-specific templates.

Workers add ~1-3ms median overhead. The benefit is intelligent routing, health checks, and failover at the edge — much faster than round-tripping to a centralized load balancer.

No. EdgeBalancer never sees your production traffic. We store only metadata (origin URLs, weights, strategy choice) encrypted in MongoDB. All requests flow directly from Cloudflare edge to your origins.

Yes. Your token is encrypted with AES-256-GCM before storage in MongoDB. The encryption key is stored separately from the database. We never log or store plaintext credentials.

We collect your account info (name, email), Cloudflare credentials (encrypted), and load balancer configuration. We do not collect or see your production traffic.

Yes. Delete your load balancers from the dashboard, then disconnect your Cloudflare credentials (OAuth or API token). You can also revoke access directly from your Cloudflare dashboard.

Yes. We comply with GDPR (EU) and DPDP Act 2023 (India). You can request data access, correction, or deletion at any time. See our Privacy Policy for details.

No. EdgeBalancer is free to use. You only pay Cloudflare for Worker requests.

Cloudflare automatically bills $0.30 per million requests. You can set spending limits in your Cloudflare dashboard.

No. No egress fees, no cross-region transfer, no idle charges, no per-balancer fees. You pay only for Worker requests.

Round Robin, Weighted Round Robin, IP Hash, Sticky Sessions, Weighted Sticky Sessions, Failover, and Geographic Routing. See the Strategies page for detailed explanations.

EdgeBalancer runs periodic health checks to your origin servers. If an origin fails (5xx error, timeout, or connection refused), it is marked unhealthy and removed from rotation. When it recovers, it is added back.

Yes. The sticky session strategies (cookie-sticky, weighted-cookie-sticky) work with WebSocket connections. The cookie keeps the connection pinned to the same origin.

Delete load balancers from the dashboard, then rotate your API token. You can also manually delete the Worker scripts from Cloudflare's dashboard. EdgeBalancer has no lock-in — everything runs in your account.