daptin  by daptin

Backend-as-a-Service application server

Created 9 years ago
1,899 stars

Top 22.6% on SourcePulse

GitHubView on GitHub
1 Expert Loves This Project
Project Summary

Daptin provides a comprehensive, "batteries-included" application server designed to streamline backend development. It addresses common needs like data modeling, APIs, authentication, permissions, file management, and background jobs, serving as a robust foundation for new projects or a powerful sidecar for existing systems. Developers benefit from a unified backend solution that reduces boilerplate and accelerates development cycles.

How It Works

Daptin operates on a schema-driven approach, defining data models that automatically generate RESTful (JSON:API), GraphQL, and OpenAPI specifications. It integrates core backend functionalities including user management, granular permissions (entity and row-level), file storage (local/cloud via rclone), background task execution (actions, state machines, scheduled jobs), and real-time capabilities via WebSockets. This consolidated architecture aims to provide a stable and consistent backend foundation.

Quick Start & Requirements

Highlighted Details

  • Data Modeling & APIs: Schema-defined entities with standard columns (id, reference_id, etc.), supporting JSON:API, optional GraphQL, and OpenAPI endpoints.
  • Identity & Permissions: Robust user, group, and role management with entity-level and row-level access control, supporting JWT and OAuth authentication flows.
  • LLM Integration: Provides OpenAI-compatible API endpoints (/v1/...) with built-in provider routing.
  • Realtime & Collaboration: WebSocket endpoint (/live) for event publishing (Olric PubSub) and optional YJS collaboration support.
  • File Management: Integrates with rclone for local and cloud storage, supporting various asset types.

Maintenance & Community

Licensing & Compatibility

  • License: LGPL v3. This copyleft license requires modifications to the Daptin core code to be shared under the same license, which may impact integration into proprietary commercial products.

Limitations & Caveats

For production deployments, using SQLite is discouraged in favor of PostgreSQL or MySQL/MariaDB. Secure configurations involving stable secrets, HTTPS/TLS, and robust backup/restore procedures for both database and file storage are essential. Durable file storage typically requires configuring cloud storage providers.

Health Check
Last Commit

2 days ago

Responsiveness

Inactive

Pull Requests (30d)
2
Issues (30d)
22
Star History
1 stars in the last 30 days

Explore Similar Projects

Feedback? Help us improve.