Skip to content

Team Management

Manage team credit, member budgets and model access centrally.

One shared wallet, individual monthly budgets and centrally managed model access. Let developers work with Lurus Code while keeping administration and usage in view.

Conversion to Team is permanent. Team accounts cannot return to individual plans. A consultation does not convert your account.

€0 per team member

No seat or team base fee. Actual model and AI feature usage is paid from the shared wallet.

Capture of the team dashboard with shared wallet, member roles and current-month usage. Use anonymised sample data.
The team in one view

Shared credit. Individual boundaries.

Shared credits for the team. A budget for each member.

Fund the shared wallet and decide how much each member can use per month. A shared balance does not have to mean unlimited spending.

Monthly member budgets

Set an individual monthly limit or allow an unrestricted member budget. Available team credit still applies.

Usage and remaining credit

Check current-month usage and remaining member budgets alongside the team balance.

Controlled replenishment

Top up manually or configure automatic replenishment with a 24-hour funding limit.

Inviting a team member and assigning an individual monthly budget.
Individual budgets, shared credit
Capture of the Admin model policy with all-model or restricted selection. Hide account identifiers.
Central model access

A shared model policy

Decide which models belong in your workflow.

Admins can allow the available model catalog or restrict access to a selected set. Your team works within that choice rather than configuring access independently.

Model availability and usage costs depend on the current catalog and available credit.

From evaluation to rollout

Make the team setup a deliberate decision.

  1. Review the conditions.

    Check usage-based billing and the permanent Team conversion before switching an account.

  2. Invite the team.

    Manage invitations and separate Admin and Member responsibilities.

  3. Set the boundaries.

    Choose member budgets, model access and wallet replenishment settings.

  4. Follow actual usage.

    Use the dashboard to check consumption and adjust budgets as the team works.

Conversion to Team is permanent. Team accounts cannot return to individual plans. A consultation does not convert your account.

Your code stays yours.

Source code and request context are processed with Zero Data Retention. No use for model training. Providers and processing regions are disclosed transparently.

See privacy and processing details

A few things to know before you start.

Does each member require a paid seat?
No. There is no seat or team base fee. The team funds a shared wallet and pays for actual model and AI feature usage.
Can I switch back to an individual plan?
No. Conversion to Team is permanent. Review the conditions before converting; contacting us for advice does not change your account.
Can I control budgets and model access?
Yes. Admins manage monthly member budgets, the shared wallet and a central model access policy. Usage remains subject to available credit.

Team Management

Discuss your team setup before switching plans.

Talk to us about your team workflow, then review the conditions before setting up Team in the dashboard.

Conversion to Team is permanent. Team accounts cannot return to individual plans. A consultation does not convert your account.

Want to start with your team? Talk to us.

A deliberate choice

Before your first prompt.

Interactive demo
Lurus Codeprivacy-demo · illustrative workspace

Demo session ready. Your model choice and data route are separate decisions.

Illustrative scenario. No real sign-in, security test or code transmission takes place.

Image preview