// the find
tegojs/tego
Tego is a pluggable Node.js framework for building customizable development platforms. It enables developers to create their own no-code/low-code systems or event-driven applications, while the core focuses on stability and environment adaptability.
Tego is a plugin-based Node.js/TypeScript framework for building your own internal tools platform — think Retool but self-hosted and extensible at the framework level. It sits between a full low-code product and a raw framework: you extend it with plugins to assemble CRM, ERP, or workflow tools. Aimed at teams who want to own the platform layer, not just configure a SaaS.
The package decomposition is solid — ACL, auth, cache, actions, and core are genuinely separate with their own test suites, not just folders pretending to be packages. The cache package includes bloom filter implementations for both memory and Redis, which shows someone thought about production deduplication rather than bolting it on later. The gateway layer uses IPC sockets alongside WebSockets, meaning multi-process deployments are a first-class concern, not an afterthought. Test coverage is real and spread across packages, not just a few smoke tests on the happy path.
The README itself opens with a warning that the git version is mid-refactor and may cause 'various unexpected issues' — they're pointing people to the npm package or Docker image for anything real, which means what you're reading on GitHub is not what you should be running. The default credentials being 'tachybase / !Admin123.' and CDN images hosted under tachybase's domain signal this is a rebranding of tachybase with unclear lineage and migration story. Documentation is thin: a five-line quick-start and a link to an external site that may or may not stay in sync with the code. The project explicitly acknowledges it has no community group, which for a framework in active refactor is a meaningful adoption risk.