tego
Tego is a pluggable Node.js framework for building customizable no-code/low-code platforms and event-driven applications. It provides a self-hosted, extensible core focused on stability and environment adaptability, with official pre-built packages available for faster deployment.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | tegojs/tego |
| Owner | tegojs |
| Primary language | TypeScript |
| License | Apache-2.0 — OSI-approved |
| Stars | 1.1k |
| Forks | 111 |
| Open issues | 15 |
| Latest release | v1.6.16 (2026-07-07) |
| Last updated | 2026-07-07 |
| Source | https://github.com/tegojs/tego |
What tego is
TypeScript-based Node.js framework with a plugin architecture, supporting customizable workflows, CRUD operations, and admin dashboards. Deployable via Docker, npm, or from source; uses SQLite by default with database configuration via environment variables.
Get the tego source
Clone the repository and explore it locally.
git clone https://github.com/tegojs/tego.gitcd tego# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Use official tegojs/tego-standard frontend and tegojs/tego-all Docker image for production stability; avoid building from Git main branch during active refactor.
- SQLite is default; plan database migration path early if moving to PostgreSQL or MySQL for multi-node deployments.
- Plugin architecture requires clear versioning and compatibility testing; document breaking changes between core framework releases.
- Default credentials (!Admin123. for tachybase) must be rotated immediately in production; no mention of secrets rotation best practices.
- Node.js version compatibility and dependency lock strategy must be defined; npm audit regularly for transitive vulnerabilities.
When to avoid it — and what to weigh
- Production Stability Required Immediately — README explicitly warns that the Git version is undergoing core refactor and may cause unexpected issues. Only use official npm package, Docker image, or tego-standard for production; Git main branch is not stable.
- High-Performance, Real-Time Workloads — No performance benchmarks, scalability data, or real-time infrastructure guarantees provided. Unknown capacity for concurrent users, request throughput, or latency-sensitive operations.
- Compliance or Airflow/Orchestration-Heavy Environments — No documented support for compliance frameworks (SOC 2, HIPAA, GDPR audit trails), data lineage, or integration with enterprise orchestration tools. Requires thorough review before regulated use.
- Minimal Maintenance Tolerance — Project is 8 months old with active refactoring. Dependency on a relatively young framework; stability and long-term maintenance commitment not yet proven.
License & commercial use
Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved license allowing commercial use, modification, and distribution with attribution and liability disclaimer.
Apache-2.0 explicitly permits commercial use and closed-source derivatives. However, users must include a copy of the license and provide notice of changes. No commercial support, SLA, or indemnification mentioned; vendor lock-in risk is low but support ecosystem is unknown.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Strong |
| Assessment confidence | Medium |
Default credentials must be rotated in production. No documented security audit, penetration test results, or security policy visible. Requires review of: authentication/authorization mechanisms, SQL injection/XSS protections, dependency vulnerability scanning, and secrets handling practices. Self-hosted deployment shifts security responsibility to operator.
Alternatives to consider
NocoDB / Airtable
Simpler, managed SaaS or open-source low-code alternatives with stronger communities; less framework overhead if you don't need heavy customization.
Supabase / Firebase
Backend-as-a-service with built-in auth, real-time, and scalable database; faster if you prioritize minimal ops and cloud-native architecture.
Retool / Budibase
Established low-code platforms with richer component libraries, stronger documentation, and commercial support; better if internal tools are the sole focus.
Build on tego with DEV.co software developers
Review the production deployment paths (npm, Docker, tego-standard), test the quick-start setup, and assess plugin compatibility with your integration needs before committing to Git main during active refactor.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
tego FAQ
Is Tego production-ready?
Can I use Tego commercially?
What databases does Tego support?
How do I extend Tego for custom workflows?
Software developers & web developers for hire
Adopting tego 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.
Evaluate Tego for Your Low-Code Platform
Review the production deployment paths (npm, Docker, tego-standard), test the quick-start setup, and assess plugin compatibility with your integration needs before committing to Git main during active refactor.