Magic.NET is an open-source permission management platform built with .NET 6/7 and Vue. Its core value lies in reducing the cost of building enterprise admin systems from scratch by providing ready-to-use RBAC, file management, job scheduling, and workflow modules. It is well suited for quickly building ERP, CRM, and OA systems. Keywords: .NET permission management, RBAC, admin scaffold.
The technical specification snapshot highlights a practical enterprise stack.
| Parameter | Description |
|---|---|
| Project Name | Magic.NET |
| Core Languages | C#, JavaScript |
| Backend Frameworks | .NET 6/7, Furion, SqlSugar |
| Frontend Frameworks | Vue, Ant Design Vue |
| Communication Protocols | HTTP API, gRPC, SignalR |
| Permission Model | RBAC |
| Databases | SQLite, SQL Server, MySQL |
| Open-Source License | Apache-2.0 |
| Code Hosting | Gitee |
| Star Count | Not provided in the source; refer to the live repository data |
| Core Dependencies | Furion, SqlSugar, SignalR, Vue, Ant Design Vue |
This project serves as a ready-made foundation for enterprise admin scenarios.
Magic.NET is not positioned as a standalone permissions component. It is a deployable admin platform foundation. It prepackages common capabilities such as users, roles, menus, organizations, positions, and dictionaries, which reduces repetitive engineering work.
For .NET teams, the value goes beyond simply being runnable. It provides the governance capabilities most enterprise systems need by default. Developers can focus on business modules instead of rebuilding account systems, menu routing, and audit logging.
The core positioning is straightforward.
Target use case: Rapidly build enterprise admin systems
Typical scenarios: ERP / CRM / OA / CMS
Core model: Frontend-backend separation + RBAC + modular extensibilityThis summary defines the product boundary of Magic.NET: it is closer to a business system scaffold than a single-purpose utility library.
The technology stack reflects strong practicality and low integration cost.
The backend uses .NET 6/7, Furion, and SqlSugar, balancing a modern development experience with technologies familiar to many domestic development teams. The frontend uses Vue and Ant Design Vue, which also aligns with the mainstream technical path for admin systems.
The project also supports multi-tenancy, dynamic APIs, gRPC, and SignalR. That indicates it can cover basic management requirements while also leaving room for service governance, real-time messaging, and more complex business orchestration.
A typical local startup flow looks like this.
# Install dependencies after entering the frontend directory
npm install
# Start the frontend development server
npm run serve
# Open backend/Magic.sln in your IDE and run the backend directly
# SQLite is used by default, which is ideal for quick evaluationThis startup flow is intended for bringing up the frontend and backend locally and is suitable for an initial validation of project usability.
The core feature set covers the most common enterprise admin modules.
Based on the source material, Magic.NET already includes users, roles, menus, organizations, positions, dictionaries, announcements, applications, files, logs, online user monitoring, service monitoring, email and SMS delivery, scheduled jobs, and workflow integration.
This combination means it does more than solve permission control. It also covers system operations and platform governance. That is especially important for teams that need to deliver management systems quickly.
The feature modules can be summarized in three layers.
1. Identity and permissions: users, roles, menus, organizations, positions
2. Platform capabilities: files, announcements, logs, monitoring, message delivery
3. Business enhancements: scheduled jobs, workflows, real-time communication, multi-tenancyThis three-layer structure helps you evaluate whether the project can directly support your business system infrastructure.
The UI screenshots suggest the project already has a mature admin interaction model.
AI Visual Insight: This image shows a typical admin dashboard home or list-page layout with left-side navigation, a top action area, and a central data workspace. It indicates that the project already implements a standard enterprise information architecture and is suitable for directly hosting menu permissions, data tables, and business configuration pages.
AI Visual Insight: This image further demonstrates the system’s implementation for tabular data management. It likely corresponds to modules such as users, roles, menus, or dictionaries, indicating that the frontend component system is relatively complete and supports common admin interactions such as filtering, pagination, and action columns.
AI Visual Insight: This image appears to show a configuration page, form page, or module detail page. It reflects that the project supports not only list views but also complex form entry and property management, which is critical for scenarios such as workflows, jobs, and organizational structures.
AI Visual Insight: This image may correspond to a monitoring, analytics, or system configuration interface. It suggests that the project already includes ready-made pages for operational visibility and system governance, which can reduce the amount of secondary development required for log centers, online users, and service monitoring modules.
The default startup experience is especially friendly for new teams.
The project uses SQLite by default, and that detail matters. It allows developers to validate, debug, and extend the project locally without first provisioning a database service, which significantly lowers the trial barrier.
When the project moves into testing or production, you can switch to SQL Server or MySQL. For small and midsize teams, this lightweight-first and smooth-upgrade approach is highly practical.
Switching databases usually only requires configuration changes.
{
"DbType": "MySql",
"ConnectionString": "Server=127.0.0.1;Database=magic;Uid=root;Pwd=123456;"
}This configuration is used to switch the database type and connection information, demonstrating the project’s flexibility in adapting to different data sources.
AI Visual Insight: This image shows the structure of the database configuration file. The key point is that data source switching is completed through DbType and the connection string, indicating that support for SQLite, SQL Server, and MySQL is implemented through a unified configuration abstraction rather than deep coupling to a single database.
The modular design is its key advantage over ordinary CRUD scaffolds.
The original material specifically emphasizes that framework upgrades do not affect business code. That implies a relatively clear boundary between the business layer and the underlying framework. When you extend the system with new modules, you do not need to frequently modify common low-level implementations.
For enterprise projects, the truly expensive part is not the first release but the iterations that follow. If the modular structure is designed well, it can significantly reduce the maintenance cost introduced by upgrades, replacements, and multi-developer collaboration.
A business module can be organized like this.
public class CustomerAppService
{
// Query the customer list by reusing the platform's existing permission and data access capabilities
public object GetList()
{
// Core logic: focus on business queries here instead of reimplementing login and authorization
return new { Message = "客户列表" };
}
}This example shows the value of a scaffold-style platform: developers mainly write business services, while the platform provides the infrastructure consistently.
It is especially well suited for three types of teams.
The first type includes outsourcing or product teams that need to deliver ERP, CRM, or OA systems quickly. The second type includes internal engineering teams that want to standardize their admin technology foundation. The third type includes developers learning how .NET enterprise admin architectures are designed.
If your project needs permissions, menus, logs, files, jobs, and real-time communication working together, Magic.NET is more time-efficient than assembling components from scratch. If your requirements are extremely lightweight and only involve a small single-page system, it may feel too heavy.
The adoption path and evaluation guidance are both clear.
The code is hosted on Gitee and released under the Apache-2.0 license, so it is free for commercial use. For teams preparing to adopt it, validate three things first: whether the permission model fits, whether the database support meets requirements, and whether the module boundaries align with your own business decomposition.
In practical selection, Magic.NET’s advantage is not that it introduces a novel concept. Its advantage is that you can put it to work immediately. For most enterprise admin projects, that is often more valuable than pursuing a more complex architecture.
FAQ
1. Is Magic.NET suitable for building an enterprise admin system from scratch?
Yes. It already provides common capabilities such as RBAC, menus, logs, files, scheduled jobs, and workflows, which can significantly reduce the time required to build foundational modules.
2. Can Magic.NET only use SQLite?
No. SQLite is only the default evaluation option. The project also supports SQL Server and MySQL, and you can switch databases through configuration.
3. Is it better suited for learning or for production use?
Both. For beginners, it is a complete sample for understanding .NET enterprise admin architecture. For enterprise teams, it is a foundational admin platform that supports fast secondary development.
[AI Readability Summary]
Magic.NET is an open-source RBAC permission management platform built on .NET 6/7 and Vue. It integrates users, roles, menus, files, scheduled jobs, workflows, and real-time communication, making it well suited for rapidly building ERP, CRM, OA, and similar enterprise admin systems. This article provides a structured analysis of its technology stack, module capabilities, startup approach, and ideal use cases.