Introduction
Your backend. Your infrastructure.
Nodabase is an open-source, self-hosted backend platform for Node.js.
What modern Node.js applications need
Most Node.js applications end up needing the same set of capabilities:
- database
- authentication
- cache
- object storage
- queues
- background jobs
Developers normally have to assemble and configure these services individually, one project at a time. The same wiring is repeated, and the result is a handful of services that have to be kept in sync.
Nodabase brings them together into one Docker-first platform.
Nodabase does not reinvent infrastructure
Nodabase is a composition and orchestration layer. It does not try to replace PostgreSQL, authentication, caching, object storage or messaging with new implementations.
The layers look like this:
Your application
|
v
Nodabase
|
v
existing, battle-tested infrastructureEach capability is still backed by a real, well-understood service. You can connect to it directly, inspect it, and replace it. The underlying technologies stay understandable and under your control.
Current components
| Capability | Service |
|---|---|
| Database | PostgreSQL |
| Authentication | GoTrue |
| Cache | Dragonfly (Redis-compatible) |
| Storage | MinIO (S3-compatible object storage) |
| Queues | NATS (JetStream) |
| Jobs | Job Runner + PostgreSQL |
| Runtime | Node.js runtime |
| Management | Control Plane and Dashboard |
One client for the platform
Everything above is reached through a single Node.js package:
import { nodabase } from "nodabase";const { rows } = await nodabase.db.query("SELECT NOW() AS time");console.log(rows[0]);
The client exposes nodabase.db, nodabase.auth, nodabase.cache, nodabase.storage, nodabase.que and nodabase.jobs.
Who Nodabase is for
Nodabase is useful for:
- Node.js applications
- SaaS applications
- internal tools
- MVPs
- small and medium applications
- applications where the developer wants control over the infrastructure