skyeye
SkyEye is a low-code/no-code enterprise OA and ERP platform built on Spring Cloud Alibaba and Vue3, targeting manufacturing, healthcare, education, and SMB sectors. It provides visual designers for forms, workflows, and reports without requiring traditional Java development.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | dromara/skyeye |
| Owner | dromara |
| Primary language | Java |
| License | MIT — OSI-approved |
| Stars | 1.2k |
| Forks | 291 |
| Open issues | 16 |
| Latest release | Unknown |
| Last updated | 2026-07-08 |
| Source | https://github.com/dromara/skyeye |
What skyeye is
Spring Cloud Alibaba 2.1.0 microservices backend with Nacos, RocketMQ, Sentinel, and Activiti 6.8.0 workflow engine; Vue3 + Ant Design Vue frontend (PC) and uni-app (mobile); MySQL/Redis persistence; Mybatis-Plus ORM with Druid connection pooling.
Get the skyeye source
Clone the repository and explore it locally.
git clone https://github.com/dromara/skyeye.gitcd skyeye# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires operational support for 5+ microservices (Nacos, RocketMQ, MySQL, Redis, main app). Kubernetes orchestration recommended; local development environment setup non-trivial.
- Custom business logic still requires Java development despite low-code UI; visual designers cover forms/workflows but not business rules engine or custom algorithms.
- Multi-tenant data isolation is declarative; audit and cross-tenant query safeguards require manual review during deployment to prevent accidental data leakage.
- License purchasing mandatory for full source code and production deployment. Freemium tier (preview-only) inadequate for business evaluation.
- No release notes or versioning in public repo (latestRelease: n/a). Upgrade path and breaking-change management unclear.
When to avoid it — and what to weigh
- Requiring Proven Enterprise Security Certifications — No mention of SOC 2, ISO 27001, HIPAA, or penetration-test results in public data. Security posture requires vendor review before handling regulated industries.
- Need for Strict Open-Source-Only Deployments — README explicitly references restricted commercial features and member-only source tiers. Full functionality tied to paid licensing model; open GitHub repo lacks complete business modules.
- Heavy Integration with Legacy ERP Systems — No documented connectors for SAP, Oracle, NetSuite, or other enterprise legacy platforms. Integration scenarios focus on internal module-to-module communication via APIs.
- High-Frequency Real-Time Analytics or OLAP Requirements — Designed for transactional workflows and operational reporting, not complex data warehousing. RocketMQ messaging and Redis caching insufficient for sub-second analytics at scale.
License & commercial use
Licensed under MIT (permissive OSI license). MIT allows commercial use, modification, and redistribution with attribution. However, README indicates full-source licensing is tiered (member-only), suggesting open repo is incomplete.
MIT license technically permits commercial use. However, README explicitly states complete source code and unrestricted commercial deployment require paid membership. Open GitHub repository lacks several business modules. Evaluate vendor's member license terms (cost, IP ownership, resale rights) before committing to commercial deployment.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Needs review |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | Medium |
No mention of authentication method (JWT, OAuth, SAML), encryption (TLS, at-rest), or audit logging. Multi-tenant isolation enforced via code; no third-party security audit results published. RocketMQ and Redis deployments should use network isolation and credentials. Recommend security review before handling PII or production financial data.
Alternatives to consider
Odoo (Community/Enterprise)
Mature, open-source ERP/CRM with stronger community support, documented APIs, and extensive third-party integrations. Better suited if you need proven enterprise deployments and large ecosystem.
ERPNext (Frappe)
Open-source ERP on Python/MySQL with transparent licensing, strong documentation, and multi-tenant SaaS architecture. Simpler deployment and active community; better for fully open-source mandates.
Mendix / OutSystems (Low-Code Platforms)
Enterprise low-code platforms with stronger governance, security certifications, and vendor support. Better for regulated industries and organizations requiring SLA-backed SaaS.
Build on skyeye with DEV.co software developers
SkyEye offers comprehensive low-code enterprise modules, but full deployment requires careful assessment of multi-service infrastructure, incomplete public source, security posture, and tiered commercial licensing. Contact us to review architecture fit, deployment complexity, and vendor support terms.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
skyeye FAQ
Can I use the open-source version in production without paying?
What is the typical deployment footprint?
Does SkyEye provide managed hosting or SaaS?
Is this suitable for regulated industries (healthcare, finance)?
Software development & web development with DEV.co
Adopting skyeye is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source crm software in production.
Evaluating SkyEye for Your Enterprise?
SkyEye offers comprehensive low-code enterprise modules, but full deployment requires careful assessment of multi-service infrastructure, incomplete public source, security posture, and tiered commercial licensing. Contact us to review architecture fit, deployment complexity, and vendor support terms.