Login Limit per User / Studio

Feature Requests
1

Ability to define maximum number of active sessions or logins per user, configurable at the studio or product level.

2

@haehre hi there! This is an interesting thought - could you tell us a bit more about the use case for such a feature?

1 Like
How to prevent multiple device logins for the same user in Pickaxe?
3

Hi there, sure:

The main use case is professional and commercial use of Pickaxe studios, especially when selling AI tools to teams, companies, or organizations rather than solo users.

Here are the core scenarios this feature would solve:

  1. Prevent account sharing
    In B2B contexts, it’s common that one login gets shared across multiple people (e.g. a team of electricians, consultants, or support staff).
    Login/session limits ensure that one license equals one real user, unless a team plan is intentionally sold.

  2. Enable flexible licensing models
    This feature allows studio owners to offer structured plans such as:

    • Single-user license (1 active session)

    • Team license (X concurrent logins)

    • Company/enterprise license (higher or unlimited sessions)

1 Like
4

Strong +1 on this. Session limiting is essential for professional B2B Pickaxe deployments.

Real-world blocker: We’re building professional tools for contractors and field teams. Manual user provisioning + no session controls = impossible to scale.

Specific pain points:

  1. Cost control: Token costs spike with shared credentials, zero attribution
  2. Trust gap: Management questions ROI when “5 licensed users” shows minimal activity (because 15 people share those 5 logins)
  3. Compliance: European B2B buyers require audit trails for licensing
  4. Support load: “Why can’t I log in?” → someone else is using their credentials

Technical suggestion:

  • JWT token invalidation on new login
  • Dashboard showing active sessions per user
  • Per-product tier configuration (Pro users get 1 session, Enterprise gets 3, etc.)

Competitive context: Every professional SaaS has this. Pickaxe builders need feature parity to sell into enterprise accounts.

This isn’t just about preventing abuse - it’s about enabling professional builders to scale past MVP stage.

@nathaniel