Skip to main content
The Coding Plan (DevPass) is a flat monthly plan for coding agents and CLIs — Claude Code, Cursor, Cline, Roo Code, or any OpenAI- or Anthropic-compatible tool. A dedicated ek-dev- key. Unlimited tokens. No credits. Independent of every other Electron Hub plan.

Tiers

Launch seats are capped per tier. If a tier is sold out, join the waitlist on the dashboard. You are notified when a seat opens (first come, first served).

Included models

All models support function calling on /v1/chat/completions, /v1/messages, and /v1/responses. Series weight (0.5× / 1× / 2×) affects soft full-speed headroom (ceil(raw × weight)). It does not stop you from using the plan. Dashboard per-model stats stay raw. Heavy models also hold 2 concurrency slots per request; Flash and Standard models hold 1. See Concurrency slots.
:dev models accept only ek-dev- keys. DevPass keys can call only :dev models. Keep your master key configured if you need the rest of the catalog.

Quickstart

  1. Subscribe on the Dashboard → Console → Coding Plan.
  2. Your ek-dev-... key is provisioned within seconds. It is always retrievable from the Coding Plan tab. Regenerating it immediately invalidates the old key.
  3. Use it as a Bearer token:

Fair use

One person, one seat. Lite and Turbo are alternative tiers, not stackable. If two concurrency slots are not enough, upgrade. Do not open another account, email, or payment method to hold a second seat. The ek-dev- key may run on machines you personally use (home, work, laptop, CI, VPN). All of that usage counts against the same seat. The plan is for interactive coding by that one person. These are violations and lead to suspension:
  • a second seat under any identity you control
  • sharing the key with anyone else
  • pooling keys or seats to raise throughput
  • resale, subletting, or access-as-a-service
  • a deployed app or backend that serves other people
  • unattended or multi-user production traffic
We treat extra seats, shared keys, and resale as the same violation. Chargebacks are account-level violations. High-duty-cycle or multi-user traffic belongs on a regular Electron Hub API key billed on credits.
Each plan has a fixed number of concurrency slots: 2 on Lite, 5 on Turbo. A request holds its slots until it finishes. Request starts are limited separately (see Requests per minute).Series can be mixed in any combination that fits the slot total. If the slots a request needs are not free, you get a 429 with Retry-After. Wait for a request to finish, then retry. Coding agents handle this automatically.To keep parallel work moving on Lite, route subagents and background tasks to a Flash model and reserve the Heavy model for the main session. While the plan is temporarily reduced to one slot, a Heavy request uses that single slot.
Each plan includes full-speed headroom that resets at 21:00 UTC. Going past it never blocks you. Requests continue with reduced concurrency and paced admission (consumption-scaled spacing, up to about a minute when far into overage) until the reset. The dashboard shows how close you are to full-speed headroom.
A rolling weekly soft headroom sits above the daily one. Past it, the same slow lane applies (lower concurrency and paced admission). This is not a hard stop. It keeps sustained 24/7 grinders from crowding out interactive work across the week.
Request starts refill continuously at 8 per minute on Lite and 20 per minute on Turbo. Up to 4 (Lite) or 8 (Turbo) can start back-to-back after a quiet moment. Every request counts as one start, Heavy included. In the slow lane (past full-speed headroom, or in low-interactivity mode) it is 3 per minute (burst 2).Past the limit you get a 429 with an exact Retry-After (Lite: about 8 seconds per start). X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset report this budget on every response. These 429s never count toward the temporary pause.
Repeatedly hitting the parallel-slot limit (hundreds of concurrency 429s in a usage day) can pause admission for a few hours. While paused, requests return 403. Your key stays valid. Service resumes automatically at the time shown on the dashboard. Regenerating the key clears an automatic concurrency pause.

Low-interactivity mode

Plans are sized for a person coding, even intensively, all day. When an account shows a usage pattern far beyond typical interactive work, the plan enters low-interactivity mode for about 24 hours:
  • Under light load, behavior is unchanged.
  • When the platform is busy, requests may be queued behind interactive sessions and may need a retry.
  • Nothing is blocked. Your plan, models, and answer quality stay the same.
  • Interactive mode resumes automatically at the time shown on the Coding Plan tab. No action is required.
Low-interactivity mode is a temporary fairness control so interactive subscribers keep responsive access during busy periods. It is not a suspension. If this surprises you, check for a runaway automation first, then ask on Discord.

Errors

Terms

  • Monthly billing via Creem, auto-renewing, non-refundable. Cancel any time. Your key stays active until the period ends.
  • Fair use is binding. Extra seats, shared keys, pooling, and resale are suspended. Chargebacks are account-level violations.

FAQ

Yes. There is no hard token cap and no per-token charge. Soft full-speed headroom only affects concurrency, request rate, and latency when you are far past typical interactive use. Requests are never blocked for burning tokens.
Yes. Founding and beta subscribers who purchased at the launch rate keep that price for as long as the subscription stays active. If you cancel and subscribe again later, the current public price applies.
No. See Fair use. One person, one seat. Upgrade Lite to Turbo if you need more parallel slots.
Yes. Change plans in the Creem billing portal. Your existing key picks up Turbo limits automatically.
Your ek-dev- key is deactivated. Resubscribe any time to restore it.
See Low-interactivity mode. Requests remain available. Under load they may queue behind interactive sessions until interactive mode resumes automatically.