Drıftstack docs
Docs

What ‘profiles at once’ (concurrent sessions) means

You might be here because: “what does profiles at once mean” · “Profiles at once” · “concurrent sessions” · “how many sessions can I run at the same time” · “do my teammate’s sessions count against my limit” · “what happens if I start one too many” · “is the limit per user or per account” · “do saved profiles count” · “Account already has 3 active sessions; tier permits 3” · “sessions at once”

Short answer

“Profiles at once” is how many of your profiles can have a session open at the same time — think of browser tabs open at once. It is the thing the plans differ by: Trial and Starter 1, Pro 3, Team 6, Scale 12, Enterprise 20 or more. On a paid plan there is no monthly hours total: within that number you can run one session after another. Each session still has its own end: a session that no AI agent drives runs for up to 4 hours, and any session closes after a time with no activity. On the Trial a session runs for up to 20 minutes, with 2 hours of session time in total.

Check first

  • Which plan does Billing show? Profiles at once is the first row on every plan card.
  • Open the Sessions tab: a session still starting counts, and so does one started from a script or another computer.

Likely causes and fixes

  1. What counts. A session counts while it is starting, ready or busy, and stops counting when it ends. Saved profiles do not count — only profiles with a session open. So Starter’s 25 saved profiles and 1 at once means you keep them all and run any one of them at a time.

  2. Starting one too many. The extra launch fails with a clear message and nothing already running is touched; the limit is checked only when a session starts, never while it runs. The message reads “Concurrent session limit reached — Account already has N active sessions; tier permits N” (HTTP 429 for developers). Fix: end a session you started (or ask whoever started one, or wait for one to end), then launch again. See Concurrent session limit reached (429 concurrency-limit).

  3. Per account, not per person. The count is the account’s, so sessions a teammate opens in your workspace share the same number. See Working in a team owner’s workspace (roles, what a member sees).

  4. You need more at once. Move to a plan with a higher number: Starter, Pro and Team are self-serve from dashboard → Billing → Choose a plan; Scale and Enterprise are arranged by contact. New limits apply the next time you start a session.

  5. After a downgrade. The number drops at renewal, and only the most recently used profiles can launch if you hold more than the new plan includes — see After a downgrade only the most recently used profiles/proxies can launch.

If it still fails

If the Sessions tab shows fewer running sessions than the message counts, press Talk to a person in this chat (or open Help) and include your plan, what the Sessions tab shows and the exact message. Nothing here needs an account action; plan changes are self-serve for Starter, Pro and Team.