DEV.co
Open-Source CMS · 3xxx

engineercms

EngineerCMS is a Go-based knowledge management system designed for civil engineering teams to organize project documentation, collaborate on files, and share resources across multiple stakeholders. Built on the Beego framework with embedded SQLite, it includes document collaboration via OnlyOffice, e-book creation, full-text search, and mobile support via WeChat mini-program.

Source: GitHub — github.com/3xxx/engineercms
1.4k
GitHub stars
420
Forks
Go
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repository3xxx/engineercms
Owner3xxx
Primary languageGo
LicenseApache-2.0 — OSI-approved
Stars1.4k
Forks420
Open issues86
Latest releasev2.0.5 (2026-05-17)
Last updated2026-06-24
Sourcehttps://github.com/3xxx/engineercms

What engineercms is

A Beego web application (Go) with SQLite embedded database, featuring real-time document collaboration via OnlyOffice integration, Elasticsearch full-text search with IK Chinese tokenizer, MinIO distributed file storage support, Casbin role-based access control, and WebSocket chat functionality. Compiles to a standalone binary executable with no runtime dependencies.

Quickstart

Get the engineercms source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/3xxx/engineercms.gitcd engineercms# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-stakeholder Project Documentation

Manage civil engineering project artifacts (designs, PDFs, contracts, meeting notes) shared across owners, designers, supervisors, and contractors with granular permission controls per directory and file type.

Real-time Document Collaboration

Enable simultaneous editing of Office documents (docx, xlsx, pptx) and WPS formats (et, dps) via OnlyOffice with version history, format conversion, and export/import workflows for distributed teams.

Centralized Knowledge Repository

Consolidate project resources (e-books, PDFs, articles, images, videos) in a single platform with full-text search, project templating, and structured hierarchical directories to reduce duplication and improve retrieval.

Implementation considerations

  • SQLite database is suitable for small-to-medium teams (< 500 users); migration to PostgreSQL or MySQL requires custom schema porting and testing.
  • OnlyOffice Document Server must be deployed separately; coordinate licensing and resource allocation (CPU/memory) for concurrent document sessions.
  • Elasticsearch and IK tokenizer require separate infrastructure if full-text search is enabled; adds operational complexity for indexing and maintenance.
  • MinIO deployment optional but recommended for production; requires S3-compatible object storage configuration and network isolation from web tier.
  • Initial deployment requires manual project/directory structure setup and role-based access control (RBAC) via backend; consider data migration scripts from legacy systems.

When to avoid it — and what to weigh

  • Require Immediate Commercial Support — Project is community-maintained with no stated commercial support tier, SLA guarantees, or vendor backing. Support limited to GitHub issues and personal contact (QQ/WeChat) with maintainer.
  • Need Multi-language UI Out of Box — Documentation and UI are primarily in Chinese (中文). Non-Chinese teams will face translation overhead and reduced community support for localization questions.
  • Strict Data Residency or Compliance Requirements — No explicit security audit, penetration test results, or compliance certification (SOC 2, ISO 27001) documented. Requires independent security review before use in regulated industries (healthcare, finance).
  • Require Enterprise HA/DR Setup — Embedded SQLite is not designed for multi-node HA. MinIO support exists but requires significant custom deployment work; no official Kubernetes Helm charts or managed deployment guidance provided.

License & commercial use

Apache License 2.0 (permissive OSI license). Permits commercial use, modification, and distribution with attribution and liability disclaimer. No copyleft restriction; you may use in proprietary products. Full license terms must be included in distribution.

Commercial use is permitted under Apache 2.0 terms. However, no commercial support, warranties, or indemnification from maintainers are provided or implied. You assume all operational, security, and compliance risk. Recommend independent security audit and support contract with a third party if deploying in production business environments.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationLimited
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceMedium
Security considerations

No public security audit, CVE disclosure process, or penetration test results provided. Relies on Beego framework security (v2.x maintained) and upstream dependencies. File-level permission controls via Casbin, role-based access via casbin rules, and file extension-based ACLs are implemented. HTTPS/TLS configuration not explicitly documented. Data in transit and at rest security posture requires independent review. No explicit input validation or XSS/CSRF mitigation details provided in README.

Alternatives to consider

Alfresco

Enterprise ECM with multi-language UI, advanced compliance, HA/DR, LDAP/SSO, and commercial support. Overkill for small engineering teams but lower operational risk.

Nextcloud

Open-source file sync & share (PHP/JS) with strong documentation, plugins for office integration, and larger community. More flexible for general-purpose knowledge management; less specialized for engineering workflows.

Mattermost + custom tools

Open-source team chat and collaboration. Requires significant custom development for project-specific features (hierarchical docs, workflow, engineering integrations) but proven ops model.

Software development agency

Build on engineercms with DEV.co software developers

Evaluate architecture fit, conduct a security audit, and plan your OnlyOffice/Elasticsearch deployment. Devco can help with custom integrations, DevOps setup, and ongoing support.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

engineercms FAQ

Can I use this in production without modifying the database?
Yes, SQLite is embedded and requires no separate DB setup. However, for > 100 concurrent users or multiple servers, schema migration to PostgreSQL is recommended and not officially documented.
What is the licensing cost?
Apache 2.0 is free; no licensing cost. No commercial support tier published. Any paid support would be via third-party vendors or custom service agreements.
Does it integrate with Microsoft Teams or Slack?
Not documented. WeChat mini-program is the mobile client. No official Slack/Teams bot or webhook integration; custom development required.
How do I back up and restore data?
SQLite file-based backup (copy database file); MinIO object storage uses S3 snapshots if configured. Detailed backup/restore procedures not in README; operations team must design own BCP.

Work with a software development agency

Adopting engineercms 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 cms software in production.

Ready to Deploy EngineerCMS?

Evaluate architecture fit, conduct a security audit, and plan your OnlyOffice/Elasticsearch deployment. Devco can help with custom integrations, DevOps setup, and ongoing support.