A full-stack TypeScript CRUD framework that uses a single source of truth for API, client, and ORM.
Remult is a full-stack TypeScript framework that simplifies building CRUD applications by using a single source of truth for your data model. It automatically generates a type-safe REST API and ORM from your TypeScript entity definitions, handling validation, authorization, and real-time updates. It solves the problem of repetitive boilerplate code in full-stack development while keeping the codebase maintainable and flexible.
Full-stack TypeScript developers building data-driven web applications, especially those who want to reduce boilerplate and ensure end-to-end type safety. It’s also suitable for teams working with multiple databases or frontend frameworks.
Developers choose Remult because it eliminates the need for separate API and ORM code while providing full-stack type safety without code generation. Its framework-agnostic design and support for major databases make it highly adaptable, and its fine-grained control allows handling complex scenarios without sacrificing simplicity.
Full-stack CRUD, simplified, with SSOT TypeScript entities
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates REST endpoints with paging, sorting, filtering, and real-time live queries directly from TypeScript entities, eliminating manual API coding as shown in the README's query examples.
Provides type-safe API calls, ORM operations, and RPC without code generation, ensuring consistency across frontend and backend based on entity definitions.
Validation rules defined in entity decorators run on both server and client, improving UX with immediate feedback and security, as demonstrated in the error handling examples.
Enables fine-grained, code-based access controls per entity or field, allowing dynamic rules like allowing updates only if the user is the author, as highlighted in the authorization snippet.
Heavily relies on TypeScript decorators for entity definition, which can be a barrier for teams avoiding decorators or using older setups, despite alternative non-decorator support.
As the project is pre-v1.0, the API is subject to breaking changes, which could impact long-term maintenance and production readiness, as noted in the status section.
The documentation is explicitly mentioned as a work-in-progress, which may slow onboarding and troubleshooting for complex use cases not fully covered.