Context
Relevant files, dependencies, and project rules.
Lurus Code for enterprise
Move more software. Give up less control.
Turn assignments into traceable code changes while budgets, model policies, and data protection remain centrally controlled. Your team keeps the final review.
€0per team member
No seat, license, or team base fee. Pay for actual usage.
Personal contact in Germany · Start with one clearly bounded use case
One assignment. A reviewable workflow.
The agent examines relevant project context, plans the change, edits files, and runs the intended quality checks — in CLI or VS Code.
Plan
Root cause, boundaries, and acceptance criteria.
Implementation
Targeted code and test changes across files.
Verification
Tests, lint, and diff before human approval.
Individual productivity. Shared guardrails.
Central team management turns individual AI usage into a governable process.
Explore team managementMembers and roles
Invite users, manage responsibilities, and organize team access in one place.
Budgets and limits
Set individual monthly budgets or unlimited access for selected members.
Shared team balance
Fund usage centrally and replenish the balance manually or automatically.
Admin policies
Define centrally which AI models your team may use.
A decision engineering, security, and procurement can support.
Lurus GmbH is your German contracting party. Product-wide privacy guarantees and route-specific provider facts are documented separately; infrastructure evidence is not a product certification.
Lurus Code processes source code and request context with Zero Data Retention.
Context required for a request is transmitted solely for processing and is not retained after processing is complete.
Customer data and source code are not used to train AI models.
The no-training guarantee applies to Lurus and every model provider connected through Lurus Code.
Zero Data Retention applies by default to every model and provider route.
Model, provider, and processing region are disclosed transparently for each route without limiting the Zero Data Retention guarantee.
Hosting infrastructure: ISO/IEC 27001 certified and C5 attested.
- German contracting party and personal contact
- Model, provider, and region disclosed per route
- Public DPA and privacy information
- Reviews, security scanning, and quality gates in the workflow
Start small. Prove impact. Scale deliberately.
No big-bang rollout. Define one real workflow and success criteria before adding more teams.
Choose the use case
A recurring workflow with clear acceptance criteria: a bug fix, test coverage, or code review.
Define guardrails
Frame repositories, quality gates, budgets, and allowed features for your organization.
Evaluate and scale
Review the outcome together and transfer only proven rules to additional teams.
Team control without a seat commitment.
Choose your shared team balance and control actual consumption with per-member budgets. Invited or inactive accounts do not create seat costs.
Note: Converting an account to Team is permanent.
€0per team member
No seat, license, or team base fee. Pay for actual usage.
Clarity before the pilot.
Does every team member require a license fee?
No. Team members cost €0 per person, with no seat, license, or team base fee. Your organization provides a shared balance and only actual usage is deducted.
Is our source code or input retained?
No. Context required for a request is transmitted solely for processing and is not retained after processing is complete. Zero Data Retention applies by default to every connected processing route.
Is our data used for training?
No. Customer data and source code are not used to train AI models by either Lurus or connected model providers.
Can we limit spend per employee?
Yes. Admins can set individual monthly budgets or allow unlimited access for selected members. Usage is paid from the shared team balance.
Do we need to migrate the entire company immediately?
No. Start with a clearly bounded pilot, one team, and a measurable workflow. Include additional areas only after evaluation.
Is a Data Processing Agreement available?
Yes. The DPA and privacy information are publicly available and can be reviewed by privacy, security, or procurement before the pilot.
How does Team billing work?
Your organization sets the shared balance. Actual model and AI feature usage is deducted; admins manage balance and member budgets centrally. Converting to Team is permanent.
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 detailsBring a real workflow. Let’s shape your pilot.
Discuss your use case, required guardrails, and the next decision directly with the Lurus team in Germany.