Skip to content

Lurus Code · Your AI coding agent

Your AI coding agent. GDPR-compliant. GDPR-compliant. With With Zero Zero Data Data Retention. Retention.

Lurus Code understands your project, plans changes and implements them in VS Code and CLI. Choose the right model and stay in control – with no training on your code.

Zero Data Retention at model providers. Providers and processing regions are clearly documented.

For your team

Shared credits. Central management.

The updated product view with codebase, task, and agent in the editor.
Lurus Code workspace
Work on a real task directly in the terminal.
Lurus Code CLI

Credits instead of usage quotas

Your Your credits. credits. Your Your workflow. workflow.

No daily or weekly usage quotas that force a pause. Lurus bills usage against credits, so you do not have to plan your work around a new usage window.

All prices and terms
Credit example: Ultra
200€/ month
Model credits
€400
Separate Lura credits
+ €200

Additional credits, exclusively for Lura.

Usage depends on your available credits and plan features. This is not a promise of unlimited technical capacity.

The right intelligence

The The right right model model for for your your code. code.

Choose your model for planning, implementation, and review – in one workflow. Providers and processing regions stay transparent, with Zero Data Retention at model providers and no training on customer code.

  • GLM / Z.ai
  • Claude
  • DeepSeek
  • Gemini
  • Kimi
  • MiniMax
  • GPT / OpenAI
  • Qwen

GDPR GDPR by by design design

Documented privacy guarantees and a contact in Germany.

Transparent Transparent data data paths paths

Model, provider, and processing region are documented for each route. Not every route is exclusively European.

Controlled Controlled changes changes

In planning mode, approach, boundaries, and approval come before implementation.

Less Less coordination coordination

Planning, implementation, and verification stay in one traceable workflow.

Reviewable Reviewable quality quality

Diffs and executed tests, reviews, and security checks help you assess results.

Continuous Continuous context context

Project rules and decisions persist across work steps.

Your next step

Start Start on on your your own. own. Or Or bring bring your your team. team.

Pro Pro

20 € / month

For developers with Security Scan, Code Review and Custom Agents.

Start free trial

Ultra Ultra

200 € / month

For teams with Agent Teams, orchestration and priority access.

Start free trial

Team Team

€0 per team member

Shared credits, individual budgets, and central management. No seat fees.

Discuss a pilot

One-week free trial

After the trial, your selected paid plan continues unless you cancel beforehand.

Compare all plans

No seat or team base fee. Model and AI feature usage is paid from your shared credits.

Conversion to Team is permanent. A pilot conversation does not convert your account.

Team management and terms

Start Start right right in in your your terminal. terminal.

Install the CLI globally, sign in once, and start Lurus Code directly in your project.

Read the quickstart
  1. 01
    Install globally npm install -g @scramble-cloud/lurus-code-cli
  2. 02
    Sign in lurus login
  3. 03
    Start in your project lurus chat

Where you already work

Your Your project project context. context. In In VS VS Code Code and and CLI. CLI.

Project rules, decisions, and sessions connect your work. Start in your editor and continue in the CLI with the same context.

VS Code
Saved decisions and the task being continued.
Session and project context

Project rules · Decisions · Sessions

Same task. Same context.

CLI
Continue a task in the terminal using saved project rules and decisions.
Project context in the CLI

From task to result

Stay Stay in in control. control.

From understanding your codebase to a result you can review – in one connected workflow.

  1. 01 / Understand

    Understand your project.

    The agent reads relevant files, dependencies and project rules. Existing patterns establish the foundation for the change.

    Relevant files and dependencies in project context.
    Understand the codebase
  2. 02 / Plan

    Plan the changes together.

    For larger tasks, ask for a plan first. Review the affected code and verification steps, then approve implementation.

    Capture of an implementation plan with affected files and verification steps.
    Plan before implementation
  3. 03 / Implement

    Implement in your project.

    The agent edits related files and runs suitable tools and terminal commands. Progress and changes remain visible.

    Tool use and concrete code changes.
    Implementation in the project
  4. 04 / Verify

    Verify the result.

    Tests, code review, security scanning and browser checks help verify changes. See which checks ran and which questions remain open.

    Capture of related diffs and the project checks that were run.
    Change and verification

Clarity before you start

Anything Anything else else before before you you build? build?

What does no daily or weekly quotas mean?

There are no time-based usage quotas with a plan-imposed pause. You draw from your available credits. This means neither free unlimited usage nor unlimited technical capacity; features and agent limits depend on your plan.

What is included in my plan?

Pro, Pro+, and Ultra include model credits plus separate Lura credits, which can only be used for Lura. Current amounts, features, and agent limits are listed on the pricing page.

What happens after the trial week?

You can try Pro, Pro+, and Ultra free for one week. Your selected paid plan then continues unless you cancel beforehand. Subscriptions can be cancelled at any time.

How is code checked, and who decides?

You can inspect the diff and the tests, reviews, and security checks that ran. In planning mode, implementation begins only after your approval; other modes follow configured permissions. The final assessment stays with you.

What happens to my code?

Zero Data Retention applies by default at connected model providers: required request context is not stored there after processing. Neither Lurus nor connected model providers train on customer code. Provider and processing region are documented for each route.

How does a team get started?

Teams use a shared wallet without seat or team base fees and pay for actual usage. Admins control budgets, roles, and policies. Discuss an enterprise pilot with us. Subsequent conversion to Team is permanent, not a reversible individual-plan trial.

Your project is not waiting

What What will will you you build build next? next?

Start with a real task in your project.

After the trial, your selected paid plan continues unless you cancel beforehand.

Read the quickstart

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