tachybase

Caution

Tachybase is still in the alpha stage. If you plan to use it in production, please proceed with caution. The codebase contains many experimental features and will undergo significant refactoring. Please feel free to contact us if you encounter any issues.

Tachybase

Tachybase is a pluggable application framework., where developers can build complex application logic, while core developers focus on ensuring the stability of key modules and adapting to different environments.

Project Overview

Tachybase is designed with a three-layer structure: Kernel Layer, Module Layer, and Plugin Layer.

• Kernel Layer provides core plugin mechanisms and unified interfaces.
• Module Layer implements specific application functions, such as building a low-code platform or creating a service orchestration tool with Tachybase.
• Plugin Layer offers more choices, for example, in the authentication module, different authentication sources can be implemented as plugins.

Currently, Tachybase aims to handle the framework's core functions and some common business logic, while providing low-code and AI capabilities for easier use. In the future, Tachybase will evolve into a flexible foundation, with different product layers based on it, offering unique positioning. Future versions will continue along the core, module, and plugin design route, while becoming increasingly productized.

Snapshots

For developers, by developers, we provide a variety of application templates and examples.

Using the Tachybase, you will not be limited to any specific development form. It can be an independent npm package loaded within the platform, embedded into an existing system, or a combination of both for development. Alternatively, if Tachybase earns your full trust, you can use it as the core to develop the next application.

Development Roadmap

The following is a general development roadmap. The detailed development plan will be announced by March 31, 2025, and will be released along with the related application templates.

• Kernel: Kernel API
• Kernel: Message Mechanism
• Kernel: Module API
• Module: Ant Design-based UI Library
• Module: Workflow
• Module: No-code Capability
• Module: Cloud Components
• Module: Message Queue
• Module: Scheduled Tasks
• Plugin: Workflow - Approval
• Plugin: Workflow - Data Templates

UI planning principles: The core mechanisms are designed in the Kernel Layer, and the specific components are provided in the Module Layer.

• Kernel: Modal Interaction (for context-sensitive interactions)
• Kernel: Tab Interaction (for interactions when a single page cannot contain too much content)
• Kernel: Independent Pages (for core or shared content)
• Module: Basic Components (single-line text, multi-line text, numbers, etc.)
• Module: Related Components (sub-table, sub-detail, etc.)
• Module: Specialized Components (dashboard, calendar, Gantt chart, file browser, etc.)

Try

Demo application

You can register an account and password on your own, create sub-applications within the system to explore, and experience the features. Please note that the test environment is not the latest version and may have some issues.

Quick Start with Docker Compose

We provides multiple Docker Compose test environments. Here's an example using a PostgreSQL database. You can quickly start with the following commands:

cd docker-compose-samples/app-postgres
docker compose up -d
# View startup logs
docker logs -f

# Visit app
http://localhost:3000
# Visit pgadmin
http://localhost:3080

Quick Start from Source Code

pnpm install
pnpm tachybase install
pnpm dev

Upgrade From Previous Version

pnpm install
pnpm tbu
pnpm dev

Default username：tachybase，password: !Admin123. The default database is sqlite, you can change it in .env file.

License

This project is licensed under the Apache 2.0 License。

Third-party Code Notice

The project includes a significant amount of code from third-party libraries such as RequireJS, JsonLogic, NocoBase, Formily, and Ant Design (antd). This code adheres to their original licenses and agreements. It will be gradually rewritten in the future. Please be mindful of this when using it in the early stages of the project.

Contributing

• Provide background information on deployment and usage, and describe the situations where the current system services fall short. Depending on the impact, we will categorize this into different development levels (Kernel, Module, or Plugin).
• Share usage cases where the current interaction methods do not meet your needs. We will address these based on their impact level.
• You are welcome to directly contribute code. We currently do not have a dedicated community group, but you can submit ideas through tickets, and we can discuss them together.