Manifest

Manifest is a single‑file, self‑hosted backend engine that bundles data storage, business logic, authentication, and an admin UI into one minimalistic configuration file. It is designed for rapid iteration: a developer can define entities, relationships, and policies in a concise YAML file, then launch the entire stack with a single Node.js process. The framework abstracts away database migrations and admin scaffolding, allowing teams to ship prototypes or micro‑services in minutes rather than days.

Key Features

• Declarative entity model: Define tables, fields, relations, and validation rules directly in YAML.
• Built‑in CRUD API & SDK: Each entity automatically exposes REST endpoints (/api/<entity>) and a lightweight JavaScript SDK for client consumption.
• Multi‑database support: Choose between PostgreSQL, MySQL/MariaDB, SQLite, or a custom connection string; the schema is generated on first run.
• Custom endpoints & webhooks: Extend functionality with user‑defined handlers (beforeCreate, afterUpdate, etc.) that can call external services or trigger internal workflows.
• Auth & RBAC: Toggle authenticable: true on any entity to turn it into a user model; role‑based access control and ownership policies are defined in the same file.
• Storage layer: File uploads go to a local disk or an S3‑compatible endpoint, with optional image resizing.

Architecture & Technical Stack

The core engine parses the YAML file at startup, builds a Knex migration to sync the database schema, and registers route handlers based on declared policies. Middleware chains are constructed dynamically, allowing developers to inject custom logic without touching the core codebase.

Deployment & Infrastructure

• Self‑hosted: A single manifest.yml file and a Node.js runtime are all that is required.
• Containerization: Official Docker image (mnfst/manifest) includes the runtime and exposes port 3000.
• Scalability: While designed for lightweight services, the architecture can be horizontally scaled behind a load balancer. The database layer is fully compatible with production‑grade relational DBs, so scaling is limited only by the underlying database.
• Zero downtime: Hot‑reload of the YAML file is supported; changes are applied without restarting the server, making iterative development painless.

Integration & Extensibility

• Plugins: The plugin system exposes hooks for authentication providers, email services, or custom middleware.
• Webhooks: Trigger external HTTP endpoints on CRUD events (onCreate, onDelete, etc.).
• SDK hooks: Client‑side interceptors for token refresh or request logging.
• Custom endpoints: Developers can add arbitrary routes in a routes.js file that receives the same context as built‑in handlers.

Developer Experience

• Configuration: A single YAML file keeps all definitions in one place; no separate migration scripts or schema files.
• Documentation: The README and inline YAML comments provide clear examples; the community maintains a growing set of plugins.
• Community: Active Discord channel, open issues on GitHub, and frequent CI/CD checks ensure quick feedback.
• Testing: Built‑in test harnesses (manifest-test) allow unit tests for custom endpoints and policies.

Use Cases

1. Rapid Prototyping – Quickly spin up a data model for an MVP and iterate with live reload.
2. Micro‑services – Deploy isolated services (notification, payment gateway, file storage) with minimal boilerplate.
3. CRUD‑heavy Apps – Build directories, PIMs, or e‑shop backends with auto‑generated admin panels.
4. Headless CMS – Use the entity system to model content types and expose APIs for static site generators or SPA frontends.

Advantages Over Alternatives