Feature: License/Limiter RAGFlow Management

[PentaFrame-Development]

Hello Everyone!
Months ago we created a license management feature that allows only the first user registered (that becomes the admin) to see an admin panel that allows to create expiring licenses for the next users, limit the file upload and limit the available models and llm calls.
We made it to limit the usage of some members of our workspace and we think that this could be useful also to others.
Parallel to this we also added a passcode in new user registration that is required to sign up for the first time.
Since we made it for RagFlow V21.0, if anyone needs this feature, in the next month we can update this functionality to the latest version and create a pull request! Let us know what do you think! We are open to any question or suggestions!

Thanks
PentaFrame-Development

[PentaFrame-Development]

I just noticed that the newer releases include an admin CLI tool and panel — great addition. We're testing it now, and when we have time we'd be happy to help improve or extend its functionality if needed.

In our internal setup we implemented a few alternative admin assignment methods (like configuring an admin email in the service file or automatically assigning admin rights to the first or a specific user). If any of that could be useful, we’re happy to share or contribute further.

Thanks again for the solid work on this project.

[Magicbook1108]

You are welcome to submit a pull request for collaborators to review.

[PentaFrame-Development]

Thank you for the invitation to contribute.

After reviewing the current admin implementation in admin/server/, I see that RAGFlow has a solid foundation with user management, service monitoring, and role management stubs. However, I noticed there are no built-in features for:

• License/trial expiration management
• File upload quotas per user
• LLM call limits per user or model
• Model availability restrictions

In our internal fork, we implemented a License model that tracks:

• License status (active, trial, expired)
• Trial expiration dates with automatic status updates on login
• Upload counters and limits
• Per-model usage tracking and limits (e.g., GPT-4: 1000 calls, Claude: 500 calls)

The implementation integrates with the login flow to block expired licenses and could extend the existing admin routes.

A few questions before we proceed:

Admin assignment: How would you prefer the first admin/superuser to be set?
Option A: Configure an admin email in service_conf.yaml (e.g., admin_email: [email protected])
Option B: Automatically assign superuser rights to the first registered user
Option C: Keep the current approach (manual CLI assignment)
Registration control: We also implemented a passcode requirement for new user registration (users need a code to sign up). Would this be useful, or do you prefer to keep only the current whitelist approach?

If there's interest, we could prepare a PR that adds these features to the existing admin system. We're flexible on the approach - we could either:

• Extend the current User or Tenant models with quota fields
• Add a separate License model (our current approach)
• Integrate with the role-based permission system that's currently stubbed out

Let us know which direction would be most useful for the project.
@Magicbook1108 @KevinHuSh @buua436
And thanks again for the amazing work!

PentaFrame-Development