Introduction
Gisila is a set of Dart packages for building HTTP backends, plus a self-hosted platform for running them. You can use each package on its own or combine them into a full stack.
The packages
Section titled “The packages”| Package | What it does | Use it when |
|---|---|---|
gisila |
Shelf-based MVC framework: annotated controllers, typed forms, services, permissions, middleware, logging | You are building an HTTP API in Dart |
gisila_orm |
Schema-first PostgreSQL ORM with codegen, query builder, migrations and eager loading | Your data lives in Postgres and you want typed queries |
gisila_queue |
Distributed task queue with Redis, RabbitMQ or in-memory brokers | Work should happen outside the request: email, reports, webhooks, retries |
gisila_redis |
Small Redis client used by the queue | You need the Redis connection the queue uses |
gisila_doc |
The OpenAPI-aware variant of gisila: specs plus route registration from one controller |
You want OpenAPI 3.1, Swagger UI or generated clients |
gisila_studio |
Auto-generated admin UI over your ORM tables | Staff need to browse and edit data without a custom frontend |
gisila-panel |
Self-hosted PaaS for compiled backends | You want Heroku-style deploys on your own VPS |
How they fit together
Section titled “How they fit together” ┌──────────────── your app ────────────────┐ request → │ gisila / gisila_doc controllers │ │ ├─ forms, permissions, services │ │ ├─ gisila_orm ──────────────→ PostgreSQL │ ├─ gisila_queue producer ────→ Redis / RabbitMQ ─→ workers │ └─ gisila_studio at /studio │ └───────────────────────────────────────────┘ deployed and supervised by gisila-panelWhere to go next
Section titled “Where to go next”- Choosing packages: which combination fits your project.
- Quickstart: a running API in a few minutes.
- Framework overview: the core of every Gisila app.